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 List resource with the Delete operation, it allows users to delete a list by specifying its unique List ID.
Common scenarios where this node is beneficial include automating the cleanup of outdated or irrelevant lead lists in a marketing or sales workflow, managing dynamic segmentation of contacts, or integrating list management into broader automation pipelines.
For example, after a campaign ends, you might want to automatically delete the associated lead list to keep your database tidy.
Properties
| Name | Meaning |
|---|---|
| List ID | The unique identifier of the list to delete (e.g., li_abcdef123456). This property is required to specify which list should be deleted. |
Output
The node outputs a JSON object representing the response from the BookedIn API after attempting to delete the specified list. Typically, this will confirm successful deletion or provide error details if the operation failed.
The output JSON structure depends on the API's response but generally includes status information about the deletion request.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating requests to the BookedIn API.
- The node makes HTTP requests to endpoints under
https://api.bookedin.ai/api/v1/lists/. - Proper configuration of the API authentication credential within n8n is necessary.
Troubleshooting
Common issues:
- Providing an invalid or non-existent List ID will result in an error from the API indicating that the list could not be found.
- Missing or incorrect API credentials will cause authentication failures.
- Network connectivity issues can prevent the node from reaching the BookedIn API.
Error messages and resolutions:
"List not found": Verify that the List ID is correct and that the list exists."Authentication failed": Check that the API key credential is correctly configured and valid."Invalid List ID format": Ensure the List ID matches the expected pattern (e.g., starts withli_).- JSON parsing errors are unlikely here since the input is a simple string, but malformed inputs elsewhere in the node may cause errors.
Links and References
- BookedIn API Documentation (general reference for API endpoints)
- n8n documentation on HTTP Request Authentication
If you need summaries for other resources or operations, feel free to ask!