Route notifications across WhatsApp, Slack, email and SMS via a webhook

Quick overview

This workflow receives a notification request via webhook, enriches it with recipient context, selects the best delivery channel (WhatsApp, Slack, Email, or SMS) using an external decision endpoint plus local heuristics, sends the notification through an HTTP API, logs the outcome, and returns a detailed delivery report.

How it works

1. Receives a POST request on a webhook endpoint containing recipient details, message content, priority, and optional channel preferences.
2. Validates required fields, enriches the payload with defaults (priority-based channel order and quiet hours), and prepares the context and endpoint URLs.
3. Calls an HTTP endpoint to fetch additional recipient and channel context such as preferences, recent activity, and delivery history.
4. Calls an HTTP decision endpoint to select an optimal channel and ordered fallbacks based on priority, message type, quiet hours, and preferences.
5. Sends the notification by calling an HTTP endpoint representing the chosen delivery channel and then calls another HTTP endpoint to log the decision and delivery outcome.
6. Builds a consolidated report that includes the channel decision, confidence/reasoning, send/log status codes, and recommendations, and returns it to the original webhook caller.

Setup

1. Configure the webhook URL (path /notify-intel) in the system that will send notification requests to this workflow.
2. Replace the placeholder httpbin.org URLs for context fetch, decision engine, sending, and logging with your real HTTP endpoints (or add the required credentials if those endpoints require authentication).
3. Ensure incoming webhook payloads include at least recipientId and message, and provide channel addresses under channels (for example whatsapp, slack, email, sms) so the workflow has valid delivery options.