Overview
This node interacts with Cribops AI agents, allowing users to perform various operations such as retrieving information about a specific agent, listing all agents, sending messages to agents, replying to conversations, sending typing indicators, and polling message queues. It is useful for integrating AI-driven communication workflows, automating responses, and managing conversations with Cribops agents. For example, a user can get detailed info about an agent, send a message to start or continue a conversation, or poll a queue for incoming messages to process them automatically.
Use Case Examples
- Get detailed information about a specific Cribops AI agent by providing its ID.
- Send a message to a Cribops agent to initiate or continue a conversation.
- Reply to an existing conversation with a Cribops agent using the conversation ID.
- Poll a message queue to retrieve and acknowledge messages for processing.
Properties
| Name | Meaning |
|---|---|
| Agent | The ID of the Cribops AI agent to interact with. Can be selected from a list or provided directly by ID. Required for operations involving a specific agent. |
| Additional Fields | Optional additional parameters for the request, including metadata key-value pairs and a request timeout in milliseconds. |
Output
JSON
agents- List of agents returned when listing all agents.count- Count of agents or messages returned.id- Unique identifier of a message or agent.correlation_id- Correlation identifier for messages in the queue.queue_name- Name of the queue from which messages are polled.data- Message data, parsed if possible from JSON.headers- Headers associated with a message.params- Parameters associated with a message.inserted_at- Timestamp when the message was inserted into the queue.tenant_id- Tenant identifier associated with the message.path- Path information from message headers._originalTriggerData- Original trigger data included in some responses, especially for typing indicator operation.
Dependencies
- Requires an API key credential for Cribops API authentication.
Troubleshooting
- Ensure the API credentials are correct and the Cribops API is accessible to avoid authentication errors.
- When providing the conversation ID, ensure it does not contain unevaluated expressions (e.g., '{{' or '}}') to prevent errors.
- If a 422 validation error occurs when replying to a conversation, check the conversation ID and message format for correctness.
- If the response webhook URL is missing in input data during reply operations, the node falls back to the agent webhook endpoint, which may affect behavior.
- Timeouts can be adjusted via the 'Timeout' additional field to handle slow network responses.