Actions29
Overview
This node integrates with the BookedIn API to manage and interact with various marketing and sales automation resources, including strategies. Specifically, the "Strategy - Get Many" operation retrieves multiple strategy records from the BookedIn platform. This is useful for scenarios where you want to list or process multiple strategies in bulk, such as syncing strategies into your workflow, analyzing available strategies, or displaying them in a dashboard.
Practical examples:
- Fetching all strategies to display in a custom UI.
- Retrieving strategies for further processing or filtering within an automation.
- Paginating through strategies when there are many entries.
Properties
| Name | Meaning |
|---|---|
| Skip | Number of strategies to skip for pagination (offset). |
| Limit | Maximum number of strategies to return in one request (pagination limit). |
Output
The node outputs JSON data representing the retrieved strategies. The structure corresponds directly to the response from the BookedIn API's endpoint for listing strategies. Each item in the output array represents a single strategy object with its details (such as ID, name, description, stages, etc.).
No binary data is output by 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/strategies/with query parameters for pagination (skipandlimit). - Proper configuration of the API authentication credential in n8n is necessary.
Troubleshooting
- Invalid JSON format in strategy configuration: Although not applicable to "Get Many", other operations involving strategy configuration require valid JSON. Ensure JSON inputs are correctly formatted.
- API Authentication Errors: If the API key is missing or invalid, requests will fail. Verify that the API key credential is set up correctly.
- Pagination Issues: Setting very high limits or skips beyond available data may result in empty responses. Adjust
SkipandLimitaccordingly. - Network or API Downtime: Network issues or BookedIn API downtime can cause request failures. Check connectivity and API status.
Links and References
- BookedIn API Documentation (general reference for API endpoints)
- n8n documentation on HTTP Request Node for understanding how authenticated requests work in n8n