AI & RAG
Incident Runbook Walkthrough Agent via Webhook
Given an active incident, retrieves the matching runbook and returns a step-by-step remediation walkthrough with citations, then posts a status thread to Microsoft Teams.
How it runs
The automated pipeline, trigger to output.
- TriggerWebhook receives incident summary and serviceHTTP webhook
- ActionRetrieve service-scoped runbook stepsPostgres
- LogicIf no runbook found, return explicit notice
- ActionAssemble ordered cited remediation walkthroughOpenAI
- OutputPost walkthrough thread to Microsoft TeamsMicrosoft Teams
What it does
During an incident, an operator (or an alerting system) sends the incident details to a webhook and gets back an ordered remediation plan drawn strictly from the relevant Confluence and Drive runbook. Each step carries a citation so responders can verify the source, and the plan is posted to a Teams channel as a living incident thread.
When to use it
Use it when severity-1 response depends on a runbook nobody can find fast under pressure. It collapses 'which doc, which section' into one grounded, cited checklist and broadcasts it where the response team is already coordinating.
How it works
- 1An HTTP webhook receives the incident summary and affected service.
- 2The summary is embedded and matched against the runbook index in Postgres, scoped to the affected service.
- 3A logic gate confirms a runbook exists; if not, it returns an explicit 'no runbook on file' response.
- 4OpenAI assembles an ordered remediation walkthrough constrained to the retrieved steps, each with a citation.
- 5The walkthrough is posted to the incident's Microsoft Teams channel as a threaded message.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect OpenAIModels, embeddings, files.
- 4Connect ConfluenceSpaces, pages, blueprints.
- 5Connect Microsoft TeamsChannels, chats, files.
- 6Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 7Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 8Test, 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 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.