Actions48
- Custom Variable Actions
- Custom Variable Group Actions
- Event Actions
- Integration Actions
- Lead Actions
- Lead List Actions
Overview
This node operation deletes a specific lead list identified by its unique List ID. It is useful in scenarios where you want to remove an entire list of leads from your system, for example, when a campaign ends or when cleaning up outdated or irrelevant lead data.
Practical examples:
- Automatically deleting a lead list after a marketing campaign finishes.
- Removing test or temporary lead lists created during development or testing phases.
- Cleaning up lead lists that no longer meet certain criteria or compliance requirements.
Properties
| Name | Meaning |
|---|---|
| List ID | Unique identifier of the list to delete |
Output
The output JSON will typically contain confirmation details about the deletion operation. This may include success status, deleted list ID, or any relevant metadata returned by the API indicating the result of the delete request.
No binary data output is expected from this operation.
Dependencies
- Requires an API key credential or similar authentication token configured in n8n to authorize requests to the external service's API.
- The node makes HTTP DELETE requests to the external service endpoint responsible for managing lead lists.
- Network connectivity to the external API endpoint is necessary.
Troubleshooting
Common issues:
- Invalid or missing List ID: Ensure the List ID provided exists and is correctly formatted.
- Authentication errors: Verify that the API key or authentication credentials are valid and have sufficient permissions.
- Network timeouts or connectivity issues: Check network access and API availability.
- Attempting to delete a list that does not exist or has already been deleted.
Error messages:
- "List not found" or similar indicates the List ID does not correspond to any existing list.
- "Unauthorized" or "Authentication failed" suggests invalid or missing credentials.
- Timeout errors indicate network or server responsiveness problems.
Resolving these usually involves verifying input parameters, checking credentials, and ensuring stable network connections.
Links and References
- Refer to the external service’s official API documentation for lead list management and deletion endpoints.
- n8n documentation on configuring API credentials and HTTP Request nodes for further customization.