Actions113
- Accounts Actions
- Account Users Actions
- Agent Bots Actions
- Users Actions
- Inbox API Actions
- Contacts API Actions
- Conversations API Actions
- Messages API Actions
- CSAT Survey Page Actions
- Account Agent Bots Actions
- Agents Actions
- Canned Responses Actions
- Canned Response Actions
- Custom Attributes Actions
- Contacts Actions
- Contact Actions
- Automation Rule Actions
- Help Center Actions
- Conversations Actions
- Conversation Assignment Actions
- Conversation Labels Actions
- Inboxes Actions
- Messages Actions
- Integrations Actions
- Teams Actions
- Custom Filters Actions
- Webhooks Actions
- Reports Actions
Overview
The "Update A Message" operation in the Messages API resource allows users to modify an existing message within a specific conversation. This is useful when you need to correct, append, or otherwise change the content or metadata of a message that has already been sent or stored. Typical scenarios include updating message text for clarity, fixing typos, or adding additional structured data after the initial message creation.
For example, if a customer support agent sends a message and later realizes it contains incorrect information, they can use this operation to update the message without creating a new one, maintaining conversation continuity.
Properties
| Name | Meaning |
|---|---|
| Inbox Identifier | The unique identifier of the inbox channel where the message resides, obtained from the API inbox channel. |
| Contact Identifier | The source ID of the contact associated with the message, obtained when the contact was created. |
| Conversation Id | The numeric ID representing the conversation containing the message to be updated. |
| Message Id | The numeric ID of the specific message to update within the conversation. |
| Submitted Values | A JSON object containing the fields and values to update on the message. This is sent as the request body. |
Output
The node outputs a JSON object representing the updated message details as returned by the API. This typically includes the message's current state after the update, such as its content, timestamps, identifiers, and any other relevant metadata.
If the API supports binary data related to messages (e.g., attachments), the node would handle this accordingly, but based on the provided code and properties, the output focuses on JSON data describing the updated message.
Dependencies
- Requires an API key credential for authenticating with the ChatWoot API.
- The base URL for the API must be configured in the node credentials.
- The node depends on the
@devlikeapro/n8n-openapi-nodepackage for OpenAPI integration. - The operation uses the ChatWoot API endpoint corresponding to message updates, which expects JSON-formatted request bodies.
Troubleshooting
- Missing Required Fields: Ensure all required properties (
Inbox Identifier,Contact Identifier,Conversation Id,Message Id) are provided; missing these will cause errors. - Invalid JSON in Submitted Values: The
Submitted Valuesproperty must contain valid JSON. Invalid JSON syntax will result in parsing errors. - Authentication Errors: Verify that the API key credential is correctly set up and has sufficient permissions to update messages.
- Resource Not Found: If the specified conversation or message IDs do not exist, the API will return an error indicating the resource could not be found.
- API Endpoint Issues: Confirm the base URL is correct and reachable; network issues or incorrect URLs will prevent successful requests.
Links and References
- ChatWoot API Documentation
- n8n OpenAPI Node Integration
- JSON Syntax Validator Tools (for validating
Submitted Valuesinput)