Kakiyo

Interact with the Kakiyo API

Actions19

Overview

The node interacts with the Kakiyo API to manage prospects and their conversations within campaigns. Specifically, the "Resume Conversation" operation for the "Prospect" resource allows users to resume a previously paused conversation with a prospect identified by a chat ID. This is useful in scenarios where automated or manual outreach was temporarily halted and needs to be restarted without losing context.

Practical examples include:

  • Resuming follow-up messages to a lead after a pause due to unavailability.
  • Restarting engagement with a prospect after resolving an issue or waiting period.
  • Automating conversation flow control in sales or marketing campaigns.

Properties

Name Meaning
Chat ID The unique identifier of the chat or conversation to resume.

Output

The node outputs JSON data representing the response from the Kakiyo API after attempting to resume the conversation. This typically includes confirmation of the resumed state or details about the prospect's conversation status. The output is structured as an array of JSON objects, each corresponding to an input item processed.

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 Kakiyo API must be configured in the node credentials.
  • Network access to the Kakiyo API endpoint is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing Chat ID: Ensure the Chat ID provided corresponds to an existing conversation.
    • Authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
    • Network or API downtime: Check connectivity and Kakiyo service status.

  • Error messages:

    • Errors returned from the API will be included in the node output if "Continue On Fail" is enabled.
    • Typical error messages may indicate invalid parameters, unauthorized access, or resource not found.

To resolve errors:

  • Double-check input parameters, especially the Chat ID.
  • Confirm API credentials are valid.
  • Review API documentation or contact support if persistent errors occur.

Links and References

Discussion