Actions26
- Collections Actions
- Records Actions
- Fields Actions
- Chats Actions
- Files Actions
- User Contacts Actions
- Triggers Actions
Overview
The "Complete Message" operation in the "Chats" resource allows users to send a message completion request to a chat system. This node is useful for scenarios where you want to programmatically continue or complete a conversation by providing new content, either as text or audio. For example, it can be used to automate chatbot responses, append additional information to an ongoing chat, or send audio messages within a chat context.
Properties
| Name | Meaning |
|---|---|
| Collection Id | The identifier of the collection that contains the chat. |
| Chat Id | The identifier of the specific chat to which the message completion applies. |
| Content | The actual content of the message to be sent as the completion. |
| Content Type | The type of content being sent; options are: "text" or "audio". |
| File | JSON object containing file information if the message includes a file (e.g., audio). |
Output
The node outputs a JSON object representing the response from the chat completion API. This typically includes details about the completed message, such as its content, metadata, and any relevant status information. If the message includes binary data (like audio), the node handles this accordingly, but the output primarily focuses on the JSON response describing the completion result.
Dependencies
- Requires an API key credential for authenticating with the Cogfy Tables API.
- Needs the base URL of the Cogfy Tables API configured in the node credentials.
- Depends on the external Cogfy Tables API service to process chat completions.
Troubleshooting
- Missing or invalid Collection Id or Chat Id: Ensure these identifiers are correctly provided and correspond to existing resources in the API.
- Invalid content or content type: Verify that the content matches the specified content type ("text" or "audio"). For audio, ensure the file information is correctly formatted.
- Authentication errors: Confirm that the API key credential is valid and has the necessary permissions.
- API connectivity issues: Check network connectivity and the correctness of the base URL configuration.
- JSON parsing errors for the File property: Make sure the JSON string provided for the file property is well-formed.
Links and References
- Cogfy Tables API Documentation (hypothetical link)
- n8n Documentation on Creating Custom Nodes