SUMMARIZATION
Dropped Transcript File to Deal Objection Cards
Watches a Google Drive folder for newly uploaded call transcript files, condenses each into objection-handling cards with OpenAI.
How it runs
The automated pipeline, trigger to output.
- TriggerNew transcript file in Drive folderGoogle Drive
- ActionRead file and parse deal identifierGoogle Drive
- ActionCondense into objection cards with OpenAIOpenAI
- LogicBranch on matching opportunity found
- OutputFile cards on deal or log review taskSalesforce
What it does
Lets reps drop a raw transcript file into a Drive folder and have it automatically distilled into objection cards and attached to the correct deal, with a safety net for files that can't be matched.
When to use it
Use this when calls are recorded outside Zoom (Gong exports, dialer transcripts, manual notes) and you want one folder where any transcript becomes structured deal intelligence.
How it works
- 1A Google Drive trigger fires when a new file lands in the watched transcripts folder.
- 2The flow reads the file contents and parses the opportunity identifier from the filename or header.
- 3OpenAI condenses the transcript into objection-handling cards with rep response and suggested counter.
- 4A logic branch checks whether a matching Salesforce opportunity exists.
- 5If matched, the cards are filed on that opportunity; if not, a review task is logged so nothing is silently dropped.
Set it up
What you configure once, before turning it on.
- 1Connect Google DriveDocs, sheets, slides, files.
- 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.