Overview
This node integrates with Cribops AI agents to perform various communication-related operations. Specifically, the 'Send Message' operation allows users to send messages to a Cribops agent, either starting a new conversation or continuing an existing one. It supports sending text messages, attaching files via URLs, and adding metadata to messages. This node is useful for automating interactions with AI agents, such as customer support bots or virtual assistants, enabling workflows to programmatically send messages and manage conversations.
Use Case Examples
- Send a greeting message to a specific AI agent to initiate a conversation with a user.
- Attach a PDF document to a message sent to an AI agent for processing or review.
- Add custom metadata to messages for tracking or categorization purposes.
Properties
| Name | Meaning |
|---|---|
| Agent | Selects the Cribops AI agent to which the message will be sent. It can be chosen from a list of available agents or specified by ID. |
| Message | The text content of the message to send to the agent. |
| Conversation ID | The ID of the conversation to send the message to. If left empty, a new conversation will be started. |
| User ID | The identifier of the user sending the message, useful for tracking message origin. |
| File Attachment | Optional file attachment to include with the message, specified by URL, file name, and MIME type. |
| Additional Fields | Optional extra fields including metadata key-value pairs and a request timeout in milliseconds. |
Output
JSON
id- Unique identifier of the sent message.content- The text content of the sent message.conversationId- The conversation ID associated with the message.userId- The user ID who sent the message.type- Type of the message, typically 'user_message' for sent messages.timestamp- Timestamp when the message was sent.fileUrl- URL of the attached file, if any.fileName- Name of the attached file, if provided.fileType- MIME type of the attached file, if provided.metadata- Optional metadata key-value pairs attached to the message.
Dependencies
- Requires an API key credential for Cribops API access.
Troubleshooting
- Ensure the agent ID is correctly specified and matches the allowed pattern (letters, numbers, hyphens, underscores).
- If the conversation ID is provided, it must not contain unevaluated expressions (e.g., '{{...}}').
- Verify that the Cribops API credentials are valid and the API endpoint is accessible.
- If sending a file attachment, ensure the file URL is reachable and the MIME type is correctly specified.
- Timeouts can be adjusted via the 'Timeout' additional field to handle slow network responses.