Businesses can connect their WhatsApp number to automation tools through the WhatsApp Business API, which enables messages go out automatically when an event fires in another internal system, like a new order, a form submission, or a missed appointment. Most businesses already have a stack of connected tools, but WhatsApp usually sits outside it or is run manually. The API changes that. It is free to use, but Meta offers it as self-service only: a business either builds the integration from scratch or works with a Business Solution Provider (BSP) that manages all the setup and support.[5][6] 360Dialog is a BSP and Official Meta Solution Partner that provides the API connection, a dashboard for managing keys and webhooks, and 24/7 support, so a business can skip the build and start automating with tools like Zapier, n8n, Make, Pabbly Connect, Pipedream, IFTTT, and Activepieces.
Key Takeaways
- WhatsApp automation connects a business number to external tools through the WhatsApp Business API, replacing manual messaging with event-driven workflows.[5]
- The WhatsApp Business App offers basic auto-replies (greeting messages, away messages, quick replies), but it supports only one user, has no API access, and cannot connect to external automation tools.[5]
- A BSP adds managed billing, a dashboard for API keys and webhooks, dedicated support, and a team inbox on top of Meta’s free-to-use Cloud API, so a business does not have to build that infrastructure from scratch.[6]
- Seven tools connect to WhatsApp through 360Dialog today, using a native app, a community node, or a generic HTTP and webhook module depending on the platform.[2][3][4][7]
- Inside the 24-hour customer service window, a business can send any message type; outside it, only pre-approved template messages go through.[5]
What Is WhatsApp Automation
WhatsApp automation is the use of the WhatsApp Business API to send, receive, and respond to messages automatically based on events in other systems. A form submission triggers a follow-up message. A shipment status change sends a tracking update. A calendar booking fires a reminder. The business number does the work without anyone typing a reply.
The WhatsApp Business App, which is Meta’s free mobile and desktop app for small businesses, supports basic auto-replies: a greeting message when a new customer writes, an away message outside business hours, and quick replies for frequent questions. But the app is limited to one user at a time, does not expose an API, and cannot connect to external tools like a CRM, an e-commerce platform, or an automation builder.
The WhatsApp Business API is the level that makes real automation possible. It opens a programmatic interface for sending messages, receiving inbound events via webhooks, managing templates, and integrating with any system that can make an HTTP request. Businesses access the API either directly through Meta or through a BSP that manages the connection on their behalf.
Why Connect Through a BSP Instead of Meta’s API Directly
Connecting through a BSP adds a managed billing relationship, dedicated account support, and a dashboard for API keys, webhooks, and templates on top of Meta’s Cloud API, which is free to call but otherwise self-service.[6] Meta’s own WhatsApp Manager lets a business manage numbers and templates directly, but Meta provides no dedicated account manager or guaranteed support SLA the way a BSP does.
360Dialog is an Official Meta Solution Partner, with WhatsApp API plans starting at €49 per number per month. More than 100,000 businesses run their WhatsApp Business Platform connection through 360Dialog, backed by 24/7 support.[6] Our pricing page lists current plan tiers, including higher-throughput options for numbers sending at volume.
The 360Dialog Hub is the dashboard behind the API key and webhook setup described in the next section: a business generates and rotates its channel’s API key there, configures the webhook URL, and manages message templates, without building that tooling from scratch.[12] Every endpoint the tools in this guide call, from POST /messages to the multi_webhook configuration endpoints, is documented at docs.360dialog.com.[1]
How Does the API Key and Webhook Pattern Work
Connecting WhatsApp to any automation tool starts with generating an API key for a WhatsApp number, then pointing that number’s webhook at the tool’s endpoint. In the 360Dialog Hub, a business generates a channel-specific key once a phone number finishes onboarding.[12] That key is sent as the D360-API-KEY header on every request to the API.[1]
Outbound messages go to a single endpoint, POST https://waba-v2.360dialog.io/messages, with the recipient identified by country code plus digits, no plus sign and no spaces. Inbound messages, delivery statuses, and errors arrive as JSON payloads on the webhook URL configured for that number, which can be set directly in the Hub or through the API.[1]
The webhook side carries the strict requirements. A webhook URL must support HTTPS with a valid certificate, and the domain cannot contain an underscore or an explicit port. The endpoint must acknowledge each notification with an HTTP 200 response within 5 seconds; anything slower or any other response code is treated as a failed delivery and queued for retry. Meta retries a failed webhook for up to 7 days using exponential backoff, so a webhook that recovers from downtime still receives the backlog.[1] By default, one webhook serves a whole phone number, but a business can attach up to 3 destinations to a single number through the multi_webhook endpoint, useful when an automation tool and a team inbox both need to see the same traffic.[14]
Which Automation Tools Connect to WhatsApp
Several automation platforms connect to WhatsApp through 360Dialog’s integrations: Zapier, n8n, Make, Pabbly Connect, Pipedream, IFTTT, and Activepieces, each through a different connection method ranging from a native app to a plain HTTP request.
| Tool | How It Connects | Best For |
|---|---|---|
| Zapier | Native 360Dialog app in Zapier’s directory, no code required[2] | Non-technical teams already running Zapier |
| n8n | Community node, @pmartino/n8n-nodes-360dialog, self-hosted n8n only[3] | Self-hosted teams that want full workflow control |
| Make | Standard Webhooks and HTTP modules, no native 360Dialog app in Make’s directory[4] | Visual scenario builders comfortable configuring HTTP requests |
| Pabbly Connect | Native module, listed as “360 Dialog (Cloud)” in Pabbly’s naming[7] | Cost-conscious teams on Pabbly’s pricing model |
| Pipedream | HTTP trigger plus a Node.js or Python code step[8] | Developers who want code-level control with managed infrastructure |
| IFTTT | Webhooks service, any use requires at least a paid Pro plan[9][10] | Teams already paying for IFTTT Pro |
| Activepieces | HTTP and Webhook steps, no native 360Dialog piece, free self-hosted Community Edition[11] | Teams wanting open-source, self-hosted automation |
Zapier’s 360Dialog app in the directory offers a “New Inbound Message” trigger plus actions for sending text, media, and template messages and checking channel health, all without writing a line of code.[2] The n8n community node covers the same operations through a node built and maintained outside 360Dialog, so it carries the version and support caveats typical of any community package.[3] Make and Activepieces both ship a built-in WhatsApp connector, but neither one talks to a 360Dialog number: Make’s WhatsApp-named apps and Activepieces’ built-in WhatsApp piece connect to unrelated services or hardcode Meta’s own API host, so a 360Dialog integration on either platform has to go through the generic HTTP and Webhook steps instead.[4][11] IFTTT’s Webhooks service handles WhatsApp in the same generic way, but any use of it, sending or receiving, sits behind at least a paid Pro subscription; Pro+ is required only for Webhooks queries, multiple connected accounts, and filter code.[10] Pabbly Connect’s native module covers the same core operations as Zapier’s app, sending text, template, image, and document messages plus a List Templates action, and pairs them with a one-time pricing option that suits teams wary of recurring per-task fees.[7] Pipedream’s code step hands a developer full control over the request logic in Node.js or Python, running on Pipedream’s own managed infrastructure, which puts it between Zapier’s no-code simplicity and n8n’s full self-hosting.[8]
What Can You Automate on WhatsApp
Automating WhatsApp means an event in another system triggers a message, or a downstream action, automatically, replacing manual typing and sending.
- Lead follow-up. A form submission or an ad click triggers an automatic WhatsApp message that opens the conversation before a sales rep ever sees the lead.
- Order updates. An e-commerce status change, such as a shipment leaving the warehouse, triggers a WhatsApp template message with the new status and a tracking link.
- Appointment reminders. A calendar booking triggers a scheduled reminder message a set number of hours before the appointment.
- CRM sync. An inbound WhatsApp message creates or updates a contact record in the CRM automatically, without manual data entry.
- Internal alerts. A high-value order, a support escalation, or a failed payment triggers an internal WhatsApp or Slack notification to the right team.
What Is the 24-Hour Customer Service Window
The 24-hour customer service window is the period after a WhatsApp user messages or calls a business during which the business can send any message type; once it closes, only Meta-approved template messages go through. The window resets to 24 hours every time the user sends a new message or call, and while it is open a business can send free-form text, images, documents, and interactive messages without restriction.[5]
Every automation tool built on the WhatsApp Business API has to respect this rule, regardless of connection method. A Zap or a Make scenario that tries to send a free-form message to a customer outside the window fails; the workflow needs to fall back to an approved template message instead, which is why every tool covered in the table above supports a distinct “send template” action alongside its regular text-sending action.[2] A common failure mode is a workflow that replies to an old conversation days later, well after the window closed. Automation platforms with a stale webhook, or with no separate template action configured, are the most likely to hit this.
Automation vs Live Chat: What Handles What
Automation tools handle structured events and data, so a business running WhatsApp automation still needs a live inbox for human replies. An automated workflow reacts to a known event with a predictable message: a status change, a form submission, a scheduled reminder. A live inbox handles the back-and-forth when a customer asks an unscripted question.
360Dialog’s Marketplace plan bundles a messaging tool package alongside the API connection, giving a team a shared inbox for live replies on the same number that its automations run on.[6] Because a 360Dialog number supports up to 3 webhook destinations, an automation tool and a team inbox can both receive the same message traffic in parallel, with the automation tool handling triggers and the inbox handling the conversation.[14]
Ready to connect both automation and a live team inbox to the same number? Talk to us.
What You’ll Find in This Series
This series will go deeper on each platform:
- WhatsApp Zapier integration, covering the native app’s exact triggers and actions, and how it differs from Zapier’s built-in WhatsApp app (coming soon).
- n8n WhatsApp integration, covering the community node’s installation, credential setup, and version caveats (coming soon).
- Make WhatsApp integration, covering the Webhooks and HTTP module setup in full, step by step (coming soon).
- 4 more ways to automate WhatsApp with 360Dialog, covering Pabbly Connect, Pipedream, IFTTT, and Activepieces in depth (coming soon).
- How to build a WhatsApp AI chatbot with 360Dialog, covering how to wire an LLM such as ChatGPT, Claude, or Gemini into WhatsApp through the API (coming soon).
- Getting started with the WhatsApp Business API, covering account setup and verification from scratch (coming soon).
Ready to connect your number? Get API access.
Frequently Asked Questions
Do I Need a Developer to Automate WhatsApp?
It depends on the tool. Zapier’s native app and Pabbly Connect’s native module need no code, just an API key pasted into the connection screen.[2][7] Make, Pipedream, IFTTT, and Activepieces route WhatsApp through generic HTTP and webhook modules, which need some comfort configuring headers and a JSON body.[4][8][9] The n8n community node needs no custom code either, but it only installs on a self-hosted n8n instance, which suits teams with developer resources.[3]
Which Tool Is Best for a Non-Technical Team?
Zapier and Pabbly Connect fit non-technical teams best, since both offer a native 360Dialog connection with no HTTP configuration required.[2][7] Make’s visual scenario builder is approachable to learn, but it still needs a webhook and an HTTP module configured by hand, since no native 360Dialog app exists in Make’s directory.[4]
Can I Use Multiple Automation Tools on One WhatsApp Number?
Yes. 360Dialog’s multi-webhook feature raises a single phone number’s destination limit from the single default to up to 3, useful for running an automation tool and a team inbox side by side. Adding destinations adds latency to message delivery, so 360Dialog recommends staying on the single default for high-volume numbers.[14]
Is There a Sandbox for Testing WhatsApp Automations?
360Dialog provides a separate Sandbox API, at base path waba-sandbox.360dialog.io, for testing sends and templates before going live, with its own API key and a 200-message cap.[15] Businesses should still test a new production automation with a small number of real WhatsApp contacts, ideally team members or a handful of opted-in customers, before turning it on for the full audience.
What Happens if My Webhook Goes Down?
Meta retries a failed webhook delivery for up to 7 days using exponential backoff, which keeps messages queued through temporary downtime. Once the webhook recovers, it still needs to return HTTP 200 within 5 seconds; any other response, or no response in time, goes back into the retry queue.[1]
Sources
[1] 360Dialog, “Webhooks,” docs.360dialog.com/docs/messaging/webhook. Accessed 27 Aug 2026.
[2] Zapier, “360dialog Integrations,” zapier.com/apps/360dialog/integrations. Accessed 27 Aug 2026.
[3] npm, “@pmartino/n8n-nodes-360dialog,” npmjs.com/package/@pmartino/n8n-nodes-360dialog. Accessed 27 Aug 2026.
[4] Make, “Browse Apps,” make.com/en/integrations. Accessed 27 Aug 2026.
[5] Meta, “Pricing on the WhatsApp Business Platform,” developers.facebook.com/documentation/business-messaging/whatsapp/pricing. Accessed 27 Aug 2026.
[6] 360Dialog, “WhatsApp Business Platform Pricing,” 360dialog.com/pricing. Accessed 27 Aug 2026.
[7] Pabbly, “360 Dialog (Cloud) Integrations,” pabbly.com/connect/integrations/360-dialog-cloud/. Accessed 27 Aug 2026.
[8] Pipedream, “HTTP-Triggered Workflows,” pipedream.com/docs/workflows/triggers. Accessed 27 Aug 2026.
[9] IFTTT, “Webhooks Integrations,” ifttt.com/maker_webhooks. Accessed 27 Aug 2026.
[10] IFTTT, “Plans & Pricing,” ifttt.com/plans. Accessed 27 Aug 2026.
[11] Activepieces, “Pricing,” activepieces.com/pricing. Accessed 27 Aug 2026.
[12] 360Dialog, “API Keys,” docs.360dialog.com/docs/hub/api-key. Accessed 27 Aug 2026.
[13] 360Dialog, “Webhook URL,” docs.360dialog.com/docs/hub/webhook-url. Accessed 27 Aug 2026.
[14] 360Dialog, “Set Multiple Webhooks for Phone Number,” docs.360dialog.com/partner/onboarding/webhook-events-and-setup/set-multiple-webhooks-for-phone-number. Accessed 27 Aug 2026.
[15] 360Dialog, “Sandbox,” docs.360dialog.com/docs/get-started/sandbox. Accessed 27 Aug 2026.
