AI AGENTS
Discord FAQ Gap Digest from Unanswered Questions
On a daily schedule, scans the questions the FAQ agent had to escalate, clusters the recurring ones it couldn't answer from docs.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires
- ActionPull escalated unanswered questions from PostgresPostgres
- LogicCluster and rank recurring topics
- ActionCheck Notion for existing coverageNotion
- OutputPost prioritized docs-gap digest to Discord modsDiscord
What it does
This is the feedback loop that makes your deflection agent get smarter. Instead of answering live, it runs once a day, looks back at every question that got escalated because the docs didn't cover it, groups the recurring themes, and tells your team exactly which docs to write next — ranked by how often each gap was hit.
When to use it
Run this alongside any live FAQ agent. Use it weekly or daily when you want documentation work driven by real demand instead of guesswork, and to prove the deflection rate is climbing.
How it works
- 1A scheduled trigger fires (e.g., every morning).
- 2The flow pulls the last day of escalated, unanswered questions logged in Postgres.
- 3A clustering step groups them into recurring topics and ranks by frequency.
- 4It cross-checks Notion to confirm no doc already covers each top topic.
- 5It posts a prioritized "docs to write" digest into the Discord mod channel, with question counts and example messages per gap.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect NotionPages, databases, comments.
- 3Connect DiscordCommunity channels + voice + bots.
- 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 Agents workflows
Custom Metrics Cardinality Spike Pager
A webhook from a Datadog monitor fires when custom-metric cardinality jumps; an agent pinpoints the offending metric and tag, estimates the added cost.
Sentry-to-Confluence Runbook Updater
When a Sentry issue is resolved, the agent finds the matching Confluence runbook page and proposes an inline update with the verified fix.
Stale Doc-PR Chaser for Runbook Gaps
On a daily schedule the agent finds runbook doc PRs that were opened from resolved incidents but never reviewed, summarizes what each one fixes.
Resolved Incident to Public Troubleshooting Doc
For customer-facing errors resolved in Sentry, the agent drafts a sanitized troubleshooting entry and opens a PR to your ReadMe documentation.
On-Call Runbook Gap Closer: Resolved Sentry Issues to Doc PRs
An agent reads each newly resolved Sentry issue, compares the actual fix against your existing runbook, and opens a GitHub PR adding the missing remediation steps.
Weekly On-Call Doc-Gap Digest
Each week the agent reviews every Sentry issue resolved in the last 7 days, ranks the ones whose runbook coverage is missing or thin.
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.