Overview
This node registers an event indicating that a specific contact has entered a workflow. It is useful for tracking and logging when contacts begin interacting with automated processes, enabling better monitoring and analysis of workflow engagement.
Practical examples include:
- Marking the start of a customer journey in a marketing automation system.
- Logging entry points for contacts in a CRM workflow.
- Triggering downstream actions or analytics based on workflow entry events.
Properties
| Name | Meaning |
|---|---|
| Contact ID | The ID of the contact involved in this event |
Output
The node outputs JSON data representing the response from the external service after registering the event. Each output item corresponds to an input item and contains the server's response data under the json field.
If an error occurs during the event registration and the node is set to continue on failure, the output will contain an error field with the error message instead.
No binary data is produced by this node.
Dependencies
- Requires an API key credential for authentication with the external service.
- Uses Axios HTTP client to send POST requests to the external API endpoint
/events. - The external API base URL and API key must be configured in the node credentials.
Troubleshooting
Common issues:
- Invalid or missing API key credential will cause authentication failures.
- Incorrect Contact ID values may result in errors or no event being registered.
- Network connectivity problems can prevent successful API calls.
Error messages:
- Errors returned from the external API are captured and thrown as node errors unless "Continue On Fail" is enabled.
- If "Continue On Fail" is enabled, errors are included in the output JSON under the
errorproperty for each failed item.
To resolve errors:
- Verify that the API key and base URL are correctly configured.
- Ensure the Contact ID is valid and exists in the external system.
- Check network connectivity and firewall settings.
Links and References
- Axios HTTP Client
- Documentation for the external API (not provided in source code) would be needed for detailed event registration parameters and responses.
