SUMMARIZATION
Sales-objection radar from discovery calls into an Airtable tracker
After each Zoom discovery call, isolates the objections and lost-deal signals, classifies them by type, and logs them to an Airtable objection tracker.
How it runs
The automated pipeline, trigger to output.
- TriggerZoom discovery call endsZoom
- ActionExtract + classify objections with quotesOpenAI
- ActionLog each objection to Airtable trackerAirtable
- LogicCheck rolling count per category vs threshold
- OutputAlert Slack on objection-category spikeSlack
What it does
Gives sales and product a running ledger of why deals stall. After a discovery call, it parses the transcript specifically for objections, hesitations, and competitor mentions, classifies each into a category (price, timing, missing feature, competitor, trust), and writes a row to an Airtable objection tracker with the quote and account. When one category spikes past a threshold in a rolling window, it fires a Slack alert so the team can respond before the pattern costs more deals.
When to use it
Use this when objections are scattered across reps' memories and call notes, and no one notices that "too expensive" tripled this month. It builds an auditable objection dataset and an early-warning signal in one pass.
How it works
- 1A Zoom discovery-call-ended event triggers the workflow.
- 2OpenAI extracts objections and classifies each into a fixed category set with a supporting quote.
- 3Each classified objection is written as a row to the Airtable objection tracker.
- 4A logic step checks the rolling count per category against a spike threshold.
- 5If a category spikes, a Slack alert names the objection, the count, and recent example quotes.
Set it up
What you configure once, before turning it on.
- 1Connect ZoomMeetings, recordings, transcripts.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect AirtableBases, tables, views, automations.
- 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.