Event Trigger - UNEXO

Node to trigger on an event condition

Overview

This node acts as a webhook trigger that listens for incoming HTTP POST requests on a specified path. It is designed to start workflows when an event occurs and the external system sends data to the configured webhook URL. The node validates the request method and authorization token before triggering the workflow.

Common scenarios include:

Integrating with external services that send event notifications via webhooks.
Automating processes based on real-time events, such as updates from third-party APIs or custom applications.
Receiving data payloads that initiate downstream processing in n8n.

For example, you might configure this node to listen for order creation events from an e-commerce platform that posts order details to your webhook URL, triggering order fulfillment workflows.

Properties

Name	Meaning
workfowPath	The URL path segment where the webhook listens for incoming POST requests. This must be unique per workflow and is required.

Output

The node outputs the JSON body of the incoming POST request as an array of JSON objects under the json field. This means the data sent by the external service to the webhook is directly passed into the workflow for further processing.

No binary data output is produced by this node.

Example output structure:

[
  {
    "key1": "value1",
    "key2": "value2",
    ...
  }
]

Dependencies

Requires an environment variable named UNEXO_Event_Trigger_Token which holds the bearer token used to authenticate incoming webhook requests.
The external service sending the webhook must include this token in the Authorization header as Bearer <token>.
No additional API keys or credentials are needed within n8n beyond this environment variable.

Troubleshooting

Error: Only POST requests are allowed for this webhook.
This error occurs if the webhook receives a request with any HTTP method other than POST. Ensure the external service sends POST requests.
Error: Invalid authorization token
This indicates the Authorization header in the incoming request does not match the expected bearer token set in the environment variable. Verify that the external service includes the correct token and that the environment variable is properly configured in n8n.
Webhook path conflicts or registration issues
Since the webhook path must be unique, ensure no other workflow uses the same path. If the webhook is not triggering, check that it is registered and active.