Kakiyo

Interact with the Kakiyo API

Actions19

Overview

This node integrates with the Kakiyo API to manage agents, campaigns, prospects, products, and prompts. Specifically for the Agent - Pause operation, it allows users to pause an agent by sending a request to the Kakiyo API. This is useful in scenarios where you want to temporarily halt an agent's activity, such as pausing automated outreach or processing without deleting the agent.

Practical example:

  • You have an agent running LinkedIn outreach campaigns but need to pause it during holidays or maintenance windows. Using this node’s Agent Pause operation, you can programmatically pause the agent to stop all its activities until resumed.

Properties

Name Meaning
Agent ID The unique identifier of the agent to be paused.

Output

The node outputs the JSON response returned by the Kakiyo API after attempting to pause the specified agent. The output structure corresponds directly to the API’s response and typically includes confirmation of the pause action or details about the agent’s new state.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Kakiyo API.
  • Requires 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 credentials configuration.

Troubleshooting

  • Common issues:

    • Invalid or missing Agent ID: Ensure the Agent ID provided is correct and exists in the Kakiyo system.
    • Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
    • Network or connectivity problems: Check your network connection and Kakiyo API availability.

  • Common error messages:

    • "error": "Agent not found" — The specified Agent ID does not exist. Double-check the ID.
    • "error": "Unauthorized" — Authentication failed. Confirm your API credentials.
    • "error": "Bad Request" — Possibly due to malformed input; ensure the Agent ID is correctly formatted.

Resolving these usually involves verifying input parameters, checking credentials, and ensuring the Kakiyo service is reachable.

Links and References

Discussion