Slack and Code: Human Approval Gate Before API Call Template

This Spojit template pauses an inbound request, notifies approvers in Slack, and only on approval calls the protected downstream API.

What It Builds

A Webhook trigger receives an inbound request, a Slack Connector node posts the details to a review channel, and a Human approval node pauses the run until an approver responds in the Approvals inbox. Only when the request is approved does a Connector node on the http connector use http-post to call the protected downstream action. A rejection or timeout halts the workflow before any external call is made.

The Prompt

Paste this into Miraxa and it builds the workflow, connecting the tools for you:

Build a workflow with a Webhook trigger that receives a request. Post a message to the #approvals Slack channel summarizing the request, then add a Human approval node that pauses until someone approves. On approval, use the http connector to send an http-post to https://api.example.com/v1/action with the request body, passing the API key in the Authorization header.

Connectors Used

Webhook trigger - receives the inbound request that needs sign-off.
slack - posts the request summary to a review channel with send-message.
http - calls the protected downstream REST API with http-post once approved.

Customize It

Change the Slack channel name, the summary fields drawn from {{ input }}, the target URL and HTTP method (swap http-post for http-put or http-patch), and add a Timeout (minutes) on the Human node so stale requests auto-reject. Set the approval slots in the node's properties panel to the user, role, or team that should sign off.

Tips

A rejection or timeout halts the run, so the http-post never fires: there is no "on reject" branch to build.
Use Direct mode on both Connector nodes since the Slack post and the API call are single, predictable tool calls with no AI cost.
Store the API key in a connection, not in the prompt, and reference it in the Authorization header field of the http-post node.