Overview
This node triggers a workflow when it receives an HTTP request on a dynamically generated webhook URL. It listens for incoming HTTP requests using either the GET or POST method, as configured by the user. This is useful for scenarios where you want to start a workflow based on external events sent via webhooks, such as receiving transcription data from a third-party service or any other event notification.
Practical examples include:
- Starting a workflow when a transcription service posts new transcription results.
- Triggering automation when an external system sends a GET or POST request with relevant data.
Properties
| Name | Meaning |
|---|---|
| HTTP Method | HTTP method to listen for: GET or POST |
Output
The node outputs the data received in the webhook request as JSON under the json field. Specifically, the entire body of the incoming HTTP request is passed through as the output data, allowing subsequent nodes to process this information.
No binary data output is produced by this node.
Dependencies
- Requires the ability to expose a webhook endpoint accessible by external services.
- No external API keys or credentials are needed.
- The node internally generates a unique random webhook path to avoid collisions and ensure security.
Troubleshooting
- Webhook not triggering: Ensure that the external service is sending requests to the correct dynamically generated webhook URL. The URL includes a random path segment generated by the node.
- Incorrect HTTP method: Verify that the HTTP method used by the external service matches the one configured in the node (GET or POST).
- Empty or missing data: Confirm that the external service sends data in the request body; otherwise, the node will output empty JSON.
- Access issues: Make sure the webhook URL is publicly accessible if the workflow is running on a server behind firewalls or NAT.