CHATBOTS

Slack Access Bot: Route High-Risk Requests to Approvers with Buttons

Sends access requests that fall outside auto-grant rules to the designated approver as an interactive Slack message, then provisions a GitHub team membership on approval.

CategoryChatbots
Enginesim
Difficultyintermediate
Triggerwebhook
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNeeds-approval access request event receivedHTTP webhook
  • ActionResolve approver and target GitHub team from matrixCodaCoda
  • ActionSend interactive Approve/Deny card to approverSlack
  • LogicBranch on button: Approve provisions, Deny halts
  • ActionAdd requester to GitHub team on approvalGitHubGitHub
  • OutputConfirm grant in requester's original threadSlack

What it does

Handles the requests the entitlement matrix marks as approval-required. The bot identifies the system owner from the matrix, DMs them an interactive Approve/Deny card with full context, and on approval adds the requester to the matching GitHub team — closing the loop without anyone touching the org settings page.

When to use it

Use it for medium- and high-risk access (production repos, admin groups) where a human must sign off but you still want zero-friction execution once they click Approve. Pairs well with the auto-resolver for low-risk tiers.

How it works

  1. 1An access request event arrives (from a form or the helpdesk bot) tagged needs-approval.
  2. 2The matrix is queried for the system's designated approver and the target GitHub team.
  3. 3The approver gets an interactive Slack card with requester, system, and reason.
  4. 4A branch waits on the button: Approve provisions, Deny stops.
  5. 5On Approve the requester is added to the GitHub team via the org API.
  6. 6The bot confirms the grant back to the requester's original thread.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SlackChannels, DMs, threads, mentions.
  2. 2
    Connect CodaDocs, packs, automations.
  3. 3
    Connect GitHubRepos, issues, pull requests, actions.
  4. 4
    Connect HTTP webhookTrigger any URL on agent actions.
  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.