SUMMARIZATION
Lost-Deal Objection Alert from Zoom Calls to Slack
Scans recorded Zoom calls tied to deals that recently went closed-lost, extracts the unresolved objection that likely killed the deal.
How it runs
The automated pipeline, trigger to output.
- TriggerDeal marked closed-lost via CRM webhookHTTP webhook
- ActionFind and fetch the deal's latest Zoom transcriptZoom
- LogicSkip if no transcript or call too short
- ActionIdentify the decisive unresolved objection with OpenAIOpenAI
- OutputPost objection and rebuttal alert to SlackSlack
What it does
When a deal is marked closed-lost, this workflow finds the most recent Zoom call on that deal, identifies the specific objection the rep failed to overcome, and surfaces it to the team in Slack within minutes.
When to use it
Use this when post-mortems on lost deals happen too late or not at all. It catches the decisive objection while the rep still remembers the conversation, so the debrief is grounded in what actually happened.
How it works
- 1A CRM webhook fires when a deal moves to closed-lost.
- 2The flow locates the most recent Zoom recording associated with that deal and pulls its transcript.
- 3A logic step filters out calls with no transcript or calls shorter than a meaningful threshold.
- 4OpenAI reads the transcript and isolates the single unresolved objection most likely tied to the loss, plus a suggested rebuttal.
- 5A formatted alert with the deal name, objection, and coaching tip is posted to the sales Slack channel.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect ZoomMeetings, recordings, transcripts.
- 3Connect OpenAIModels, embeddings, files.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Summarization workflows
Daily Front Escalation Digest with Salesforce Rollup
Each morning, sweeps the prior day's escalated Front conversations, summarizes each, enriches with Salesforce account value, and emails account execs a single prioritized digest.
File a Linear ticket for regressed errors after deploy
Detects Sentry issues that regressed in the latest deploy's release window, summarizes what broke and when it was previously fixed.
Daily release-health rollup to Confluence
Each morning, compares the last 24 hours of Sentry activity against the deploys that shipped in that window and publishes a dated release-health page to Confluence summarizing…
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.
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.
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.