Actions29
Overview
This node integrates with the BookedIn API to manage various marketing and sales resources such as agents, leads, lists, strategies, campaigns, and human messaging. Specifically for the List - Update operation, it allows users to update the name of an existing list by specifying its unique ID and the new desired name.
Common scenarios where this node is beneficial include:
- Renaming a lead list to reflect updated campaign goals or timeframes.
- Correcting typos or standardizing naming conventions in your lead lists.
- Organizing lists dynamically based on evolving marketing strategies.
For example, you might use this node to rename a prospecting list from "Q3 Prospects" to "Q4 Prospecting List" after a quarter ends.
Properties
| Name | Meaning |
|---|---|
| List ID | The unique identifier of the list to update (e.g., li_abcdef123456). This is required to specify which list to modify. |
| List Name | The new name to assign to the list. This is a required string that represents the updated list name (e.g., "Q4 Prospecting List"). |
Output
The node outputs JSON data representing the updated list object returned by the BookedIn API. This typically includes fields such as the list's ID, updated name, creation date, and other metadata related to the list.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the BookedIn API via an API key credential configured in n8n.
- The node uses authenticated HTTP requests to communicate with the BookedIn service endpoint at
https://api.bookedin.ai/api/v1/lists/{listId}. - Proper permissions on the API key are necessary to perform update operations on lists.
Troubleshooting
- Invalid List ID: If the provided List ID does not exist or is malformed, the API will return an error. Verify the List ID format and existence.
- Missing Required Fields: Both List ID and List Name are mandatory. Omitting either will cause the node to fail.
- API Authentication Errors: Ensure the API key credential is valid and has sufficient permissions.
- Network Issues: Connectivity problems can cause request failures; check network access to the BookedIn API.
- Unexpected API Response: If the API changes or returns unexpected data, the node may throw errors. Check for updates or changes in the BookedIn API documentation.
Links and References
- BookedIn API Documentation (for detailed API endpoints and payloads)
- n8n HTTP Request Node Documentation (for understanding HTTP request handling in n8n)