Reachkit icon

Reachkit

Interact with the Reachkit API

Actions20

Conversation → Reply

AI-generated

Overview

The node enables interaction with the Reachkit API, specifically allowing users to reply to an existing conversation by sending an HTML content message. This is useful in scenarios where automated or manual responses need to be sent within a conversation thread, such as customer support chats, sales follow-ups, or engagement campaigns.

For example, a user can automate replying to customer inquiries by providing the conversation ID and the reply content, which will then be posted back into the conversation via the Reachkit platform.

Properties

Name Meaning
Conversation ID The unique identifier of the conversation to which the reply will be sent.
Content The HTML content of the reply message that will be posted in the conversation.

Output

The node outputs JSON data representing the response from the Reachkit API after posting the reply. This typically includes details about the newly created reply message such as its ID, timestamp, content, and possibly metadata about the conversation state.

If the node supports binary data output (not indicated here), it would represent any attachments or media associated with the reply, but based on the provided code and properties, the output is purely JSON.

Dependencies

  • Requires an API key credential for authenticating with the Reachkit API.
  • The base URL for API requests is https://reachkit.ai/api/v1.
  • Proper configuration of the API key credential in n8n is necessary for successful communication.

Troubleshooting

  • Common Issues:

    • Invalid or missing Conversation ID: Ensure the conversation ID exists and is correctly provided.
    • Authentication errors: Verify that the API key credential is valid and has the necessary permissions.
    • Malformed HTML content: The content must be valid HTML; otherwise, the API might reject the request.

  • Error Messages:

    • Unauthorized or 401 errors indicate issues with API authentication.
    • 404 errors may mean the conversation ID does not exist.
    • Validation errors could arise if required fields are missing or content format is incorrect.

Resolving these usually involves checking input parameters, ensuring credentials are correct, and validating the content format.

Links and References

Discussion