Overview
This node allows interaction with Cribops AI agents, specifically enabling users to reply to an existing conversation with a message. It is useful in scenarios where automated or manual responses need to be sent within ongoing conversations managed by Cribops agents. For example, customer support workflows can use this node to send replies to user queries in a conversation thread.
Use Case Examples
- Replying to a customer query in a support conversation by sending a message through the Cribops agent.
- Automating responses in a chatbot conversation by replying to the conversation ID with a predefined message.
Properties
| Name | Meaning |
|---|---|
| Agent | The Cribops AI agent to interact with, selected either from a list or by specifying an agent ID. |
| Conversation ID | The ID of the conversation to reply to. This is required to identify the conversation thread. |
| Message | The message content to send as a reply in the conversation. |
| Additional Fields | Optional additional parameters such as metadata key-value pairs and request timeout in milliseconds. |
Output
JSON
id- Unique identifier of the sent message or reply.content- The content of the message sent in the reply.conversationId- The conversation ID to which the reply was sent.type- Type of message, typically 'agent_response' for replies.timestamp- Timestamp when the message was sent.
Dependencies
- Requires an API key credential for Cribops API authentication.
Troubleshooting
- Ensure the Conversation ID is provided and does not contain unevaluated expressions (e.g., '{{...}}').
- Verify that the API credentials are correct and the Cribops API is accessible.
- If a 422 validation error occurs, check the conversation ID and message format for correctness.
- If the response webhook URL is missing in input data, the node falls back to sending the message directly via the agent webhook endpoint.