🇬🇧 EN

🔔 Webhook Notification

Sends an HTTP POST request to an external URL with a JSON payload. Designed for fire-and-forget outbound notifications to third-party services, internal systems, or other automation platforms.

Category: Notifications & Messaging · Type identifier: webhook_notification

Overview

The Webhook Notification node is a lightweight way to push data from Flusso to any external system that accepts HTTP POST requests. It sends a JSON body and optionally includes custom headers (useful for authentication tokens or content-type overrides).

Unlike the HTTP Request node, Webhook Notification is purpose-built for outbound notifications. It does not parse or process the response body — if you need to read the response and use it in subsequent steps, use the HTTP Request node instead.

When to use Webhook Notification vs HTTP Request

Use case	Best node
Notify a service and move on (fire-and-forget)	Webhook Notification
Call an API and use the response in later steps	HTTP Request
Platform-specific webhooks (Slack, Discord)	Dedicated messaging nodes

Configuration

Field	Required	Description
URL	Required	The target webhook URL to POST to. Supports `{{ variable }}`.
Payload	Required	JSON payload to include in the request body. Supports `{{ variable }}` references anywhere in the JSON.
Headers	Optional	Custom HTTP request headers as key-value pairs. Use for authentication tokens or custom content types. Example: `Authorization: Bearer my_token`.
Timeout	Optional	Request timeout in seconds. If the external server does not respond within this time the step fails. Default: 10 seconds.

Output Data

Field	Type	Description
`status`	integer	The HTTP response status code returned by the external server (e.g. 200, 201, 404).
`ok`	boolean	`true` if the status code is in the 2xx range.
`response_body`	string	The raw response body text returned by the server. Available for logging or debugging purposes.

Example Usage

Notify an internal operations system whenever a new customer record is created. The payload includes the customer name and ID resolved from an earlier step.

-- URL -- https://ops.internal.example.com/hooks/new-customer -- Payload -- { "event": "customer.created", "customer_id": "{{ create_customer.output.id }}", "name": "{{ create_customer.output.name }}", "created_at": "{{ create_customer.output.created_at }}" } -- Headers -- Authorization: Bearer {{ trigger.output.api_key }}

Tips & Notes

If the receiving server requires HMAC signature verification, use the HTTP Request node instead — it gives you full control over the request.
Setting a reasonable Timeout prevents your workflow from hanging indefinitely if the external server is slow or unavailable.
Use the ok output in a subsequent Logic Gate node to branch on success or failure.
The node does not retry on failure by default. Add a retry pattern using a Loop and a Wait node if reliable delivery is required.

Related Nodes

Email Notification — send an email instead of an HTTP POST.
Emit Event — trigger other Flusso workflows rather than an external URL.
Slack Message — dedicated Slack integration with richer formatting options.