Actions19
- Agent Actions
- Campaign Actions
- Product Actions
- Prompt Actions
- Prospect Actions
Overview
This node interacts with the Kakiyo API to retrieve multiple campaign records. Specifically, the "Get Many" operation under the "Campaign" resource fetches a list of campaigns with support for pagination and limiting the number of results returned. This is useful in scenarios where you want to display or process multiple campaigns at once, such as generating reports, syncing campaign data, or managing campaigns in bulk.
For example, you might use this node to:
- Retrieve the first 50 campaigns to display in a dashboard.
- Paginate through all campaigns by using the cursor ("After") to fetch subsequent pages.
- Integrate campaign data into other workflows or systems.
Properties
| Name | Meaning |
|---|---|
| Limit | Max 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 given point. |
Output
The node outputs an array of JSON objects representing campaigns retrieved from the Kakiyo API. Each item corresponds to one campaign record with its associated fields as returned by the API.
- The output is structured as a JSON array under the
jsonproperty. - No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating requests to the Kakiyo API.
- The base URL for the API is configured via credentials.
- The node uses HTTP methods (GET) to interact with the
/campaignsendpoint of the Kakiyo API.
Troubleshooting
- Empty results: If no campaigns are returned, verify that campaigns exist in the Kakiyo account and that the pagination cursor ("After") is correct.
- Invalid limit value: Ensure the "Limit" property is a positive integer (minimum 1).
- Authentication errors: Check that the API key credential is valid and has sufficient permissions.
- Pagination issues: If pagination does not work as expected, confirm the "After" cursor value is obtained from a previous response and correctly passed.
- API errors: Any error messages from the Kakiyo API will be returned in the node's output if "Continue On Fail" is enabled; otherwise, they will cause the workflow to error out.
Links and References
- Kakiyo API Documentation (Assumed URL, replace with actual if known)
- n8n Documentation on HTTP Request Node (for understanding request structure)
- Pagination concepts: Cursor-based Pagination