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 resources such as campaigns, contacts, opt-ins, and more. Specifically, for the Opt-In resource with the Delete operation, the node deletes a selected opt-in entry from the 4leads system.
Common scenarios where this node is beneficial include:
- Cleaning up outdated or invalid opt-in records.
- Managing user consent by removing opt-ins that are no longer valid or requested.
- Automating data hygiene processes in marketing workflows.
For example, a marketing automation workflow could use this node to delete an opt-in record when a user unsubscribes or revokes consent.
Properties
| Name | Meaning |
|---|---|
| Opt-In | Select the opt-in to delete. You can choose from: - A list of existing opt-ins (searchable) - Specify the opt-in by its numeric ID |
Output
The node outputs a JSON array containing the result(s) of the delete operation. Each item in the output corresponds to the response from the 4leads API after attempting to delete an opt-in. The exact structure depends on the API response but typically includes confirmation of deletion or error details if the operation failed.
No binary data output is produced by this node.
Dependencies
- Requires an active connection to the 4leads platform via an API key credential configured in n8n.
- The node depends on the 4leads API being accessible and the provided API key having sufficient permissions to delete opt-in records.
Troubleshooting
- Invalid Opt-In ID: If the provided opt-in ID does not match any existing record, the node may return an error indicating the opt-in was not found. Verify the ID is correct and exists in 4leads.
- Authentication Errors: If the API key is missing, expired, or lacks proper permissions, authentication errors will occur. Ensure the API key credential is correctly set up and has delete permissions.
- Network Issues: Connectivity problems with the 4leads API can cause timeouts or failures. Check network connectivity and API status.
- Validation Errors: The opt-in ID must be numeric; providing non-numeric values will trigger validation errors before the request is sent.
Links and References
- 4leads Official Documentation (for API details and authentication)
- n8n Documentation on Creating Custom Nodes