Actions33
- Campaign Actions
- Contact Actions
- Field Actions
- Opt-In Actions
- Opt-in-Case Actions
- Sign in Form Actions
- Storage-Field Actions
- Tag Actions
Overview
The node integrates with the 4leads platform, allowing users to interact with various resources such as campaigns, contacts, tags, opt-ins, and more. Specifically, for the Campaign - Start operation, it enables starting a campaign for a selected contact. This is useful in marketing automation scenarios where you want to trigger a campaign workflow or sequence for a particular contact programmatically.
Practical examples include:
- Automatically enrolling a new lead into a drip email campaign.
- Restarting a campaign for a contact based on certain triggers or events.
- Managing campaign participation dynamically from other workflows.
Properties
| Name | Meaning |
|---|---|
| Campaign | Select the campaign to start. You can choose from a searchable list of campaigns or specify the campaign by its numeric ID. |
| Notice | Informational text indicating that the contact's email can be used as an alternative identifier. (Display only) |
| Contact | Select the contact for whom the campaign should be started. Choose from a searchable list of contacts or specify by ID. |
Output
The node outputs a JSON array containing the results of the campaign start operation. Each item in the output corresponds to the processed input item and typically includes details about the campaign start action performed for the specified contact.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating with the 4leads service.
- The node depends on the 4leads API endpoints to fetch campaigns, contacts, and to start campaigns.
- Proper configuration of the API credential within n8n is necessary for successful execution.
Troubleshooting
- Invalid Campaign ID: If the campaign ID does not match the expected numeric format, the node will reject it. Ensure the campaign ID is numeric if entered manually.
- Contact Not Found: Selecting a contact that does not exist or is not accessible via the API may cause errors. Use the provided search list to select valid contacts.
- API Authentication Errors: Missing or invalid API credentials will prevent the node from connecting to 4leads. Verify the API key is correctly configured.
- Network Issues: Connectivity problems with the 4leads API can cause timeouts or failures. Check network access and API status.
- Empty Input Data: If no input items are provided, the node will not perform any operations.
Links and References
- 4leads Official Website — For general information about the platform.
- 4leads API Documentation (not publicly linked here) — Consult your 4leads account or support for API details relevant to campaign management.