Actions13
- Chatwoot Integration Actions
- Instance Actions
- Message Actions
- Parser Actions
- Webhook Actions
Overview
The "Send Message to Chatwoot" operation in the Chatwoot Integration resource allows sending messages directly to a specific conversation within Chatwoot. This node is useful for automating communication workflows where messages need to be programmatically sent to contacts or conversations managed in Chatwoot, such as customer support follow-ups, notifications, or chatbots.
Typical use cases include:
- Sending text updates or alerts to customers via Chatwoot conversations.
- Attaching files or media (via URL or binary upload) to enrich messages.
- Automating responses or bulk messaging campaigns integrated with Chatwoot.
For example, you can send a text message notifying a customer about their order status or attach a PDF invoice directly into an ongoing Chatwoot conversation.
Properties
| Name | Meaning |
|---|---|
| Chatwoot Account ID | Your Chatwoot account identifier used to target the correct account. |
| Contact ID | The unique identifier of the contact in Chatwoot to whom the message relates. |
| Conversation ID | The unique identifier of the Chatwoot conversation where the message will be sent. |
| Message Content | The textual content of the message to send. |
| Message Type | Specifies if the message is "Incoming" or "Outgoing". |
| Attachment Type | Type of attachment included with the message: None, URL, or Binary File. |
| Attachment URL | If Attachment Type is URL, this is the web address of the file to attach. |
| Input Binary Field | If Attachment Type is Binary File, this is the name of the input binary property containing the file data. |
| File Name | For binary attachments, the filename to assign to the uploaded file. If omitted, it uses the original or generates one. |
Output
The node outputs a JSON object representing the result of the message sending operation to Chatwoot. This typically includes confirmation details such as message IDs, status, and any metadata returned by Chatwoot's API.
If a binary attachment is sent, the node handles uploading the file content accordingly but does not output binary data itself; instead, it confirms successful transmission.
Dependencies
- Requires a valid Chatwoot account and access credentials (e.g., an API key or token) configured in n8n to authenticate requests.
- The node depends on Chatwoot's REST API endpoints to create messages within conversations.
- For binary attachments, the node expects the input binary data to be available in the specified binary property field.
Troubleshooting
- Missing Required Fields: Ensure that Chatwoot Account ID, Contact ID, Conversation ID, and Message Content are provided. Missing these will cause errors.
- Invalid Attachment Type or Data: If Attachment Type is set to URL or Binary, verify that the URL is accessible or the binary data exists in the specified input field.
- API Authentication Errors: Confirm that the API credentials for Chatwoot are correctly configured and have sufficient permissions.
- Conversation or Contact Not Found: If the Contact ID or Conversation ID does not exist or is incorrect, the message will fail to send.
- Error Messages: The node throws errors indicating unknown operations or resources if misconfigured. Double-check the Resource and Operation parameters.
Links and References
This summary is based on static analysis of the node's source code and provided property definitions for the "Send Message to Chatwoot" operation under the Chatwoot Integration resource.