Before
A person likely had to send or coordinate the approval request, monitor Slack for the reviewer’s response, and determine whether the response meant approval or denial. They then had to post or communicate the resulting status update manually.
How it works
- Receive an approval request and send it to Slack for reviewer action.
- Capture and parse the reviewer’s Slack response, then check whether it is Approve or Deny.
- Post the corresponding approval or denial update in Slack.
Workflow details
- Approval request delivery: An incoming approval request starts the workflow, which sends an interactive approval request to Slack and provides a way for the response to return to the flow.
- Response capture: When a reviewer interacts with the Slack message, the workflow receives the response and parses the incoming payload into usable decision data.
- Decision routing: The automation checks whether the reviewer selected Approve or Deny and follows the matching path without requiring someone to interpret or forward the response manually.
- Status communication: The workflow posts a Slack message reflecting the selected approval outcome, creating a clear status update for the relevant conversation or channel.
What changed
The reviewer still makes the approval decision, but the request delivery, response capture, decision check, and status notification now happen automatically through Slack. The outcome is posted as soon as the response is received instead of requiring a separate manual follow-up.
Work removed
Sending or coordinating the approval request, monitoring for the Slack response, interpreting the Approve or Deny selection, routing the decision, and posting the resulting status update.
Expected outcome
At least two recurring coordination actions per request—manual response routing and manual status notification—are removed, while the human approval decision remains in place.
