CHATBOTS

Weekly Knowledge Base Gap Digest to Slack

On a weekly schedule, summarizes the questions the helpdesk bot couldn't answer and the most down-voted topics, then posts a prioritized documentation to-do list to Slack.

CategoryChatbots
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule fires
  • ActionQuery unanswered questions and low ratingsSupabaseSupabase
  • ActionCluster and rank gapsOpenAI
  • LogicAnything worth reporting?
  • OutputPost gap digest to SlackSlack

What it does

Turns helpdesk usage data into an action plan for your docs team. Once a week the workflow pulls logged unanswered questions and low-rated answers from Supabase, clusters them by theme with OpenAI, and posts a ranked list of documentation gaps to a Slack channel so someone owns fixing them.

When to use it

When you're logging bot misses and feedback (see the escalation and feedback-logger templates) and want a recurring nudge to keep the knowledge base fresh. Best for teams who want proactive doc maintenance instead of waiting for repeat complaints.

How it works

  1. 1A weekly schedule triggers the digest.
  2. 2The flow queries Supabase for the past week's unanswered questions and down-voted answers.
  3. 3OpenAI clusters the items into themes and ranks them by frequency and severity.
  4. 4A logic step skips posting if there is nothing notable that week.
  5. 5A formatted digest with the top documentation gaps is posted to the Slack ops channel.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SupabaseTables, auth, storage, edge functions.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  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.