What WhatsApp Business API is and why it’s not the green app
WhatsApp Business API is a programming interface that lets businesses send and receive WhatsApp messages through automated systems, not through a phone. It’s not the green app you download from app stores - it’s infrastructure that connects directly to CRM systems, dashboards, or automation tools like n8n.
The key difference: the app is designed for businesses managing conversations manually from a single device, while the API enables automated workflows, multiple users, and integration with existing systems. A business receiving dozens of inquiries daily or wanting to send automated notifications after a system action needs the API, not the app.
Who needs it and when to move from the app
Businesses move to the API when the app becomes a bottleneck. This happens when a support team needs to access the same number from multiple computers, when you want to send messages based on sales stages in your CRM, or when message volume grows beyond manual response capacity.
Examples of use cases requiring the API:
- A business receiving orders through a website form that wants to send automatic WhatsApp confirmation
- A company managing appointments and sending reminders the day before
- A support team responding to customers from a shared ticketing system
- A business wanting to send real-time delivery or order status updates
All of these require connecting WhatsApp to other systems, which is exactly what the API enables.
How it works technically
WhatsApp Business API operates through Meta (formerly Facebook) and requires a Meta Business account. The process starts with creating an app in Meta for Developers, adding the WhatsApp product, and getting approval for the phone number that will be used for sending and receiving.
After approval, you receive access tokens that allow you to send HTTP requests to the WhatsApp Cloud API. Every message sent or received goes through endpoints that handle text, media, message templates, and more.
In practice, most businesses don’t write code directly against the API. They use an automation platform like n8n that includes built-in WhatsApp Cloud API integration. This allows building visual workflows: when a new message arrives, check if it contains a keyword, look up the customer in the CRM, send an automatic response, or route to a person if needed.
Connection to additional systems happens in the same workflow: you can read data from Google Sheets, update a card in Monday, send data to HubSpot, or check inventory in an internal system before sending a response.
Costs: what you actually pay
WhatsApp Business API is not free. Meta charges per conversation, not per individual message. A conversation is defined as a 24-hour window during which you can send and receive unlimited messages.
Pricing varies by conversation type:
- Customer-initiated conversations: When a customer sends the first message, the business can respond within 24 hours. These conversations are less expensive.
- Business-initiated conversations: When the business wants to message a customer who hasn’t reached out recently, you must use an approved template. These conversations cost more.
Prices vary by country. In Israel, the cost per customer-initiated conversation is relatively low, while business-initiated conversations cost more. Meta publishes rates on their official site, and they update periodically.
Beyond per-conversation costs, consider:
- Automation platform costs (n8n is free self-hosted, paid for managed versions)
- Development and configuration time for workflows
- Ongoing maintenance and system monitoring
A business handling hundreds of conversations monthly might see costs of hundreds of shekels, depending on the split between incoming and outgoing conversations. Larger businesses with thousands of conversations will reach thousands of shekels.
Setup process: what you need to prepare
Setting up WhatsApp Business API requires several steps:
-
Meta Business account: Create a business account on Meta and verify your business. Meta requires official documents like a business license or certificate of incorporation.
-
Dedicated phone number: The number used for the API cannot already be registered on regular WhatsApp or the business app. You need a new number or must release an existing one.
-
Create app and add WhatsApp: In Meta for Developers, create a new app, add the WhatsApp product, and configure the number.
-
Approve message templates: Every message the business sends first (not in response to a customer) must use a pre-approved template. You need to write templates and submit them for approval, a process taking anywhere from hours to several days.
-
Build workflows: Connect the API to your automation tool, build logic for handling incoming messages, sending responses, and integrating with additional systems.
-
Test and launch: Test workflows with team phone numbers, verify messages are received and sent as expected, and move to production.
The entire process can take between a week and several weeks, depending on workflow complexity and template approval speed.
Integration with existing systems
The real value of WhatsApp Business API lies in integration with systems the business already uses. When a message arrives, you can look up the customer in your CRM by phone number, see their purchase history, and tailor the response accordingly.
Example of a typical workflow:
- Customer sends a message with an order number
- System searches for the order in Google Sheets or a database
- If found, system sends automatic status update
- If not found, system routes the conversation to a human agent and opens a CRM ticket
This type of workflow reduces support team load and enables immediate responses to common questions. The customer gets an answer within seconds, and the team only handles inquiries requiring human intervention.
Another integration businesses build: sending outbound messages based on system events. When an order changes status in the CRM, an automated workflow sends an update to the customer on WhatsApp. When an appointment approaches, the system sends a reminder. When payment is received, the customer gets confirmation.
All of this requires upfront workflow planning and thorough testing, but the result is a system that works consistently and frees up team time.
Monitoring and ongoing maintenance
An automation system based on WhatsApp Business API requires ongoing monitoring. Meta occasionally changes terms or adds new requirements, and the workflows themselves can encounter technical issues.
We build systems with built-in alerts: if a message fails, if a token expires, or if a workflow doesn’t complete as expected, the system sends an alert to the team. This allows addressing problems before they affect customers.
Tracking message volume is also important for cost management. If conversation numbers suddenly spike, it’s worth checking whether there’s a workflow issue causing unnecessary messages, or if it’s legitimate activity growth.
Maintenance also includes updating message templates when content changes, adjusting workflows when adding services or products, and improving logic based on feedback from the team and customers.
Connection to customer response systems
WhatsApp Business API is part of a broader customer response automation infrastructure. Businesses use it alongside other channels like email, SMS, and website chat, all connected to the same management systems.
The advantage of an integrated approach: the customer can start a conversation on WhatsApp, continue via email, and finish with a phone call, while all history is saved in one place. The team sees the complete picture and can continue from where the customer left off, without asking them to repeat themselves.
Building such a system requires planning data flows between tools, but the result is a consistent customer experience and greater business efficiency.
When to get started
WhatsApp Business API suits businesses that have passed the point where the regular app is sufficient. If you find yourself copying and pasting responses, searching for information in other systems during conversations, or struggling to manage growing message volume - it’s time to examine the transition.
Initial investment includes setup time, development costs, and ongoing conversation costs. But for a business handling dozens or hundreds of inquiries daily, the savings in team time and improvement in response time can justify the cost fairly quickly.
The key is not trying to build everything at once. Start with one simple workflow - for example, automatic response to messages arriving outside business hours - and expand gradually. As the team learns what works and what doesn’t, you can add more complex workflows and integrate additional systems.
Businesses that build the system gradually, with close monitoring and ongoing maintenance, succeed in turning WhatsApp into a central communication channel that saves time and improves service.
Frequently asked questions
Can I use the same number for both the app and the API?
No. A phone number can only be registered in one place: regular WhatsApp, WhatsApp Business (the app), or WhatsApp Business API. If the number is already in use, you need to release it or use a different number for the API.
How long does it take to get a message template approved?
Usually between a few hours and 48 hours. Meta checks that the template meets guidelines: doesn't contain prohibited promotional content, includes an opt-out option if relevant, and is written in clear language. Rejected templates can be edited and resubmitted.
What happens if the customer doesn't respond within 24 hours?
The conversation window closes, and you cannot send free-form messages until the customer reaches out again. If the business wants to make contact, they must send a message via an approved template, which opens a new 24-hour window. This is a WhatsApp limitation to prevent spam.
Do I need to know how to code to set up the system?
Not necessarily. Tools like n8n allow building workflows visually, without writing code. But you need basic technical understanding of how APIs work, how to connect systems, and how to build logic. Many businesses prefer working with someone who has already built such systems.