Overview
The OmniFlow Trigger node listens for events from the OmniFlow platform via webhooks. It allows users to specify which OmniFlow events they want to receive and process within an n8n workflow. This node is useful for automating workflows based on real-time OmniFlow event data, such as triggering actions when specific business process events occur.
Common scenarios include:
- Automating notifications or updates when certain OmniFlow events happen.
- Integrating OmniFlow event data into other systems or databases.
- Reacting to changes in OmniFlow workflows without polling.
For example, a user can configure this node to listen for "Task Completed" or "Process Started" events and then trigger subsequent workflow steps like sending emails or updating CRM records.
Properties
Name | Meaning |
---|---|
Authentication | Method of authentication to connect with OmniFlow API. Options: Credentials (API key) or OAuth2 token. |
Event Names or IDs | Select one or multiple OmniFlow event names or IDs to listen for. Users can pick from a dynamically loaded list or specify IDs via expressions. |
Events Order | The order in which queued events are processed for a single webhook. Options: ASC (ascending), DESC (descending). |
Output
The node outputs the incoming webhook payload as JSON data under the json
field. Each execution returns an array containing one object representing the event data received from OmniFlow.
If the webhook receives binary data, it would be included accordingly, but based on the code, the output focuses on JSON event data.
Dependencies
- Requires access to the OmniFlow API.
- Needs either an API key credential or OAuth2 authentication configured in n8n.
- Uses the OmniFlow API endpoints
/hooks/triggers
to load available events and/hooks/new
to create webhooks. - The node depends on helper functions from a bundled module (
GenericFunctions
) to make authenticated API requests.
Troubleshooting
- Webhook creation failure: If the node cannot create a webhook, ensure that the provided credentials have sufficient permissions and the webhook URL is accessible from OmniFlow.
- Event loading issues: If the event list does not populate, verify network connectivity and that the API credentials are valid.
- Webhook not triggering: Confirm that the OmniFlow service is sending events to the correct webhook URL and that the selected events match those sent by OmniFlow.
- Authentication errors: Check that the chosen authentication method matches the configured credentials and that tokens or keys are current.
Links and References
- n8n Expressions Documentation
- OmniFlow API documentation (not publicly linked here; refer to your OmniFlow provider)
- n8n Webhook Node Guide: https://docs.n8n.io/nodes/n8n-nodes-base.webhook/