Actions13
- Chatwoot Integration Actions
- Instance Actions
- Message Actions
- Parser Actions
- Webhook Actions
Overview
This node operation "Send Media Direct From Chatwoot" allows sending media messages directly to WhatsApp by extracting all necessary information automatically from a complete Chatwoot message_created event payload. The user provides the full JSON payload received from Chatwoot, which includes message details and attachments such as images, audio, video, or documents.
This is useful in scenarios where you want to forward or relay media messages received in Chatwoot conversations to WhatsApp contacts without manually parsing or specifying each field. For example, when integrating Chatwoot with WhatsApp via MegaAPI, this operation simplifies sending media files by handling extraction and formatting internally.
Practical examples:
- Automatically forwarding voice notes or images sent in Chatwoot to a WhatsApp contact.
- Syncing multimedia customer support messages from Chatwoot to WhatsApp channels.
- Building automated workflows that react to Chatwoot events and send corresponding media on WhatsApp.
Properties
| Name | Meaning |
|---|---|
| Chatwoot Payload | Complete Chatwoot message_created event payload including attachments. Paste the full JSON here. All fields will be automatically extracted. Example structure includes event type, message type, conversation metadata (sender phone number), and an array of attachments with file type and data URL. |
Output
The node outputs a JSON object representing the result of the media sending operation. This typically includes confirmation of the message being sent or any response data from the underlying WhatsApp/MegaAPI service.
If the operation supports binary data output (not explicitly shown here), it would represent the media content or related files. However, for this operation, the main output is JSON confirming the media message dispatch.
Dependencies
- Requires integration with MegaAPI WhatsApp service to send messages.
- Needs a valid Chatwoot webhook payload as input containing the media attachments.
- No explicit credential names are shown, but the node requires proper API authentication configured in n8n to communicate with MegaAPI.
- The user must provide the full Chatwoot payload JSON string as input.
Troubleshooting
- Invalid or incomplete Chatwoot payload: If the pasted JSON is malformed or missing required fields like attachments or sender phone number, the node may fail to extract necessary data. Ensure the full and correct Chatwoot
message_createdevent JSON is provided. - Unsupported media types: If the attachment file type is not supported by MegaAPI or WhatsApp, the message might not send correctly.
- Network or API errors: Failures communicating with MegaAPI could cause errors. Check API credentials and network connectivity.
- Error messages about unknown operations or resources: These indicate misconfiguration of the node parameters; ensure Resource is set to "Message" and Operation to "Send Media Direct From Chatwoot".
Links and References
- Chatwoot Webhook Events Documentation
- MegaAPI WhatsApp Service Documentation
- WhatsApp Media Message Guidelines
This summary is based solely on static analysis of the provided source code and property definitions.