ENGINEERING

Confirm reviewer acknowledgment when a PR review is requested

Fires the moment GitHub requests a review, immediately DMs the chosen reviewer an acknowledgment prompt on Slack, and if they don't react within the window.

CategoryEngineering
Enginesim
Difficultyadvanced
Triggerwebhook
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerGitHub webhook fires on review_requestedGitHubGitHub
  • ActionDM the reviewer a Slack acknowledgment promptSlack
  • LogicWait the grace period and check for an ack reaction
  • ActionRequest a backup reviewer on the PR if no ackGitHubGitHub
  • OutputNotify the channel that review was reassignedSlack

What it does

Closes the gap between assigning a reviewer and that reviewer actually noticing. It reacts in real time to a review-request event, asks the reviewer to acknowledge, and if no ack lands in the grace period it reassigns to a backup so the PR never silently waits on someone who's out or heads-down.

When to use it

When review delays usually come from reviewers simply not seeing the request, or when a reviewer is frequently OOO. Best for teams with on-call or round-robin review rotations that need a fast failover.

How it works

  1. 1A GitHub webhook fires on a `review_requested` event.
  2. 2The flow DMs the requested reviewer a Slack message asking them to react to acknowledge.
  3. 3A logic step waits the grace period and checks for the acknowledgment reaction.
  4. 4If acknowledged, the run ends quietly.
  5. 5If not, it requests a backup reviewer on the GitHub PR and notifies the channel that review was reassigned.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GitHubRepos, issues, pull requests, 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.