Actions36
- Account Actions
- Canned Response Actions
- Contact Actions
- Conversation Actions
- Inbox Actions
- Label Actions
- Message Actions
- Team Actions
- Webhook Actions
Overview
This node interacts with the Chatwoot API to manage messages within conversations. Specifically, the "Message" resource with the "Get" operation retrieves a single message by its numeric ID from a specified conversation. This is useful when you need to fetch detailed information about a particular message in a customer support or chat context managed via Chatwoot.
Practical examples:
- Fetching the content and metadata of a specific message in a conversation for auditing or display.
- Retrieving message details to trigger further automation based on message content or status.
- Integrating Chatwoot message data into other systems or workflows.
Properties
| Name | Meaning |
|---|---|
| Conversation ID | The numeric ID of the conversation containing the message to retrieve. |
| Message ID | The numeric ID of the specific message to retrieve within the conversation. |
| Continue on Fail | Whether the node should continue processing subsequent items if this operation fails. |
| Debug Logging | Whether to output detailed request and response logs to the console for debugging purposes. |
Output
The node outputs the JSON representation of the requested message as returned by the Chatwoot API. This typically includes fields such as message content, sender information, timestamps, message type, and any associated metadata.
If the operation succeeds, the output will be an object with a json property containing the message data.
No binary data output 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 GET requests to the Chatwoot API endpoint
/api/v1/accounts/{accountId}/conversations/{conversationId}/messages/{messageId}.
Troubleshooting
- Common issues:
- Invalid or missing Conversation ID or Message ID parameters will cause the API call to fail.
- Incorrect or expired API authentication token will result in authorization errors.
- Network connectivity issues can prevent successful API calls.
- Error messages:
- Errors from the HTTP request are logged if debug logging is enabled.
- If the API returns an error (e.g., 404 Not Found), the node will throw an error unless "Continue on Fail" is enabled, in which case it outputs an error object.
- Resolutions:
- Verify that the Conversation ID and Message ID are correct and exist in the Chatwoot account.
- Ensure the API key credential is valid and has necessary permissions.
- Enable debug logging to get detailed request/response info for troubleshooting.