n8n Workflow: WhatsApp to Chatwoot Message Forwarder with Media Support

This n8n workflow automates the forwarding of WhatsApp messages, including media, to a Chatwoot inbox. It acts as a bridge, ensuring that customer inquiries and their associated media received via WhatsApp are seamlessly transferred to your Chatwoot customer support platform for efficient management.

What it does

This workflow is designed to process incoming data (likely from a WhatsApp webhook) and intelligently forward it to a Chatwoot instance. Here's a step-by-step breakdown:

1. Triggered by External Execution: The workflow starts when it's executed by another workflow, indicating it's likely a sub-workflow or part of a larger automation.
2. Initial Data Transformation: It uses a "Code" node to manipulate the incoming data, likely extracting relevant fields or reformatting the payload for subsequent steps.
3. Conditional Logic for Media: An "If" node checks for the presence of media in the incoming message.
   • If Media Exists:
     • It converts the binary media data into a file.
     • It then makes an HTTP Request to an external API (likely Chatwoot's API) to create a message with the attached media.
   • If No Media:
     • It directly makes an HTTP Request to an external API (likely Chatwoot's API) to create a text-only message.
4. Data Storage (Postgres/Redis - currently unused): The workflow includes "Postgres" and "Redis" nodes, which are currently disconnected. This suggests potential for future enhancements to store message data or conversation states in a database or cache.
5. Flow Control (Switch/Wait - currently unused): "Switch" and "Wait" nodes are present but not connected. These could be used for more complex routing logic or to introduce delays in the workflow if needed in future iterations.

Prerequisites/Requirements

• n8n Instance: A running n8n instance to host and execute the workflow.
• WhatsApp Webhook: An external system (e.g., a WhatsApp Business API integration or a WhatsApp webhook provider) configured to send message data to the n8n workflow's trigger.
• Chatwoot Account: An active Chatwoot account with an inbox configured to receive messages.
• Chatwoot API Access: API credentials (e.g., API Key, Account ID, Inbox ID) for your Chatwoot instance to allow the workflow to create messages.
• HTTP Request Node Configuration: The "HTTP Request" nodes will need to be configured with the correct Chatwoot API endpoints and authentication.

Setup/Usage

1. Import the Workflow: Download the provided JSON and import it into your n8n instance.
2. Configure Credentials:
   • Ensure any necessary HTTP Request credentials (e.g., for Chatwoot API authentication) are set up in n8n.
3. Configure "When Executed by Another Workflow" Node: This node acts as the entry point. You'll need to ensure the calling workflow is correctly configured to execute this workflow and pass the WhatsApp message payload.
4. Review "Code" Node: Examine the JavaScript in the "Code" node to understand how it processes the incoming WhatsApp message data. Adjust it if your incoming payload structure differs.
5. Configure "HTTP Request" Nodes:
   • URL: Update the URLs in both "HTTP Request" nodes to point to your Chatwoot API endpoint for creating messages (e.g., https://your-chatwoot-instance.com/api/v1/accounts/YOUR_ACCOUNT_ID/inboxes/YOUR_INBOX_ID/messages).
   • Headers: Add any required headers, such as Authorization with your Chatwoot API token.
   • Body: Verify the JSON body sent to Chatwoot matches your requirements, using expressions to map WhatsApp message data to Chatwoot message fields.
6. Activate the Workflow: Once configured, activate the workflow in n8n.
7. Test: Send a test WhatsApp message (with and without media) to your configured WhatsApp webhook to ensure messages are forwarded correctly to Chatwoot.