Actions19
- Agent Actions
- Campaign Actions
- Product Actions
- Prompt Actions
- Prospect Actions
Overview
This node interacts with the Kakiyo API to manage marketing campaigns and related entities. Specifically, for the Campaign - Get Many operation, it retrieves a list of campaigns from the Kakiyo platform. This is useful when you want to fetch multiple campaign records for reporting, analysis, or further automation workflows.
Typical use cases include:
- Listing all active or past campaigns to monitor their status.
- Fetching campaigns in batches for synchronization with other systems.
- Paginating through campaigns when there are many entries.
For example, you might use this node to pull the latest 50 campaigns and then process each campaign's data downstream in your workflow.
Properties
| Name | Meaning |
|---|---|
| Limit | Maximum number of campaign results to return. Must be at least 1. Defaults to 50. |
| After | Cursor string used for pagination to fetch the next set of results after a specific point. |
Output
The node outputs an array of JSON objects representing campaigns retrieved from the Kakiyo API. Each object corresponds to a single campaign with its associated data fields as returned by the API.
The output does not include binary data; it is purely JSON structured data about campaigns.
Dependencies
- Requires an API key credential for authenticating with the Kakiyo API.
- The base URL for the Kakiyo API must be configured in the node credentials.
- The node uses HTTP requests to communicate with the Kakiyo REST endpoints.
Troubleshooting
- Empty results: If no campaigns are returned, verify that campaigns exist in the Kakiyo account and that the
LimitandAfterparameters are set correctly. - Authentication errors: Ensure the API key credential is valid and has sufficient permissions.
- Pagination issues: Incorrect or expired cursor values in the
Afterparameter may cause unexpected results or empty responses. - API request failures: Network issues or incorrect base URL configuration can cause request errors. Check connectivity and credential settings.
Links and References
- Kakiyo API Documentation (hypothetical link, replace with actual if available)
- n8n documentation on HTTP Request Node for understanding underlying request mechanics