Actions36
- Account Actions
- Canned Response Actions
- Contact Actions
- Conversation Actions
- Inbox Actions
- Label Actions
- Message Actions
- Team Actions
- Webhook Actions
Overview
The node interacts with the Chatwoot API to manage messages within conversations. Specifically, the Message - Update operation updates the content of an existing message in a specified conversation. This is useful when you need to correct or modify a previously sent message programmatically.
Common scenarios include:
- Editing customer support replies after additional information is available.
- Correcting typos or updating message content dynamically based on workflow logic.
- Automating message updates in bulk or triggered by external events.
Example: Updating a message with ID 123 in conversation 456 to change its text to "Hello, how can I help you today?"
Properties
| Name | Meaning |
|---|---|
| Conversation ID | The numeric ID of the conversation containing the message to update. |
| Message ID | The numeric ID of the message to update. |
| Content | The new content/text for the message. |
| Continue on Fail | Whether the node should continue processing subsequent items if this update fails. |
| Debug Logging | Whether to output detailed request and response logs to the console for debugging. |
Output
The node outputs the JSON response from the Chatwoot API after updating the message. This typically includes the updated message object with fields such as message ID, content, timestamps, sender info, and status.
No binary data is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Chatwoot API.
- Needs the account ID and base URL configured in the credentials.
- The node makes HTTP PUT requests to the Chatwoot API endpoint for messages.
Troubleshooting
- Invalid JSON or missing parameters: Ensure that Conversation ID, Message ID, and Content are provided and valid.
- Authentication errors: Verify that the API key credential is correctly set up and has permissions to update messages.
- HTTP errors (404, 403, etc.): Confirm that the conversation and message IDs exist and belong to the authenticated account.
- Continue on Fail: If enabled, the node will skip failed updates and continue; otherwise, it will stop execution on error.
- Debug Logging: Enable this option to see detailed logs which can help diagnose issues with URL construction, request payloads, and API responses.