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 - Create operation, it allows users to create a new list by specifying its name. This is useful in scenarios where you want to organize leads into different groups or segments for targeted campaigns or outreach.
Practical examples include:
- Creating a prospecting list for a specific quarter (e.g., "Q4 Prospecting List").
- Organizing leads based on product interest or region.
- Preparing segmented lists for marketing campaigns or sales outreach.
Properties
| Name | Meaning |
|---|---|
| List Name | The name of the list to create. For example, "Q4 Prospecting List". |
Output
The node outputs the JSON response returned by the BookedIn API after creating the list. This typically includes details about the newly created list such as its unique ID, name, creation timestamp, and other metadata provided by the API.
The output is structured as an array of JSON objects, each representing the created list entity.
No binary data is involved in this operation.
Dependencies
- Requires an API key credential for authenticating requests to the BookedIn API.
- The node makes HTTP requests to
https://api.bookedin.ai/api/v1/lists/endpoint. - Proper configuration of the API authentication credential in n8n is necessary.
Troubleshooting
Common issues:
- Missing or invalid API credentials will cause authentication failures.
- Providing an empty or missing "List Name" property will result in an error since it is required.
- Network connectivity issues can prevent successful API calls.
Error messages:
"List Name" is required— Ensure the list name is provided and not empty.- Authentication errors — Verify that the API key credential is correctly set up and has proper permissions.
- API response errors — Check the API documentation for any rate limits or validation rules that might be causing failures.
Links and References
- BookedIn API Documentation (general reference for endpoints and payloads)
- n8n HTTP Request Node documentation for understanding how authenticated requests are made within n8n workflows