AI AGENTS
Dedupe call feature requests into an Airtable tracker
Extracts explicit feature requests from each call transcript and logs them into an Airtable tracker.
How it runs
The automated pipeline, trigger to output.
- TriggerCall transcript completedZoom
- ActionExtract explicit feature requestsOpenAI
- ActionSemantic search Airtable for existing requestAirtable
- LogicBranch: existing match vs new request
- OutputUpdate count or create new tracker rowAirtable
What it does
For every call transcript it isolates the explicit feature requests a customer made, then checks an Airtable tracker for an existing matching request. If one exists, it increments the request count and appends the new account and quote; if not, it creates a fresh row. The result is a deduplicated, vote-counted feature ledger.
When to use it
Use it when feature requests pile up as duplicate one-liners across hundreds of calls and you need a single tracker that shows true demand per request rather than raw mention count.
How it works
- 1A finished call transcript starts the run.
- 2The model extracts discrete, explicit feature requests from the conversation.
- 3For each request it semantically searches the Airtable tracker for an equivalent existing entry.
- 4A branch decides match versus new.
- 5On a match, it updates the row: bump the count, add the requesting account and a supporting quote.
- 6On no match, it creates a new tracker row with the request, source account, and first quote.
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
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.
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.
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.
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.
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.
Weekly On-Call Doc-Gap Digest
Each week the agent reviews every Sentry issue resolved in the last 7 days, ranks the ones whose runbook coverage is missing or thin.
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.
