Kakiyo

Interact with the Kakiyo API
Join our community

Actions19

Overview

The node integrates with the Kakiyo API to manage various resources such as campaigns, prospects, agents, products, and prompts. Specifically for the Prospect - Qualify operation, it marks a prospect (identified by a chat/conversation ID) as qualified within the Kakiyo system. This is useful in sales or marketing automation workflows where you want to programmatically update the status of a lead or prospect after certain criteria are met.

Practical scenarios include:

  • Automatically qualifying a prospect after a successful conversation.
  • Integrating qualification status updates into CRM or outreach pipelines.
  • Triggering follow-up actions based on prospect qualification.

Properties

Name Meaning
Chat ID The unique identifier of the chat or conversation with the prospect to be qualified.

Output

The node outputs JSON data representing the response from the Kakiyo API after marking the prospect as qualified. The structure depends on the API's response but generally includes confirmation of the qualification action or updated prospect details.

No binary data output is involved.

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.
  • Network access to the Kakiyo API endpoint.

Troubleshooting

  • Common issues:

    • Invalid or missing Chat ID will cause the API request to fail.
    • Authentication errors if the API key or base URL is misconfigured.
    • Network connectivity problems preventing API calls.

  • Error messages:

    • Errors returned from the Kakiyo API will be passed through, typically indicating invalid parameters or authentication failure.
    • If "continue on fail" is disabled, the node execution will stop on error; enabling it allows processing subsequent items despite failures.

  • Resolutions:

    • Verify that the Chat ID corresponds to an existing prospect conversation.
    • Ensure the API key credential and base URL are correctly set up.
    • Check network connectivity and firewall settings.

Links and References

Discussion