SUMMARIZATION
Extract objections from a Zoom sales call and log them to Salesforce
After a Zoom sales call ends, transcribes it, pulls out every buyer objection with the surrounding context.
How it runs
The automated pipeline, trigger to output.
- TriggerZoom recording completedZoom
- ActionFetch call transcript from ZoomZoom
- ActionExtract categorized objections with OpenAIOpenAI
- LogicSkip calls with no objections
- ActionMatch meeting to Salesforce opportunitySalesforce
- OutputWrite objection notes to the opportunitySalesforce
What it does
When a recorded Zoom sales call finishes, this workflow turns the raw transcript into a clean, categorized list of buyer objections (price, timing, competitor, authority, feature gap) and attaches them to the right Salesforce opportunity so reps and product leaders can see exactly what blocked the deal.
When to use it
Run this on every recorded discovery or demo call where you want a durable record of what the prospect pushed back on — without a rep having to retype notes from memory. Ideal for teams that already live in Salesforce and want objection data sitting next to the deal.
How it works
- 1A Zoom recording-completed event fires the workflow with the meeting and recording IDs.
- 2The workflow fetches the call's transcript text from Zoom.
- 3OpenAI reads the transcript and returns each objection as a structured item: a quote, a category, and the rep's response (or lack of one).
- 4A filter drops calls with zero objections so noise never reaches the CRM.
- 5The workflow matches the meeting to a Salesforce opportunity by attendee email or meeting subject.
- 6The categorized objections are written to the opportunity as a timestamped note for the deal team.
Set it up
What you configure once, before turning it on.
- 1Connect ZoomMeetings, recordings, transcripts.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect SalesforceAccounts, opportunities, cases.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Summarization workflows
On-submit Loom standup roll-up archived to Confluence
When a standup video is submitted via webhook, transcribes it, generates a per-person written summary, and appends it to a running team standup page in Confluence.
Front Escalation Handoff Doc in Notion
When a Front escalation closes, drafts a structured handoff document in Notion capturing the resolution, customer commitments, and open follow-ups, then alerts the AE in Slack.
Front Escalation War-Room Brief to Slack
On a Front escalation, posts a concise threat-assessment brief to a Slack channel only when the AI judges the situation high-severity.
VIP Front Escalation Instant Exec Page-Out
Detects escalations from VIP accounts in Front, generates a one-paragraph executive recap, and pages the named account exec via Slack and Salesforce task within minutes.
Release health note per Vercel deploy
When a Vercel deploy goes live, summarizes the Sentry errors observed in the release window into a plain-English health note that separates brand-new error classes…
Rollback recommendation when a deploy spikes errors
When a Sentry alert fires for an error spike, attributes it to the most recent deploy, summarizes whether the spike is dominated by new error classes introduced by that release.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.

Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.
