Kakiyo

Interact with the Kakiyo API

Actions19

Overview

This node integrates with the Kakiyo API to manage campaigns and related resources such as agents, products, prompts, and prospects. Specifically for the Campaign - Resume operation, it allows users to resume a previously paused campaign by sending a request to the Kakiyo API.

Use cases include:

  • Restarting outreach or marketing campaigns that were temporarily halted.
  • Automating campaign lifecycle management within workflows.
  • Resuming campaigns after manual review or adjustment.

For example, if a campaign was paused due to low engagement or to update its parameters, this node can be used to programmatically resume it once ready.

Properties

Name Meaning
Campaign ID The unique identifier of the campaign to resume. This is required to specify which campaign should be resumed.

Output

The node outputs the JSON response returned by the Kakiyo API after attempting to resume the campaign. This typically includes details about the campaign's current state or confirmation of the resume action.

The output is structured as an array of JSON objects, each corresponding to an input item processed. Each object contains the API response data relevant to the resume operation.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Kakiyo API.
  • Needs an API authentication token configured in n8n credentials (referred generically as "an API key credential").
  • The base URL for the Kakiyo API must be set in the node credentials.

Troubleshooting

  • Common issues:

    • Invalid or missing Campaign ID will cause the API call to fail.
    • Network connectivity problems or incorrect API credentials will prevent successful requests.
    • Attempting to resume a campaign that is not paused may result in an error or no state change.

  • Error messages:

    • Errors from the Kakiyo API are passed through; typical messages might indicate invalid campaign IDs or unauthorized access.
    • If the node throws an error about authentication, verify that the API key credential is correctly configured.
    • If the node fails with a network error, check internet connectivity and the correctness of the API base URL.

Links and References

Discussion