WhatsApp outbound messaging with Baserow & WasenderAPI
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
Nodes used (5)
- No Operation, do nothing
n8n-nodes-base.noOp - Webhook
n8n-nodes-base.webhook - HTTP Request
n8n-nodes-base.httpRequest - Switch
n8n-nodes-base.switch - Baserow
n8n-nodes-base.baserow
What it does
Master Outbound WhatsApp: Baserow & WasenderAPI This workflow integrates with your Baserow 'Messages' table, triggering on 'Sent' status. Messages fire via WasenderAPI, rigorously logged as 'Outbound' in Baserow. Gain total control; drive results. How it works Monitors Baserow 'Messages' table for 'Sent' status. Sends messages via WasenderAPI. Logs outbound details in Baserow. Who's it for For teams dominating outbound WhatsApp and centralizing Baserow logging. Demand communication efficiency? This is your solution. Setup Steps Rapid implementation. Action plan: 1. Activate all critical workflow nodes. 2. Copy Sentwhatsapp webhook URL. Configure Baserow automation (on 'Sent' status) to trigger webhook. 3. Ensure Baserow 'Messages' table includes 'Status' ('Sent' option), linked 'WhatsApp Number', and 'Message Content' fields. (Optional: Baserow Message Form for input). 4. Embed WasenderAPI and Baserow API tokens in n8n Credentials. Security is non-negotiable. Requirements Active n8n instance (self-hosted/cloud). WasenderAPI.com trial/subscription. Baserow account with pre-configured 'Contacts' (link) and 'Messages' (link) tables.