AI & RAG
Detect changed specs between manual revisions and alert affected teams
When a new manual revision is indexed, it diffs key specs against the prior version and posts a 'spec changed' alert to Slack summarizing what changed, the old vs new values.
How it runs
The automated pipeline, trigger to output.
- TriggerManual version marked superseded after reindexSupabase
- ActionFetch old and new page chunks for the same equipmentSupabase
- ActionExtract and align spec key-value pairs across revisionsOpenAI
- LogicKeep only specs whose values changed; attach old, new, and page
- OutputPost 'spec changed' alert with page link to Slack ops channelSlack
What it does
Compares each newly ingested manual revision against the version it replaces, uses an LLM to extract and align the technical specs, and flags any value that changed. It then sends a structured alert so techs do not keep working from outdated torque, voltage, or clearance numbers.
When to use it
When a manufacturer ships a revision and you need to know immediately which specs moved, not just that a new PDF exists. Critical for safety-sensitive or warranty-bound equipment where a stale spec causes rework.
How it works
- 1The reindex workflow marks a manual version as superseded, firing this trigger.
- 2The flow pulls the old and new page chunks for the same equipment from Supabase.
- 3OpenAI extracts comparable spec key-value pairs from both revisions and aligns them.
- 4A logic step keeps only specs whose values actually changed, attaching old value, new value, and page.
- 5If any change is found, a formatted 'spec changed' alert with a page link is posted to the Slack ops channel.
Set it up
What you configure once, before turning it on.
- 1Connect SupabaseTables, auth, storage, edge functions.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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
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.
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…
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.
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.
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.