AI AGENTS
Zoom Demo Objection Trend Tracker in Airtable
After each Zoom demo, normalizes every objection into a typed category and logs one row per objection in Airtable.
How it runs
The automated pipeline, trigger to output.
- TriggerZoom recording completed for a demo callZoom
- ActionFetch transcript and host metadataZoom
- ActionExtract and normalize objections to taxonomyOpenAI
- LogicDedupe objections and attach call context
- OutputWrite one row per objection to AirtableAirtable
What it does
Builds a structured, analyzable record of objections over time. Every objection from every demo becomes a normalized Airtable row tagged with category, rep, deal size band, and outcome signal, so enablement can spot patterns like a competitor objection spiking after a rival's launch.
When to use it
Use it when you want data, not anecdotes. If you need to answer questions like "which objection costs us the most late-stage deals" or "which reps consistently beat pricing pushback," this turns scattered call audio into a tidy table you can pivot and chart.
How it works
- 1Zoom fires its recording-completed event for a demo.
- 2The flow fetches the transcript and host metadata.
- 3An OpenAI step extracts each objection and normalizes it to a fixed taxonomy (price, timing, competitor, authority, integration, trust).
- 4A logic step deduplicates near-identical objections within the same call and attaches the rep and call context.
- 5The workflow writes one Airtable row per normalized objection with category, rep, severity, and the rep's response.
Set it up
What you configure once, before turning it on.
- 1Connect ZoomMeetings, recordings, transcripts.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect AirtableBases, tables, views, automations.
- 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 AI Agents workflows
Stale Doc-PR Chaser for Runbook Gaps
On a daily schedule the agent finds runbook doc PRs that were opened from resolved incidents but never reviewed, summarizes what each one fixes.
On-Call Runbook Gap Closer: Resolved Sentry Issues to Doc PRs
An agent reads each newly resolved Sentry issue, compares the actual fix against your existing runbook, and opens a GitHub PR adding the missing remediation steps.
Datadog Bill Spike Attribution Agent
When a daily Datadog cost check detects a spend jump, an agent attributes the increase to the specific services and metric types driving it and posts a ranked breakdown to Slack.
Sentry-to-Confluence Runbook Updater
When a Sentry issue is resolved, the agent finds the matching Confluence runbook page and proposes an inline update with the verified fix.
Custom Metrics Cardinality Spike Pager
A webhook from a Datadog monitor fires when custom-metric cardinality jumps; an agent pinpoints the offending metric and tag, estimates the added cost.
Resolved Incident to Public Troubleshooting Doc
For customer-facing errors resolved in Sentry, the agent drafts a sanitized troubleshooting entry and opens a PR to your ReadMe documentation.
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.