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 contacts, campaigns, tags, and more. Specifically, for the Contact - Delete operation, it enables deleting a contact from the 4leads system. This is useful in scenarios where you want to remove outdated or incorrect contact information from your marketing or CRM database.
Practical examples include:
- Automatically removing unsubscribed or bounced email contacts.
- Cleaning up test or duplicate contacts after data import.
- Managing contact lifecycle by deleting contacts no longer relevant to your campaigns.
Properties
| Name | Meaning |
|---|---|
| Contact | Select the contact to delete. You can choose a contact either from a searchable list or specify its ID directly. |
Additionally, there is a notice property (informational) indicating that the contact's email can be used as an alternative identifier when performing update, delete, or tag operations on contacts.
Output
The node outputs a JSON array containing the result(s) of the delete operation. Typically, this will include confirmation details about the deleted contact or status messages returned by the 4leads API.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the 4leads API via an API key credential configured in n8n.
- The node depends on internal handlers for managing contacts (
contactHandler), which interact with the 4leads API endpoints. - Proper permissions on the 4leads account are necessary to perform delete operations on contacts.
Troubleshooting
Common issues:
- Attempting to delete a contact that does not exist or has already been deleted may result in errors.
- Insufficient API permissions or invalid API credentials will cause authentication failures.
- Network connectivity problems can prevent successful API calls.
Error messages and resolutions:
- "Contact not found": Verify the contact ID or selection method; ensure the contact exists in 4leads.
- "Authentication failed": Check that the API key credential is correctly set up and has required permissions.
- Timeout or network errors: Confirm internet connectivity and 4leads service availability.
Links and References
- 4leads Official Documentation (for API details and contact management)
- n8n Documentation on Creating Custom Nodes