WhatsApp Business API UK — Setup, Integration & Automation
Stack — WhatsApp Business API

WhatsApp Business API for UK businesses.

The WhatsApp Business API is what separates a messaging app from an operational system. It connects your WhatsApp number to your HR platform, CRM and finance stack — so every message can trigger a workflow, update a record, or generate a document. No laptop required. No human in the middle.

API vs app

What the free app gives you — and where it stops.

WhatsApp Business app — the starting point

The free WhatsApp Business app gives you away messages, quick replies, broadcast lists and a business profile. Useful for sole traders and very small teams. The limits appear quickly: no integrations, no logic, no memory, broadcast capped at 256 contacts with no personalisation.

Meta Business Agent — the next step

Meta now offers a native AI agent inside Meta Business Suite — the platform managing your Facebook, Instagram and WhatsApp Business accounts. It handles inbound customer FAQs, basic queries and routing automatically. Free to activate. Good for customer-facing enquiries. Not designed for internal operational workflows.

WhatsApp Business API — the operational layer

The API is what unlocks real automation. Every inbound message fires a webhook. Every outbound message can be triggered by a workflow. The system knows who sent the message, what they're authorised to do, and routes accordingly. This is where proposals, HR requests, invoicing and onboarding live.

The cost is lower than almost everyone expects

Meta charges per conversation — at typical small business volumes this is a few pounds per month. The API itself is free to access. There is no SaaS subscription, no per-seat licence. The running cost of a fully operational WhatsApp AI agent is typically under £40 per month total.

What the API unlocks

Every message becomes a system trigger.

Once the API is connected via Make.com, every inbound message can start a workflow. Every outbound message can be sent by automation. Here is what that enables in practice.

01

Inbound webhook — every message triggers Make.com

Every message sent to your WhatsApp number arrives at a Make.com webhook in real time. The scenario reads the message, checks who sent it, identifies intent, and routes to the right workflow. Voice notes are transcribed automatically — engineers on site can send audio and the system processes it identically to text.

02

Permissions layer — senders know their role

The system identifies every sender by their phone number and checks what they are authorised to do. Staff can access their own data. Managers can see their team. Directors can trigger higher-level workflows. Enforced automatically — no login, no passcode, no separate app.

03

HR platform integration — BreatheHR, HiBob, Factorial

Holiday requests, sick day reporting, shift swaps and new starter onboarding all handled via WhatsApp. The system reads entitlement from the HR platform, raises requests, logs absences and files documents — writing everything back without a manager touching a keyboard.

04

Proposal and invoice generation — Xero, Monday.com

A message with job details triggers a branded proposal, deploys it to a live URL, emails the client, updates the CRM deal and creates the Xero record. The same pipeline runs in under two minutes from any phone. No laptop, no copy-pasting, no chasing the office.

05

Outbound templated messages — proactive comms

Beyond reactive responses, the API supports business-initiated messages via pre-approved templates. Appointment reminders, job completion notifications, onboarding prompts sent to new starters — all triggered by your existing systems, delivered on WhatsApp.

06

Media handling — images, documents, voice

The API handles images, PDFs and voice notes natively. A staff member photographs a right-to-work document — it is filed automatically. An engineer sends a voice note from site — it is transcribed and logged. A client replies with a signed document — it is filed against their record.

What to expect

The verification process — what nobody tells you.

Fresh number
The API requires a number never previously registered to WhatsApp — personal or business app.
5–10 days
Typical Meta business verification timeline. Start this before the build is complete, not after.
£0 access
The API itself is free. Meta charges per conversation — a few pounds per month at typical small business volumes.
GDPR ready
Operates under Meta's data processing agreements. Opt-in flows and audit logging included as standard.
Setup process

From zero to live WhatsApp agent.

End-to-end — API access, verification, build and go-live. We handle all of it.

01

Meta Business Account and verification

We set up your Meta Business Account, submit for business verification and connect the WhatsApp number through an approved Business Solution Provider. Verification runs in parallel with the build — we start it on day one.

02

Make.com webhook configured

The inbound webhook is configured in Make.com to receive every message from your WhatsApp number. The scenario structure is built — sender identification, intent parsing, routing logic — before the live number is connected.

03

AI agent trained on your business

Claude is configured with your services, terminology, pricing structure and tone of voice. System prompts lock the AI to your brand and policies — it never freelances, never guesses, never outputs something you wouldn't send to a client.

04

Downstream systems connected

BreatheHR, HiBob, Factorial, Xero, Monday.com — whichever systems your workflows need to read from or write to are connected and tested. Each workflow is a separate Make.com scenario: clean, documented, maintainable.

05

Live number connected and tested

Once Meta verification clears, the live number is connected and every workflow is tested end-to-end with real messages. We don't go live until every scenario behaves correctly under realistic conditions.

06

30-day post-launch support

A month of monitoring and fixes after go-live. Production always surfaces edge cases that testing misses — we handle them without raising a new invoice.

Common questions

What businesses ask before they start.

Can I use my existing WhatsApp Business number?

No — this is the single most common blocker. A number previously registered to any WhatsApp account (personal or business app) cannot be cleanly migrated to the Cloud API without losing message history and potentially the number itself. The API requires a fresh number. We typically recommend sourcing a dedicated SIM for the purpose.

How long does Meta business verification take?

Typically five to ten business days, depending on the business and the documents submitted. It is the one part of the process outside your control — which is why we start it on day one of the engagement, not after the build is complete. The build runs in parallel.

What is the difference between the Meta Business Agent and the full API?

The Meta Business Agent is a native tool inside Meta Business Suite — useful for customer-facing FAQs and basic inbound queries on your existing WhatsApp Business number. It is free and quick to set up. The API is required for internal operational workflows — anything that needs to read from or write to your HR platform, CRM or accounting software. Both are legitimate; they solve different problems.

Is it GDPR compliant?

Yes. WhatsApp Business API operates under Meta's data processing agreements, which are compatible with UK GDPR. All message data is handled within your own Meta Business Account — we don't hold client data. Opt-in flows, data retention settings and audit logging are configured as standard.

What does it cost to run?

Make.com Pro covers the automation scenarios at around £16 per month. Meta's Cloud API charges per conversation — at typical internal staff volumes this is a few pounds per month. The Claude API for the AI agent costs pennies per message at conversational volumes. Total running cost: typically £20–40 per month depending on message volume and workflow complexity.

Can one WhatsApp number handle multiple workflow types?

Yes — and this is one of the key advantages of the API build. The same number can handle proposal requests from a sales team, HR leave requests from staff, and invoice queries from an accounts team. The permissions layer routes each sender to the right workflow based on their phone number and the intent of their message.

Ready to connect WhatsApp to your operation?

Book a discovery call. We'll map the workflows your team runs manually on WhatsApp, identify the highest-value one to automate first, and walk you through exactly what the API setup involves.

Free ops checklist