iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
You can connect n8n to WhatsApp through WaSphere’s self-hosted REST API: WaSphere handles the WhatsApp session, n8n receives message events and runs your workflow, and an n8n HTTP Request node sends replies through WaSphere. This route can avoid the Meta Cloud API onboarding steps used by n8n’s official WhatsApp Business Cloud integration. It does not mean Meta has approved the integration or that every automated use complies with WhatsApp’s terms.
How the n8n and WaSphere chatbot works
The setup has three parts: a WaSphere gateway connected to a WhatsApp session, an HTTPS-accessible n8n instance, and a workflow that receives and answers messages. WaSphere’s guide describes API calls passing through its Dashboard API, which proxies them to the WA Server. For incoming messages, WaSphere sends a webhook event to n8n; for replies, n8n calls WaSphere’s REST API.
- WaSphere: connects the WhatsApp session and exposes the gateway API.
- n8n Webhook: receives events from WaSphere.
- n8n workflow: validates and routes inbound events, applies your chatbot logic, and sends a reply through an HTTP Request node.
WaSphere identifies Baileys as its WhatsApp gateway engine. This is a self-hosted WhatsApp API approach, not the official WhatsApp Business Cloud connection documented by n8n.
Free tools Windows power users keep installed
One-click scans. No signup required.
What you need before connecting them
- A server for WaSphere and a working Docker installation.
- An n8n instance reachable by WaSphere over HTTPS, with its production webhook URL accessible from outside your network.
- A connected WhatsApp session in WaSphere.
- A WaSphere API key scoped for
messages:sendfor outbound replies. - A plan for verifying webhook signatures before processing incoming events.
WaSphere’s installation documentation, as reviewed on October 7, 2026, lists minimum requirements of 1 vCPU, 1 GB RAM, and 10 GB disk, with Docker Engine 24.0+ and Docker Compose v2.20+. Its recommended configuration is 2 vCPU, 2 GB RAM, and 20 GB SSD. These are vendor-published requirements, not independent performance benchmarks. See WaSphere’s installation documentation for current requirements and deployment steps.
#1 Best Overall
Deploy WaSphere and connect a session
WaSphere’s installation page describes a Docker Compose stack with PostgreSQL, the WA Server, Dashboard API, and Dashboard UI. Follow its current installation instructions to start the stack, then use the dashboard to connect a WhatsApp session. The integration guide also calls for HTTPS access to n8n and an API key with the messages:send scope.
Confirm that the session is connected and that the WaSphere API endpoint is reachable from n8n before building customer-facing automation. Exact dashboard labels and deployment details can change; use the vendor’s current guide rather than relying on a copied compose file or an old screenshot.
Send a WhatsApp reply from n8n
- Create an n8n credential. Add a Header Auth credential using
Authorizationas the header name andBearer <scoped WaSphere key>as its value. Store the key in n8n’s credential store, not in workflow parameters or exported workflow JSON. - Add an HTTP Request node. Configure it to make a
POSTrequest to the workspace/session message endpoint specified in WaSphere’s integration guide. Select the Header Auth credential you created. - Provide the message body. Use the text-message request format in WaSphere’s guide, mapping the destination and reply text from your workflow’s incoming event and chatbot logic. The endpoint pattern supports other message types with their own request bodies; do not assume a text payload applies to media or other formats.
- Test the outbound path. Send a low-risk test message to a number you control, then inspect the node result and WaSphere logs. A successful workflow execution alone should not be treated as proof of customer-facing deliverability.
Use the exact endpoint and request fields in the WaSphere n8n integration guide; the available evidence does not establish independent delivery, throughput, or reliability results.
Receive inbound messages and protect the webhook
- Create a POST Webhook node in n8n and configure it to retain the raw request body.
- Register the production webhook URL in WaSphere’s webhook settings. Use the production URL rather than the temporary test URL when enabling the live workflow.
- Verify the HMAC signature against the original bytes. Do this before trusting, routing, logging as a valid event, or acting on its contents. Signature checks should use the unmodified request body; parsing and re-serializing JSON first can change the bytes being verified.
- Filter for the inbound message event and pass valid messages to the workflow logic. Depending on your use case, that logic could use a Switch node, an AI step, a database lookup, or a human escalation path.
- Connect the reply path to the HTTP Request node and test the complete inbound-webhook-to-outbound-message loop with a controlled conversation.
Webhook signature verification is a security boundary, not an optional chatbot feature. Do not let an unverified request trigger replies, change records, or invoke tools. WaSphere describes webhook configuration and signature handling in its integration guide and repository.
What “no Meta approval” means—and does not mean
In this context, “no Meta approval” means that this particular WaSphere/Baileys connection path does not use the Meta developer and business asset onboarding flow required for n8n’s documented WhatsApp Business Cloud credentials. It is not evidence of Meta endorsement, official WhatsApp API status, permission to automate any use case, or immunity from account action.
WhatsApp’s Business App terms, effective September 23, 2026, state that a company must not, without prior written consent, “develop or use any applications that interact with our Business App Services.” WhatsApp’s general terms also restrict unauthorized or impermissible automated use and describe possible account action. The terms are relevant to assessing risk, but the cited language alone does not determine whether every particular deployment falls within a specific restriction or is compliant in a given jurisdiction. Review the terms for the service and account you use, and do not promise customers or stakeholders that a Baileys-based setup is policy-approved.
Sources: WhatsApp Business App terms, WhatsApp terms of service, and the WaSphere repository.
WaSphere self-hosting versus n8n’s official Cloud API route
| Consideration | WaSphere with Baileys | WhatsApp Business Cloud in n8n |
|---|---|---|
| Onboarding | WaSphere documents connecting a session through its gateway without the Meta Cloud API onboarding path; support depends on the current implementation and account. | n8n documents a Meta developer account, Meta business portfolio, and a business app configured with WhatsApp. Its credential guide lists an API access token and Business Account ID, and says additional configuration is needed to fully verify and launch. |
| Policy certainty | Baileys-based gateway; the route is not shown by these sources to be Meta-approved. Review applicable WhatsApp terms and account requirements. | Uses n8n’s documented WhatsApp Business Cloud integration, with Meta onboarding and the applicable Cloud API policies. |
| Infrastructure | You operate the WaSphere deployment and maintain its server and gateway components. | The cited n8n credential documentation describes connecting to Meta’s Cloud API; it does not establish that you must operate a WhatsApp gateway server. |
| n8n connection method | Webhook node for inbound events and HTTP Request node with a scoped bearer credential for outbound messages. | n8n’s WhatsApp Business Cloud credential and node flow. |
| Business-initiated messaging | The cited WaSphere materials do not establish the applicable messaging permissions or template rules for every use. Check current WhatsApp terms and account requirements. | n8n’s tutorial says business-initiated messages use pre-approved templates and describes customized replies within 24 hours of a user message; verify current Meta rules before implementation. |
| Ongoing cost and maintenance | WaSphere claims no per-message fee, but self-hosting still entails infrastructure and maintenance costs. No comparative cost study establishes total cost. | The cited n8n sources do not establish total service costs for a particular business or usage level. |
| Protocol dependency | Depends on a Baileys-based implementation, so changes to that implementation or WhatsApp Web behavior may affect the connection. | Depends on the official Cloud API and its onboarding, policy, and product requirements. |
For the official route, see n8n’s WhatsApp Business Cloud credentials documentation and WhatsApp Business Cloud tutorial. Those details can change; consult current official guidance before launch.
Quick Recap
Launch carefully
- Test signature verification using real webhook requests and confirm that invalid signatures stop the workflow before any action.
- Test the send path with a controlled recipient and inspect the response and gateway logs.
- Obtain consent for messaging, keep a human handoff available, and avoid automated actions that exceed what your use case and applicable terms permit.
- Recheck current WaSphere implementation details, n8n labels, Meta onboarding requirements, and WhatsApp terms before putting the workflow into production.
- Set monitoring and a safe failure path so a gateway outage, malformed event, or workflow error does not silently produce misleading replies.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
