Actions29
Overview
This node integrates with the BookedIn API to manage various entities such as agents, leads, lists, strategies, campaigns, and human messages. Specifically for the Lead - Delete operation, it allows users to delete a lead by specifying its unique Lead ID.
Common scenarios where this node is beneficial include:
- Cleaning up outdated or incorrect lead data from your CRM system.
- Automating lead lifecycle management by removing leads that no longer qualify.
- Integrating lead deletion into broader workflows, such as after a lead conversion or disqualification.
Practical example:
- A sales automation workflow that removes leads marked as duplicates or invalid automatically by deleting them from the BookedIn system using their Lead ID.
Properties
| Name | Meaning |
|---|---|
| Lead ID | The unique identifier of the lead to delete (e.g., ld_f1e2d3c4b5a6). This is required to specify which lead should be deleted. |
Output
The output JSON contains the response from the BookedIn API after attempting to delete the specified lead. Typically, for a successful delete operation, the API may return an empty object or confirmation message indicating the lead was removed.
If the operation fails, the output will contain an error message describing the issue.
No binary data is produced by this operation.
Dependencies
- Requires an API key credential configured in n8n to authenticate requests to the BookedIn API.
- The node makes HTTP requests to the BookedIn REST API endpoints.
- Network access to
https://api.bookedin.aimust be available.
Troubleshooting
Common issues:
- Invalid or missing Lead ID: The node requires a valid Lead ID; ensure the ID is correct and exists.
- Authentication errors: Verify that the API key credential is correctly set up and has permissions to delete leads.
- Network connectivity problems: Ensure the n8n instance can reach the BookedIn API endpoint.
Error messages:
"Lead ID is required": Occurs if the Lead ID parameter is empty or not provided.- API error responses (e.g., 404 Not Found): Indicates the specified lead does not exist or has already been deleted.
- Authentication failures: Usually indicate invalid or expired API credentials.
To resolve errors, double-check input parameters, confirm API credentials, and review API documentation for permission requirements.
Links and References
- BookedIn API Documentation (general reference for API endpoints and usage)
- n8n HTTP Request Node documentation for understanding authentication setup and HTTP calls within n8n workflows