Overview
This node acts as a webhook trigger for WOZTELL events, allowing workflows to start when specific events are received via HTTP POST requests. It is useful for integrating WOZTELL messaging platform events into n8n automation workflows without polling or manual intervention.
Common scenarios include:
- Automatically processing incoming messages or notifications from WOZTELL.
- Filtering events by channel ID or event type to trigger workflows only on relevant data.
- Building custom integrations that react in real-time to WOZTELL activity.
For example, you could use this node to start a workflow whenever a new message arrives on a particular WOZTELL channel, then process or route that message automatically.
Properties
| Name | Meaning |
|---|---|
| Webhook Path | The URL path segment where the webhook listens for incoming POST requests. |
| Event | The type of event to listen for; currently only "WOZTELL Event" is supported. |
| Filter Fields | Optional filters to restrict which events trigger the workflow: |
| - Channel ID | Only trigger if the incoming event's channelId matches this value (string). |
| - Event Type | Only trigger if the incoming event's eventType matches this value (string). |
Output
The node outputs the full JSON payload received from the webhook request in the json field of the output items. This payload represents the WOZTELL event data sent to the webhook.
No binary data output is produced by this node.
Dependencies
- Requires an active HTTP endpoint exposed by n8n to receive webhook POST requests.
- No external API keys or credentials are needed for this node itself, but WOZTELL must be configured to send events to the webhook URL.
- The user must configure the webhook path and ensure WOZTELL sends events to the correct URL.
Troubleshooting
- ChannelId is not valid: If a Channel ID filter is set and the incoming event's
channelIddoes not match, the node responds with HTTP 400 and throws an error. Verify the filter value matches the expected channel ID exactly. - EventType is not valid: Similarly, if an Event Type filter is set and the incoming event's
eventTypedoes not match, a 400 error is returned. Check the spelling and case of the event type filter. - Webhook not triggering: Ensure WOZTELL is correctly configured to send events to the webhook URL including the specified path.
- Empty or malformed payloads: The node expects JSON body data. If the webhook receives invalid JSON or no data, the workflow may not trigger properly.
Links and References
- n8n Webhook Documentation
- WOZTELL Official Website (for configuring event webhooks)