Webhook Listener
Start a workflow when an HTTP request arrives at a unique webhook URL.
The Webhook Listener is a trigger node that starts a workflow execution when an incoming HTTP request hits a unique URL. It supports method filtering, authentication via HMAC signatures or JWT tokens, and two response modes for synchronous or asynchronous processing.
Configuration
| Field | Type | Required | Description |
|---|---|---|---|
| Enabled | Toggle | No | Whether the webhook accepts incoming requests. Defaults to on. |
| Webhook Path | Text | Yes | The unique path segment for this webhook. The full URL is displayed as a read-only field below and can be copied to the clipboard. |
| Accepted Method | Select | No | Which HTTP method to accept: POST, GET, PUT, or Any Method. Defaults to POST. |
| Response Mode | Select | No | How the webhook responds to callers. Immediate returns 202 Accepted right away and runs the workflow in the background. Wait for Completion holds the connection open until the workflow finishes and returns the final output. Defaults to Immediate. |
| Authentication | Select | No | Auth scheme: None, HMAC Signature, or JWT Bearer Token. Defaults to None. |
| HMAC Secret | Text | No | Shared secret for HMAC signature verification. Only shown when auth is HMAC Signature. Incoming requests must include a valid HMAC signature header. |
| JWT Secret / Public Key | Text | No | Secret or public key for JWT validation. Only shown when auth is JWT Bearer Token. Incoming requests must include a valid JWT in the Authorization header. |
Webhook URL
Once you set a webhook path, Buildorado generates the full URL automatically:
https://your-domain.com/api/triggers/webhook/{path}Click the copy button next to the URL field to copy it to your clipboard for pasting into external services.
Output
| Field | Type | Description |
|---|---|---|
| method | string | The HTTP method of the incoming request (e.g., POST). |
| headers | object | All request headers as key/value pairs. |
| body | object | The parsed request body (JSON). |
| query | object | Query string parameters as key/value pairs. |
| path | string | The webhook path that was matched. |
Example
A workflow that receives order notifications from a payment provider:
- Webhook Listener -- Path:
orders-webhook, Method: POST, Auth: HMAC Signature with a shared secret. Response mode: Immediate. - If/Else -- Check
webhookTrigger_1.body.eventequalspayment.completed. - HTTP Request -- Fetch full order details from the payment API using
webhookTrigger_1.body.orderId. - Send Email -- Notify the fulfillment team.
For synchronous integrations where the caller expects a custom response, set the response mode to "Wait for Completion" and add a Webhook Response node at the end of the workflow.