CHATBOTS

Triage Discord access requests by risk and auto-route to approval or ticket

Handles /access slash-command requests in Discord by classifying the resource's risk level.

CategoryChatbots
EngineSim + Paperclip
Difficultyintermediate
Triggerevent
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerEmployee runs /access slash commandDiscordDiscord
  • ActionLook up system risk tier in Confluence policyConfluenceConfluence
  • ActionClassify request risk with OpenAIOpenAI
  • LogicBranch on low-risk vs sensitive
  • ActionCreate Linear approval ticket for approverLinearLinear
  • OutputReply with self-serve steps or pending statusDiscordDiscord

What it does

Turns the chaotic "can someone give me access to X?" Discord thread into a structured intake. An employee runs a slash command naming the system they need, the bot looks up that system's risk tier in your access policy docs, and decides whether it can be acknowledged immediately or needs human sign-off.

When to use it

Use this when access requests pour into Discord and your team manually decides every time who needs to approve. It enforces your policy consistently: routine, low-risk tools get a fast acknowledgment, while anything sensitive lands in a tracked approval queue.

How it works

  1. 1An employee invokes the `/access` slash command in Discord with the system name and reason.
  2. 2The bot queries Confluence access-policy pages to find the requested system's risk tier and approver.
  3. 3An OpenAI call normalizes the request and classifies it as low-risk or sensitive.
  4. 4A logic branch splits on the risk classification.
  5. 5Low-risk requests get an immediate acknowledgment with the self-service steps.
  6. 6Sensitive requests create a Linear approval ticket assigned to the named approver, and the user is told it's pending review.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect DiscordCommunity channels + voice + bots.
  2. 2
    Connect ConfluenceSpaces, pages, blueprints.
  3. 3
    Connect OpenAIModels, embeddings, files.
  4. 4
    Connect LinearIssues, projects, cycles, triage.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    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.