CHATBOTS

Escalate Doc Gaps from Discord to Linear

When the concierge cannot answer a Discord setup question from existing docs, it flags the gap in the channel and opens a Linear issue so the docs team can fill the missing…

CategoryChatbots
Enginepaperclip
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew message in Discord help channelDiscordDiscord
  • ActionSearch Notion docs for a confident answerNotionNotion
  • LogicBranch on retrieval confidence
  • OutputPost follow-up promise in DiscordDiscordDiscord
  • ActionOpen Linear docs-gap issueLinearLinear

What it does

Catches the setup questions your knowledge base cannot answer. When a member's Discord question has no good match in your docs, the bot posts an honest "a human will follow up" reply and files a Linear issue capturing the question, so your docs backlog grows from real community demand instead of guesswork.

When to use it

Use this alongside your concierge bot to turn unanswered questions into a prioritized documentation backlog. Ideal for teams who want their docs roadmap driven by what members actually struggle with during onboarding.

How it works

  1. 1A new Discord message triggers the flow.
  2. 2The agent searches the Notion docs for a confident answer.
  3. 3A logic branch checks the retrieval confidence: if a match exists, the flow ends quietly (handled elsewhere).
  4. 4If no confident match is found, the agent acknowledges the member in Discord and promises follow-up.
  5. 5A Linear issue is created with the verbatim question, channel link, and a "docs-gap" label for triage.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect DiscordCommunity channels + voice + bots.
  2. 2
    Connect NotionPages, databases, comments.
  3. 3
    Connect LinearIssues, projects, cycles, triage.
  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.