Overview
This node interacts with Cribops AI agents, specifically providing an operation to poll messages from a message queue associated with a tenant's Cribops organization. It retrieves a batch of messages from a specified queue or all queues if none is specified, processes the messages, and acknowledges them to prevent reprocessing. This is useful for workflows that need to handle incoming messages or events from Cribops queues, such as processing AI agent responses or integrating with external systems.
Use Case Examples
- Polling a queue named 'stripe_events' to retrieve up to 50 messages for processing in an automation workflow.
- Polling all queues for a tenant to gather new messages and trigger subsequent actions based on the message content.
Properties
| Name | Meaning |
|---|---|
| Tenant ID | The tenant ID for your Cribops organization, used to identify which tenant's queues to poll. |
| Batch Size | Number of messages to retrieve in one poll operation, with a maximum of 100. |
| Queue Name | Specific queue to poll messages from. If left empty, the node polls all queues for the tenant. |
| Additional Fields | Optional additional parameters such as metadata key-value pairs and request timeout in milliseconds. |
Output
JSON
messages- Array of messages retrieved from the queue, each containing details like id, correlation ID, queue name, parsed data, headers, parameters, insertion timestamp, tenant ID, and path.count- Number of messages retrieved in the batch.
Dependencies
- Requires an API key credential for Cribops API access.
Troubleshooting
- Ensure the tenant ID is correct and the API credentials are valid to avoid authentication errors.
- If no messages are returned, verify that the specified queue name exists and contains messages.
- Timeout errors may occur if the request takes longer than the specified timeout; adjust the timeout setting accordingly.