Overview
The Cribops Trigger node integrates with Cribops to receive messages from Cribops agents. It supports two modes: polling and webhook. In polling mode, it regularly polls a specified queue for messages, useful for workflows that need to process messages at intervals. In webhook mode, it listens for incoming messages via a webhook, ideal for real-time event-driven workflows. This node is beneficial for automating responses or processing data from Cribops agents in customer support or communication platforms.
Use Case Examples
- Polling a queue named 'stripe_events' every 30 seconds to process user messages in batches of 10.
- Setting up a webhook to receive real-time messages from a specific Cribops agent, filtering events by type, and authenticating requests with a secret token.
Properties
| Name | Meaning |
|---|---|
| Trigger Mode | Determines how messages are received from Cribops, either by polling the queue at intervals or via webhook. |
| Tenant ID | The tenant ID for the user's Cribops organization, required for API access. |
| Agent Name or ID | Specifies the Cribops agent to receive messages from, selectable from a list or via expression. Only shown in webhook mode. |
| Queue Name | The specific queue to poll for messages. Optional; if empty, all queues are polled. Only shown in polling mode. |
| Poll Interval | How often to poll the queue for messages, in seconds. Only shown in polling mode. |
| Batch Size | Number of messages to retrieve per poll, with a maximum of 100. Only shown in polling mode. |
| Event Types | Types of events that trigger the node, such as agent responses, user messages, or file attachments. |
| Additional Fields | Additional optional fields, including a secret token for webhook authentication. |
Output
JSON
id- Unique identifier of the message.correlation_id- Correlation ID associated with the message.queue_name- Name of the queue from which the message was received.data- The main content of the message, parsed as JSON if possible.headers- Headers included in the message data.params- Parameters included in the message data.inserted_at- Timestamp when the message was inserted.tenant_id- Tenant ID extracted from message headers or the configured tenant ID.path- Path information from message headers.
Dependencies
- Requires an API key credential for Cribops API access.
Troubleshooting
- If webhook authentication fails, ensure the secret token matches the one configured in Cribops and the node.
- Polling errors may occur due to network issues or incorrect tenant ID; verify credentials and connectivity.
- If no messages are received, check that the correct queue name and event types are configured.
- Webhook mode requires the workflow to be activated; otherwise, manual triggers will throw an error.