Kakiyo

Interact with the Kakiyo API

Overview

This node integrates with the Kakiyo API to manage various resources such as agents, campaigns, products, prompts, and prospects. Specifically for the Agent - Get Details operation, it retrieves detailed information about a particular agent by its ID. This is useful in scenarios where you need to fetch current status, configuration, or metadata of an agent within your automation workflows.

Practical examples include:

  • Fetching agent details to monitor their activity or status.
  • Using agent information to conditionally route workflow logic.
  • Auditing or reporting on agent configurations.

Properties

Name Meaning
Agent ID The unique identifier of the agent whose details are to be retrieved. This property is required for the "Get Details" operation on the Agent resource.

Output

The output is a JSON object representing the detailed data of the specified agent as returned by the Kakiyo API. It typically includes all relevant fields describing the agent's current state and configuration.

The node does not output binary data for this operation.

Dependencies

  • Requires an API key credential configured in n8n to authenticate requests to the Kakiyo API.
  • The base URL for the Kakiyo API must be set in the credentials.
  • The node uses HTTP methods (GET) to interact with the Kakiyo API endpoints.

Troubleshooting

  • Common issues:

    • Invalid or missing Agent ID will cause the API request to fail.
    • Incorrect or expired API authentication token may result in authorization errors.
    • Network connectivity problems can prevent successful API calls.
  • Error messages:

    • Errors from the API will be returned in the node output if "Continue On Fail" is enabled.
    • Typical error messages include "Agent not found" if the provided Agent ID does not exist.
    • Authentication errors indicating invalid credentials require checking the API key setup.
  • Resolutions:

    • Verify that the Agent ID is correct and exists in the Kakiyo system.
    • Ensure the API key credential is valid and has necessary permissions.
    • Check network access and proxy settings if applicable.

Links and References

Discussion