Actions33
- Campaign Actions
- Contact Actions
- Field Actions
- Opt-In Actions
- Opt-in-Case Actions
- Sign in Form Actions
- Storage-Field Actions
- Tag Actions
Overview
This node integrates with the 4leads platform, allowing users to manage various marketing and contact-related resources. Specifically, for the Opt-In resource with the Opt-Out operation, it enables marking a contact as opted out from communications or marketing campaigns. This is useful in scenarios where compliance with email marketing regulations (like GDPR or CAN-SPAM) is required, ensuring that contacts who no longer wish to receive messages are properly excluded.
Practical examples include:
- Automatically opting out contacts who unsubscribe via a form.
- Managing opt-out status during bulk contact updates.
- Syncing opt-out preferences between 4leads and other systems.
Properties
Name | Meaning |
---|---|
Contact | Select a contact to opt out. You can choose a contact either by selecting from a list of existing contacts or by providing the contact's ID directly. |
Additionally, there is a notice property displayed as information:
- "The email of a contact can be used as an alternative ID." — indicating that the contact's email may serve as an identifier if needed.
Output
The node outputs JSON data representing the result of the opt-out operation. This typically includes confirmation details about the contact's updated opt-out status. The exact structure depends on the 4leads API response but generally contains fields such as contact identifiers and status flags.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the 4leads service via an API key credential configured in n8n.
- The node depends on the 4leads API endpoints for managing contacts and their opt-in/opt-out statuses.
- Proper permissions on the 4leads account to modify contact opt-in states are necessary.
Troubleshooting
Common issues:
- Providing an invalid or non-existent contact ID will cause the operation to fail.
- Missing or incorrect API credentials will prevent communication with 4leads.
- Network connectivity problems can interrupt the request.
Error messages and resolutions:
- "Contact not found" — Verify the contact ID or selection is correct.
- "Authentication failed" — Check that the API key credential is valid and has sufficient permissions.
- "Request timeout or network error" — Ensure stable internet connection and that 4leads API is reachable.
Links and References
- 4leads Official Website
- 4leads API Documentation (for detailed API usage and response formats)
- Relevant email marketing compliance guidelines (e.g., GDPR, CAN-SPAM) for understanding opt-out requirements.