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 - Get operation, it retrieves detailed information about a single lead by its unique ID.
Common scenarios where this node is beneficial include:
- Fetching up-to-date lead details during a workflow to personalize communications or decisions.
- Integrating lead data retrieval into automated sales or marketing pipelines.
- Synchronizing lead information from BookedIn into other systems or databases.
Example:
You have a workflow that triggers when a new event occurs (e.g., a form submission). Using this node with the Lead/Get operation, you can fetch the full lead profile by ID to enrich your CRM or trigger targeted follow-up actions.
Properties
| Name | Meaning |
|---|---|
| Lead ID | The unique identifier of the lead to retrieve. Example format: ld_f1e2d3c4b5a6. |
Output
The node outputs a JSON object representing the lead's data as returned by the BookedIn API. This typically includes fields such as:
- Contact information (name, email, phone number, timezone)
- Source of the lead
- Metadata/custom fields associated with the lead
- Other lead-specific attributes managed by BookedIn
The output is structured as an array of JSON objects (one per input item), each containing the lead data under the json property.
This node does not output binary data.
Dependencies
- Requires an API key credential for authenticating requests to the BookedIn API.
- The node uses HTTP requests to communicate with the BookedIn REST API endpoints.
- No additional environment variables are required beyond the configured API authentication.
Troubleshooting
- Invalid Lead ID: If the provided Lead ID does not exist or is malformed, the API will return an error. Ensure the Lead ID is correct and follows the expected format.
- Authentication Errors: If the API key credential is missing or invalid, requests will fail. Verify that the API key is correctly configured in n8n credentials.
- Network Issues: Connectivity problems may cause request failures. Check network access and API availability.
- API Rate Limits: Excessive requests might be throttled by the BookedIn API. Implement appropriate retry or backoff logic if needed.
- Unexpected Response Structure: If the API changes, the output structure might differ. Review the latest BookedIn API documentation if issues arise.
Links and References
- BookedIn API Documentation (general reference for API endpoints and data structures)
- n8n Documentation (for general usage of HTTP Request nodes and credentials)