CHATBOTS

Emergency Feature Flag Kill Switch with Slack Confirmation Gate

An incoming webhook proposes disabling a flag; the bot posts a confirmation in the incident channel and only flips the flag to 0% after a human approves.

CategoryChatbots
Enginepaperclip
Difficultyintermediate
Triggerwebhook
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerKill-switch webhook receivedHTTP webhook
  • ActionRead current flag exposurePostgreSQLPostgres
  • LogicPost confirmation card and gate on human approvalSlack
  • ActionSet flag to 0% and write audit rowPostgreSQLPostgres
  • OutputConfirm or report cancellation in channelSlack

What it does

Provides a fast but accountable emergency kill switch for feature flags. An external system (alerting, on-call tooling) fires a webhook naming the flag to disable. Instead of silently flipping it, the bot posts a confirmation prompt in the incident channel showing the current exposure, and waits for an explicit human approve/deny before setting the flag to 0%.

When to use it

During incidents when you need to disable a risky flag in seconds but still want a human in the loop and a clean audit record of who pulled the trigger.

How it works

  1. 1An HTTP webhook arrives with the flag key and a reason from your alerting system.
  2. 2The bot reads the flag's current rollout percentage from Postgres to show the blast radius being killed.
  3. 3It posts an approve/deny confirmation card to the incident Slack channel.
  4. 4On approval it sets the flag to 0% in Postgres and stamps an audit row with approver and reason.
  5. 5It confirms the kill in-channel; on deny or timeout it leaves the flag untouched and says so.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect HTTP webhookTrigger any URL on agent actions.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  3. 3
    Connect PostgresAny Postgres URL — query, write, migrate.
  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.