Bidirectional Chat Management between WhatsApp and Slack - n8n Workflow

Customer support teams looking to manage WhatsApp chats directly within their Slack workspace.
Businesses requiring an audit trail or collaboration capabilities around customer communications.
Developers needing an advanced n8n workflow example for integrating messaging platforms.
Users seeking robust n8n templates for real-time, bidirectional chat routing.

Managing high-volume customer communication across multiple channels can be complex. This comprehensive n8n workflow solves this challenge by establishing a real-time, bidirectional bridge between WhatsApp and Slack. By using this n8n workflow, every new WhatsApp conversation automatically creates a dedicated private Slack channel, indexed by the contact's phone number. Team members can then respond directly in Slack, and the message is relayed back to the customer on WhatsApp. This n8n workflow supports not only text but also media (images, audio, and documents) in both directions, making it a complete solution for centralized chat management. Implementing this n8n template streamlines operations and ensures context is never lost, leveraging the power of various essential n8n node capabilities.

This powerful n8n workflow operates in two main flows, ensuring complete bidirectional synchronization.

Flow 1: WhatsApp to Slack

1. The journey begins with the WhatsApp Trigger, which acts as the starting n8n trigger, activating upon receiving any new WhatsApp message (text or media).


2. The workflow first attempts to ensure a dedicated Slack channel exists for the incoming phone number. It uses the Slack n8n node to check for and, if necessary, create a private channel corresponding to the sender's phone number.


3. The Message Type n8n node (a Switch) analyzes the incoming WhatsApp message type (text, image, audio, or document).


4. For media files, dedicated WhatsApp n8n node instances fetch the public URL for the media content. The download media HTTP Request n8n node then retrieves the actual file data.


5. The upload media Slack n8n node sends the file to the corresponding Slack channel, maintaining the conversation context.


6. For text messages, the Send Message in Channel Slack n8n node posts the message directly.

Flow 2: Slack to WhatsApp

1. The Slack Trigger acts as the second primary n8n trigger, listening for messages posted by agents within the designated Slack channels.


2. The Get Channel by ID n8n node resolves the Slack channel ID back to its name (which is the customer's WhatsApp number).


3. The Checking Message Type Switch n8n node determines if the Slack message contains text or attached media.


4. If text, the Send Message WhatsApp n8n node routes the text response back to the customer.


5. If media, the Get Media URL Slack n8n node obtains the private download link. The Download Media HTTP Request n8n node fetches the file, which is then sent via the Send Message1 WhatsApp n8n node to the WhatsApp recipient. This complete n8n workflow ensures seamless team communication and customer response.

To set up this comprehensive n8n workflow, follow these steps:

1. Import the n8n Workflow: Copy the provided JSON and paste it into your n8n instance using the 'New' -> 'Import from JSON' function.


2. WhatsApp Credentials: This n8n template requires two WhatsApp credentials: one for the WhatsApp Trigger (OAuth account for webhooks) and another for the WhatsApp API nodes (API token for sending/retrieving media).

1. Slack Credentials: You need Slack API credentials (API token) capable of creating channels, listing channels, and uploading files. Apply these to all relevant Slack n8n node instances (Send Message in Channel, Create Channel, Slack Trigger, etc.).


2. HTTP Request Credentials: Configure the HTTP Request n8n node instances (download media and Download Media) with the necessary bearer tokens for API access to both WhatsApp and Slack private download links. For the WhatsApp API, this often involves using the same token used for the main WhatsApp n8n node.


3. Activate: Once credentials are set for every n8n node, save the n8n workflow and activate the two primary n8n trigger nodes (WhatsApp Trigger and Slack Trigger) to begin synchronization.

WhatsApp Trigger: The primary n8n trigger for the WhatsApp-to-Slack flow. It listens for incoming messages, essential for initiating the n8n workflow.
Create Channel (Slack n8n node): Attempts to create a private Slack channel using the WhatsApp sender's phone number as the channel name. Crucial for organizing conversations.
Message Type (Switch n8n node): Routes the flow based on the WhatsApp message type (text, audio, image, document), ensuring the correct media handling n8n node is executed.
get audio URL / get image URL / get document URL (WhatsApp n8n node): These nodes interact with the WhatsApp API to retrieve the necessary temporary download URLs for binary media content.
download media (HTTP Request n8n node): Downloads the media file from WhatsApp using the retrieved URL and WhatsApp API token authorization. The output is binary data used by the next n8n node.
upload media (Slack n8n node): Uploads the binary media data obtained from the previous n8n node into the designated Slack channel.
Slack Trigger: The initiating n8n trigger for the Slack-to-WhatsApp flow. It listens for messages posted by users in Slack channels.
Get Channel by ID (Slack n8n node): Retrieves the Slack channel name, which is used to identify the recipient's WhatsApp phone number for the outgoing message.

• Send Message / Send Message1 (WhatsApp n8n node): Responsible for sending either text or media (using the useMedian8n path for downloaded files) back to the WhatsApp user, completing the bidirectional loop of this n8n workflow.