AI & RAG
Weekly Battlecard Staleness Audit Against Recent Losses
Runs weekly to compare your published Notion battlecards against the latest win-loss notes, flagging cards that contradict or omit recent loss patterns and proposing edits.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires
- ActionPull current battlecards from NotionNotion
- ActionRetrieve recent win-loss notesPostgres
- ActionCross-check cards vs losses and rate stalenessOpenAI
- OutputPost prioritized edit suggestions to SlackSlack
What it does
Each week it reads your live battlecards in Notion and the most recent win-loss notes from Postgres, then asks an LLM whether any card is now stale — contradicted by recent losses or missing a newly common objection. It produces a prioritized list of suggested edits.
When to use it
Use it when battlecards drift out of date and reps lose trust in them. Good for product marketing teams that own a competitor library and want a standing review instead of an annual scramble.
How it works
- 1A weekly schedule fires the audit.
- 2The workflow pulls the current battlecard pages from Notion.
- 3It retrieves win-loss notes added in the last 30 days from Postgres.
- 4An LLM cross-checks each card against recent losses and rates staleness, citing the conflicting notes.
- 5A summary with proposed edits per card is posted to Slack for the owner to action.
Set it up
What you configure once, before turning it on.
- 1Connect NotionPages, databases, comments.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect OpenAIModels, embeddings, files.
- 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 AI & RAG workflows
RFP and security questionnaire drafter grounded in Coda
Drafts answers to inbound RFP and security questionnaire questions by retrieving approved language from your Coda hub, then files the cited draft for review before a rep sends it.
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.
Grounded reply suggestions for inbound sales email
Reads inbound prospect emails, retrieves the matching answers from your Coda hub.
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.
On-Call Spec Answerer from Dropbox Engineering Corpus
Answers on-call questions posted in a Slack channel by retrieving the most relevant Dropbox engineering specs and replying with a grounded, source-cited answer in the thread.
Agentic Deep-Dive API Researcher for Hard Spec Questions
An agent fielded via webhook that answers multi-part API questions by iteratively searching OpenAPI specs, changelogs, and Confluence runbooks.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.