WhatsApp Micro-CRM and Conversation Logger using Baserow - n8n Workflow

Small businesses and freelancers needing a simple CRM solution.
Users relying heavily on WhatsApp for client communication.
Automation specialists looking for robust n8n templates for external APIs.
Anyone wanting to centralize WhatsApp interactions in a structured database like Baserow.

Managing client conversations across multiple platforms is a major challenge for small operations. This specialized n8n workflow solves the problem by transforming WhatsApp interactions into structured CRM data. By utilizing the power of a custom n8n node and leveraging WasenderAPI for real-time message forwarding, every inbound and outbound message (including media) is instantly cataloged in Baserow.

This robust n8n template ensures that your contact list is always up-to-date and provides a complete conversation history, eliminating manual data entry and ensuring no client interaction is ever missed. This comprehensive n8n solution acts as a dedicated Micro-CRM.

The core logic of this n8n workflow is designed around processing incoming webhook payloads efficiently in parallel paths:

1. Incoming Data Trigger: The process starts with the 'Trigger: WhatsApp Message' n8n trigger, which receives real-time events (messages.upsert) from the WasenderAPI webhook. Header authentication is highly recommended for security.


2. Data Standardization: The 'Prepare: Standardize Incoming Data' Code n8n node runs a Python script to convert the technical WhatsApp JID format into a clean, readable phone number (+CountryCodeNumber). Crucially, this script also detects if the message is text-only or contains an image.


3. Contact Management (Path 1): The workflow performs a lookup using the 'Baserow: Search Contact' HTTP Request n8n node. The 'Route: Contact Exists?' n8n switch node then directs the flow:

1. Message Logging (Path 2): Simultaneously, the 'Route: Message Type (Image/Text)' n8n switch node determines the content type.

To deploy this powerful n8n workflow, follow these steps:

1. Import the n8n template: Copy the provided JSON code and import it into your self-hosted or n8n cloud instance.


2. Baserow Setup: Create a new workspace in Baserow and duplicate the recommended 'Contacts' and 'Messages' table templates (links provided in the original sticky note/workflow description).


3. Baserow Credentials: Set up a Baserow API key credential in n8n and replace the placeholder credentials in all Baserow and Baserow HTTP Request n8n node instances.


4. WasenderAPI Setup: Obtain your API token from WasenderAPI.


5. Webhook Setup: Configure the 'Trigger: WhatsApp Message' n8n node. Copy the generated webhook URL.

1. Review IDs: Ensure all Baserow n8n nodes have the correct Database ID (264981 is the placeholder) and Table IDs, matching the tables you duplicated.


2. Activate: Save the n8n workflow and activate it to start processing WhatsApp messages.

Trigger: WhatsApp Message (Webhook n8n trigger): The entry point. Listens for POST requests from WasenderAPI, specifically for messages.upsert events.
Prepare: Standardize Incoming Data (Code n8n node): Essential custom scripting. Converts the raw JID format to a readable phone number and detects the message type (Image vs. Text) to manage subsequent routing efficiently. This is a critical n8n node for data cleansing.
Baserow: Search Contact (HTTP Request n8n node): Searches the Baserow 'Contacts' table using the standardized phone number to check if the client already exists.
Route: Contact Exists? (Switch n8n node): Determines whether to execute the 'Create New Contact' or 'Update Contact Timestamp' steps based on the search results count.
Create New Contact / Update Contact Timestamp (Baserow n8n node): Standard Baserow n8n nodes responsible for CRUD operations (creating the contact or updating the last activity time).
WasenderAPI: Fetch Profile Picture URL (HTTP Request n8n node): Fetches the contact's profile picture using the WasenderAPI endpoint, configured with a Bearer Token.
Route: Message Type (Image/Text) (Switch n8n node): The main router for message content, directing payloads to either the complex image handling flow or the simple text logging flow.
WasenderAPI: Decrypt Image (HTTP Request n8n node): Uses the decrypt-media endpoint to securely retrieve the image content URLs before logging the file. This step is necessary due to how WhatsApp media is delivered.

• Log Inbound/Outbound Text/Image Message (Baserow n8n node): The final logging nodes that create new records in the Baserow 'Messages' table, mapping all message metadata, content, and the Baserow-uploaded image file reference.