CHATBOTS

Weekly Discord doc-gap digest from unanswered questions

Reviews the week's low-confidence and escalated Discord questions, clusters the recurring gaps, and posts a prioritized 'docs to write' digest to Notion and the team channel.

CategoryChatbots
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule fires
  • ActionPull flagged questions from Discord historyDiscordDiscord
  • ActionCluster and rank gaps with OpenAIOpenAI
  • ActionCreate doc-gap report page in NotionNotionNotion
  • OutputPost digest to team Discord channelDiscordDiscord

What it does

Turns the questions your bot couldn't confidently answer into a roadmap for documentation. On a weekly schedule it gathers low-confidence and escalated questions, groups them into themes, and produces a ranked list of missing or unclear docs.

When to use it

Use it when you want your community channel to actively improve your docs over time. It's the feedback loop that closes the gap between what members ask and what your knowledge base covers.

How it works

  1. 1A weekly schedule triggers the flow.
  2. 2The week's flagged questions (low confidence, escalated, or negatively rated) are pulled from Discord channel history.
  3. 3OpenAI clusters them into topics and ranks each by frequency and onboarding impact.
  4. 4A new Notion page is created capturing the gap themes, example questions, and suggested doc titles.
  5. 5A summary of the top gaps is posted to the team's Discord channel with a link to the full Notion page.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect DiscordCommunity channels + voice + bots.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect NotionPages, databases, comments.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.