Send WhatsApp messages automatically from your own systems
To send WhatsApp messages automatically from your own systems, call Meta's Cloud API: a POST to the number's /messages endpoint with an access token. A message to someone who has not written in the last 24 hours must be an approved template; free-form text works only within 24 hours of the customer's last message. Replies to incoming messages can be automated separately.
easyCoexistence connects the WhatsApp Business number you already use to Meta's Cloud API through Coexistence and gives you its credentials in the dashboard or through get_api_credentials, so your systems send templates and replies from that number while the app stays on the phone.
Messages that are not templates go out only within 24 hours of the customer's last message; after that, only templates deliver.
Fixed Cloud API throughput of a number used in the WhatsApp Business app and the API at once.
Messages sent and received through the Cloud API are mirrored with the WhatsApp Business app on a Coexistence number.
Unique people a new business portfolio can reach outside a customer service window in a moving 24 hours.
The send endpoint easyCoexistence hands you for a number: the Graph API base, the phone number ID, then /messages.
Which messages can your systems send on their own?
Two kinds, and the time since the customer last wrote decides which one Meta accepts. A system that sends an order confirmation, a booking reminder or a payment receipt to someone who has not written today needs an approved template. A system that answers a question asked an hour ago can send plain text. Meta bills the messages it charges for to the business's own WhatsApp Business Account, per message, by category and country, with no markup from easyCoexistence.
| Approved template | Free-form message | |
|---|---|---|
| When it is allowed | Any time, to a person who opted in | Within 24 hours of the customer's last message |
| Review | Meta reviews it first, usually in minutes, up to about 24 hours | None |
| Typical use | Order shipped, appointment tomorrow, payment received | Answering a question, sending a link they asked for |
| Content | Fixed text with variables filled per person | Any text, media or interactive message |
Where do you get the credentials to send?
From the number's page in the easyCoexistence dashboard, or from your AI. Under "Put this number to work", the card "Plug in your own system" lists the API base, the Send endpoint, the WABA ID and the Phone number ID, with "Reveal access token" for the token and "Show curl example" for a ready request. Treat the token like a password: anyone with it can message as your business. If the card says no token was issued, click "Reconnect to issue a token" from a computer; a reconnection only adds a token. Ask ChatGPT or Claude for "my number's API credentials" and it calls get_api_credentials, which returns the same values.
curl -X POST "https://graph.facebook.com/<VERSION>/<PHONE_NUMBER_ID>/messages" \
-H "Authorization: Bearer <ACCESS_TOKEN>" \
-H "Content-Type: application/json" \
-d '{
"messaging_product": "whatsapp",
"to": "5511999998888",
"type": "template",
"template": {
"name": "order_shipped",
"language": { "code": "en_US" },
"components": [{
"type": "body",
"parameters": [
{ "type": "text", "text": "Ana" },
{ "type": "text", "text": "#1042" }
]
}]
}
}'Can your AI send the message instead of code?
Yes, for messages you decide to send now. With the easyCoexistence connector in ChatGPT or Claude, "send the order_shipped template to 5511999998888 with Ana and #1042" becomes one send_template call, and "reply to Ana that the cake is ready" becomes send_message, which works only within 24 hours of her last message. Each call sends to one person, and ChatGPT may ask you to confirm before it runs a tool that writes. That suits one-off sends and checks. A job that must run on its own, on every new order, does not run inside the assistant: your system or an n8n workflow can call the Cloud API directly, or POST the person's number to a webhook automation on the number, which sends an approved template with the order's details filled in as variables.
Which events usually trigger an automatic WhatsApp message?
Something that already happens in your business software, turned into one template send. The pattern is the same for each: the event fires a webhook or a workflow, the workflow fills the template's variables from the record, and it posts the message to the send endpoint. Templates like these are usually UTILITY, as long as they carry no offer:
- An order is paid or shipped in your store: confirmation or tracking, with the order number.
- A booking is created or due tomorrow in your scheduling tool: the date, time and address.
- A payment is received or overdue in your billing system: the amount and a link.
- A form is submitted on your site with WhatsApp opt-in ticked: a first message that confirms it.
What happens when a customer replies to an automatic message?
The reply lands in the WhatsApp Business app like any other message, and it opens a 24-hour window in which any text can go back. On a number set to "Through easyCoexistence", the reply can also start an automation: a keyword reply for common questions, a menu with buttons, an AI agent or a Reply with AI step on your own key, or Call my webhook to hand it to your system. Add a Forward URL to receive the raw messages and delivery statuses in your system as well, signed per number. With "Straight to your system", Meta delivers everything to your endpoint instead, and automations stay off. Your team can answer from the phone at any moment, and the messages your system sent appear in the same chat.
What limits apply to messages your systems send?
Meta's, and they apply on any provider. Plan the system around them rather than discovering them in a failed status webhook:
- Throughput: a Coexistence number sends up to 20 messages per second.
- Messaging limit: unique people reached outside a window per moving 24 hours, set per business portfolio; new portfolios start at 250.
- Payment method: without one on the WhatsApp Business Account, Meta accepts templates and then drops them; easyCoexistence emails you when that starts.
- Quality: blocks and reports lower the number's quality rating, and a low rating leads Meta to limit the account.
How to set it up
- Connect the numberConnect your WhatsApp Business number to easyCoexistence through Meta's Coexistence flow; the app keeps working on the phone.
- Get a template approvedAsk your AI to create a UTILITY template such as order_shipped with create_template, or make it in WhatsApp Manager, and wait until its status is APPROVED.
- Copy the credentialsOpen the number in the dashboard, go to "Plug in your own system", copy the Send endpoint and click "Reveal access token".
- Send from your systemHave your store, CRM or n8n workflow POST the template to the Send endpoint when the event happens, with the variables filled from the record.
- Receive replies and statusesUnder "Where incoming messages go", choose "Through easyCoexistence" with a Forward URL, or "Straight to your system" with your endpoint as the destination, so replies and delivery statuses reach your system.
Common mistakes
- Sending free-form text to someone who last wrote two days ago. Meta refuses it with error 131047; send an approved template instead, and switch to text once they reply.
- Putting the access token in a web page, an app bundle or a shared spreadsheet. Anyone who reads it can send as your business; keep it on a server.
- Reading a message ID in the API response as delivered. Meta accepts sends it later fails, so watch the status webhook for failed and its error code.
- Retrying failed sends in a tight loop. A per-user limit or a stopped-marketing error does not clear in seconds, and the retries only add errors.
Automations answer what customers write back, and every number is monitored 24/7, with an email when Meta stops delivering its templates. US$ 9 down to US$ 0.75 per number per month, falling as you add numbers, with the first 3 days free.
easyCoexistence is a multichannel API and MCP server that connects AI agents such as Claude and ChatGPT to WhatsApp, Instagram, TikTok, Facebook and more. On WhatsApp it uses Coexistence: the business keeps using its number in the WhatsApp Business app while the AI works through Meta's official API.
Frequently asked questions
Will the messages my system sends show in my WhatsApp Business app?
Yes. On a Coexistence number, Meta mirrors messages between the Cloud API and the app, so a template your system sends appears in that customer's chat on your phone, and their reply arrives there too. You can continue the conversation from the app.
Can my system send images or PDFs automatically?
Yes, through the same endpoint: a media message within 24 hours of the customer's last message, or a template whose header holds an image or document at any time. An automation's Send a picture or file step also sends one of your pictures or PDFs, inside the same 24 hours, and an AI agent can send them by itself.
Do I send through an easyCoexistence API or through Meta?
Through Meta. Your system calls the Graph API directly with the number's own access token, so easyCoexistence does not relay or store the messages you send and does not mark up what Meta bills for them.
Can a no-code tool or a spreadsheet send WhatsApp messages?
Yes, if it can make an HTTP POST: n8n, Make, Zapier and Google Sheets with Apps Script all can. Point it at the Send endpoint, pass the access token in the Authorization header, and send an approved template, one recipient per request.
Keep reading
Ready to get started?
Set up WhatsApp Coexistence in minutes, not months. The app keeps working on the phone.
Start Free TrialVerified on