AI & RAG
Index Won/Lost Call Transcripts into a Searchable Objection Playbook
Watches a Dropbox folder for new sales-call transcripts, splits each into objection/response pairs, embeds them, and writes a searchable.
How it runs
The automated pipeline, trigger to output.
- TriggerNew transcript added to Dropbox folderDropbox
- ActionDownload and read transcript textDropbox
- ActionExtract objection/response pairs + outcome with OpenAIOpenAI
- ActionGenerate embeddings for each snippetOpenAI
- LogicDrop low-quality fragments below length threshold
- OutputUpsert indexed snippets into Notion playbook DBNotion
What it does
This is the ingestion half of an objection-handling RAG system. Every time a new call transcript lands in Dropbox, it extracts the moments where a prospect raised an objection and the rep responded, tags each pair with the deal outcome (won or lost), generates embeddings, and stores the indexed snippets in a Notion database. The result is a clean, queryable corpus that downstream retrieval workflows draw from.
When to use it
Run this once to stand up the knowledge base, then leave it on. Use it when your team records calls (Gong, Zoom, Fireflies) and exports transcripts to Dropbox, and you want every conversation to feed a living playbook instead of dying in a folder.
How it works
- 1A new file in the watched Dropbox folder triggers the flow.
- 2The transcript text is downloaded and read.
- 3OpenAI segments the call into objection -> response pairs and labels the deal outcome and topic.
- 4Each pair is embedded for semantic search.
- 5A filter drops fragments shorter than a usable threshold so noise never enters the index.
- 6The clean, embedded snippets are upserted into the Notion playbook database, one row per objection with a link back to the source transcript.
Set it up
What you configure once, before turning it on.
- 1Connect DropboxFiles and folders.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect NotionPages, databases, comments.
- 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 & RAG workflows
Coda-grounded sales answer bot with citations in Slack
Reps ask product, pricing, or competitive questions in Slack and get an answer drawn only from your Coda knowledge hub, with links to the exact docs and rows it pulled from.
Weekly knowledge-gap digest from unanswered rep questions
Each week, scans rep questions the answer bot couldn't ground in Coda, clusters the recurring gaps.
Pre-meeting prep brief grounded in Coda and CRM
Before each booked sales meeting, builds a one-page prep brief by combining the account's HubSpot context with grounded talking points and objection responses pulled from your…
Publish a Grounded API FAQ Page to Confluence Weekly
Each week, clusters the top unanswered or repeated API questions, generates spec-grounded answers with citations.
Detect Breaking API Changes from Spec Diffs and Alert Owners
Compares the new OpenAPI spec against the previous version on each GitLab merge, uses retrieval over the changelog to classify whether changes are breaking.
Re-Index API Specs on GitLab Merge to Keep the Answer Bot Fresh
Watches GitLab merges to your API repo, detects changed OpenAPI specs and changelog files, re-chunks and re-embeds only what changed.
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.
