Route multi-channel approval requests via Slack, Teams, WhatsApp and email

Description

Quick overview This workflow exposes a webhook-based approval gateway that sends approval requests to Slack, Microsoft Teams, and WhatsApp via webhooks/APIs, collects approve/reject responses through resume links, applies a configurable decision policy with timeout/escalation, and returns the final verdict plus an audit trail to the caller. How it works Receives a POST request on the /approval-gateway webhook with approval details (subject, description, approvers, channels, policy, and timeouts). Validates the input, creates an approval session, and generates an HMAC-signed token used to protect approve/reject actions. Builds channel-specific messages for Slack (Block Kit), Microsoft Teams (Adaptive Card), WhatsApp Cloud API (interactive buttons), and an email-friendly HTML payload with approve/reject links. Sends the approval request to Slack and Microsoft Teams via incoming webhooks and to WhatsApp via the WhatsApp Cloud API. Waits for approvers to respond through the workflow resume URL or for the timeout path to trigger escalation. Verifies the signed token, aggregates decisions using the selected policy (any/all/majority/first), finalizes the status, and returns the final decision and full audit object in the webhook response. Setup Replace the signing secret in the workflow’s configuration with a long, random value to secure the HMAC-signed approval tokens. Create and paste your Slack Incoming Webhook URL and Microsoft Teams Incoming Webhook URL into the workflow configuration (or node URL fields). Configure WhatsApp Cloud API access by setting the Graph API messages endpoint (phone number ID) and a permanent access token in the workflow configuration/headers. Ensure the system that calls this workflow can POST the required JSON fields (at minimum subject and approvers) to the /approval-gateway webhook URL. An n8n automation workflow template by Oneclick AI Squad.

Community Metrics

Categories

• Automation

Tags

• n8n
• workflow
• http-request
• code

Capabilities

• 2 nodes

Information