DEVOPS

Route blocked images through a Slack approval before promotion

When an image fails the CVE gate, posts an interactive approval request to a Slack security channel.

CategoryDevOps
Enginesim
Difficultyintermediate
Triggerwebhook
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWebhook: failed-scan payload from CIHTTP webhook
  • ActionPost approval request to Slack security channelSlack
  • LogicBranch: approved, denied, or timed out?
  • ActionPromote image and log time-boxed exceptionSlack
  • OutputNotify requester of final decisionSlack

What it does

Adds a human override to the automated gate. Not every Critical CVE is exploitable in your context, so this lets a security approver consciously waive a finding in Slack instead of forcing an out-of-band manual deploy.

When to use it

Use it when a hard block is too rigid — you want the gate to stay strict by default but allow an accountable, audited exception path for false positives or accepted risk.

How it works

  1. 1A webhook trigger receives a failed-scan payload from your CI gate (image, CVE IDs, requester).
  2. 2An action posts an interactive Slack message to the security channel with Approve and Deny buttons and the CVE details.
  3. 3A logic branch waits for and routes on the approver's choice.
  4. 4On approval, an action promotes the image to staging and records the exception with approver, reason, and expiry.
  5. 5On denial or timeout, an output action notifies the requester in Slack that the image stays blocked, with the logged rationale.

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
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    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.