Actions29
Overview
This node integrates with the BookedIn AI platform to manage and interact with various entities such as agents, leads, lists, strategies, campaigns, and human messages. Specifically, for the Agent - Get Many operation, it retrieves a paginated list of AI agents configured in the BookedIn system.
Typical use cases include:
- Fetching multiple AI agents to display or process their configurations.
- Synchronizing agent data from BookedIn into other systems.
- Automating workflows that require bulk access to agent information.
For example, you might use this node to retrieve all agents with pagination controls to then analyze their objectives or update related records in your CRM.
Properties
| Name | Meaning |
|---|---|
| Skip | Number of agents to skip for pagination (offset). Useful for paging through large sets. |
| Limit | Maximum number of agents to return in one request (page size). Defaults to 100. |
Output
The node outputs an array of JSON objects representing the agents retrieved from the BookedIn API. Each object contains the full details of an agent as returned by the API, including fields like agent name, configuration (objective, prompt, model), webhook URL if set, and whether lead fields are updated by the agent.
No binary data is output by this operation.
Example output snippet (simplified):
[
{
"id": "ag_123456",
"name": "Sales Assistant",
"agent_config": {
"objective": "Book meetings for sales team",
"prompt": "You are a helpful AI assistant...",
"model": "openai/gpt-4o",
"update_lead_fields": true,
"webhook_url": "https://example.com/webhook"
},
"created_at": "2024-01-01T12:00:00Z",
...
},
...
]
Dependencies
- Requires an API key credential for authenticating with the BookedIn API.
- The node makes HTTP requests to
https://api.bookedin.ai/api/v1/agents/endpoints. - Proper network connectivity to the BookedIn service is necessary.
- No additional environment variables are required beyond the API authentication setup.
Troubleshooting
Common issues:
- Pagination parameters (
skip,limit) out of range or invalid may cause empty results or errors. - Network or authentication failures will prevent data retrieval.
- Pagination parameters (
Error messages:
- Authentication errors indicate missing or invalid API credentials; verify and reconfigure the API key.
- HTTP errors from the API (e.g., 400 or 500 status codes) suggest malformed requests or server issues.
- If no agents are returned, check that agents exist in the BookedIn account and that pagination parameters are correct.
Resolution tips:
- Ensure the API key credential is correctly configured and has sufficient permissions.
- Adjust
skipandlimitvalues to valid ranges. - Check the BookedIn service status if persistent errors occur.
Links and References
- BookedIn API Documentation (for detailed API endpoint info)
- n8n Documentation on HTTP Request Node (for understanding HTTP calls)
- OpenAI Models (context on AI models used by agents)