Overview
This node acts as a trigger for workflows based on events from the 4leads platform, specifically focusing on campaign-related events. It continuously polls the 4leads API to detect new automation events and starts the workflow when such events occur. This is useful for automating processes that depend on real-time updates from 4leads campaigns, such as lead management, notifications, or data synchronization.
Practical examples:
- Automatically updating a CRM system when a new lead event occurs in a 4leads campaign.
- Sending notifications or emails triggered by specific campaign events.
- Logging or analyzing campaign event data as soon as it happens.
Properties
| Name | Meaning |
|---|---|
| Trigger On | The type of event to trigger on. Currently supports "4leads Campaign" events only. |
| Select an Automation | Choose a specific 4leads automation (campaign) to monitor for events. |
Output
The node outputs an array of JSON objects representing the new events detected from the selected 4leads automation. Each object corresponds to an event with its associated data as returned by the 4leads API.
The output JSON structure includes at least:
eventId: A unique identifier for the event.- Other event-specific fields as provided by the 4leads API under the
resultsarray.
No binary data output is produced by this node.
Dependencies
- Requires an active API key credential for the 4leads service to authenticate requests.
- Needs network access to the 4leads API endpoint:
https://api.4leads.eu/v1/automations/poll/{automationId}. - Uses n8n's polling mechanism to periodically check for new events.
Troubleshooting
- No automation ID provided: The node will throw an error if no automation is selected. Ensure you select a valid automation before running.
- No API credentials found: The node requires a valid API key credential for 4leads. Verify that the credential is configured correctly in n8n.
- Empty or missing events: If no new events are detected, the node returns no data. Confirm that the selected automation has recent events.
- API request failures: Network issues or invalid API keys can cause request errors. Check connectivity and credential validity.
- Event ID tracking: The node tracks the last processed event ID to avoid duplicates. If events are missed, consider resetting the node’s static data or reviewing API response consistency.
Links and References
- 4leads API Documentation (assumed official docs for further details)
- n8n documentation on Creating Triggers