SALES

Compile a weekly objection-trend digest from Zoom calls into Notion

On a weekly schedule, aggregates all objection types tagged across the week's Zoom discovery calls and publishes a ranked trend report to a Notion page for the sales team's review.

CategorySales
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule
  • ActionList week's Zoom discovery recordingsZoomZoom
  • ActionTag objections across all transcriptsHugging FaceHugging Face
  • LogicAggregate counts by type, rep, and deal
  • OutputPublish ranked trend digest to NotionNotionNotion

What it does

This workflow rolls up a full week of discovery-call objections into a single trend report. It counts how often each objection type came up, which deals and reps they were tied to, and how the mix shifted from the prior week, then publishes a clean, ranked digest to Notion that the team can review in their weekly sales sync.

When to use it

Use it when you want a recurring, team-level view of what is actually slowing deals down, rather than per-call alerts. It is built for sales leaders who run weekly pipeline reviews and want objection trends in front of them without manual tallying.

How it works

A weekly schedule triggers the flow. It lists every Zoom discovery recording from the past seven days and fetches each transcript. A Hugging Face classifier tags objections per call, and a logic step aggregates the tags into counts by type, rep, and deal. The flow formats a ranked digest with week-over-week deltas and writes it as a new dated page in the team's Notion sales database.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect ZoomMeetings, recordings, transcripts.
  2. 2
    Connect Hugging FaceModels, datasets, spaces — the open-source hub.
  3. 3
    Connect NotionPages, databases, comments.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.