Actions35
- Account Actions
- Canned Response Actions
- Contact Actions
- Conversation Actions
- Inbox Actions
- Label Actions
- Message Actions
- Team Actions
- Webhook Actions
Overview
This node integrates with the Chatwoot API to manage messages within conversations. Specifically, the Message - Update operation allows you to update the content of an existing message in a specified conversation and account.
Typical use cases include:
- Correcting or editing a previously sent message.
- Updating message content dynamically based on workflow logic.
- Automating message updates in customer support or chat management scenarios.
For example, if a support agent needs to amend a message after sending it, this node can programmatically update that message's content without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Account ID | The numeric ID of the Chatwoot account where the message exists. |
| Conversation ID | The numeric ID of the conversation containing the message to update. |
| Message ID | The numeric ID of the message to be updated. |
| Content | The new content text for the message. |
| Continue on Fail | Whether to continue executing subsequent items if this update operation fails (boolean). |
Output
The output is a JSON object representing the updated message as returned by the Chatwoot API. It typically includes all message details such as:
id: The message identifier.content: The updated message content.- Other metadata related to the message (timestamps, sender info, etc.).
If the update is successful, the output contains the full updated message data. If the operation fails and "Continue on Fail" is enabled, the output will contain an error message in the JSON under an error key.
No binary data is produced by this operation.
Dependencies
- Requires a valid API authentication token configured in n8n credentials to access the Chatwoot API.
- The base URL for the Chatwoot instance must be set in the credentials.
- Network connectivity to the Chatwoot API endpoint.
Troubleshooting
Common issues:
- Invalid or missing Account ID, Conversation ID, or Message ID will cause the API request to fail.
- Insufficient permissions or invalid API token may result in authorization errors.
- Providing empty or invalid content may cause validation errors from the API.
Error messages:
"404 Not Found": The specified message, conversation, or account does not exist. Verify IDs."401 Unauthorized": Authentication failed. Check API credentials."400 Bad Request": Invalid input data, e.g., empty content. Ensure required fields are correctly filled.
To handle errors gracefully, enable "Continue on Fail" to allow the workflow to proceed even if some updates fail.