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, specifically supporting various resources including Opt-In management. The "Send" operation under the Opt-In resource allows users to send an opt-in confirmation or notification related to a specific opt-in entry and contact.
Common scenarios for this node include:
- Sending opt-in confirmations to contacts who have subscribed to a mailing list or service.
- Managing consent workflows by triggering opt-in notifications programmatically.
- Automating communication flows where explicit user consent is required before further engagement.
For example, after a user signs up on a website, this node can be used to send them an opt-in confirmation email via 4leads, ensuring compliance with consent regulations.
Properties
| Name | Meaning |
|---|---|
| Opt-In | Select the opt-in entry to send the notification for. Options: select from a list of opt-ins or specify an opt-in ID (numeric). |
| Notice | Informational notice that the email of a contact can be used as an alternative identifier. |
| Contact | Select the contact to whom the opt-in notification will be sent. Options: select from a list of contacts or specify a contact ID. |
Output
The node outputs a JSON array containing the results of the send operation. Each item in the output corresponds to the response from the 4leads API regarding the opt-in send action. The exact structure depends on the API response but typically includes status information about the sending process.
No binary data output is indicated in the source code.
Dependencies
- Requires an active connection to the 4leads API using an API key credential configured in n8n.
- The node relies on internal handlers (
optinHandler) to perform the send operation, which interacts with the 4leads backend. - Proper configuration of the 4leads API credentials within n8n is necessary for authentication.
Troubleshooting
- Invalid Opt-In ID: If the provided opt-in ID does not match the expected numeric format, the node will reject it. Ensure the ID is numeric.
- Contact Not Found: Selecting a contact that does not exist or is not accessible may cause errors. Verify the contact exists in 4leads.
- API Authentication Errors: Missing or invalid API credentials will prevent the node from executing successfully. Confirm the API key is correctly set up.
- Network Issues: Connectivity problems with the 4leads API endpoint can cause timeouts or failures. Check network access and API availability.
- Empty Input Data: If no input data is provided, the node may not perform any actions. Ensure input items are passed into the node.
Links and References
- 4leads Official Website — For more information about the platform.
- 4leads API Documentation — To understand API endpoints and request/response formats.
- n8n Documentation on Creating Custom Nodes — For guidance on node development and usage.