Log inStart Free Trial
Meta Tech Provider

Copy an automation to many WhatsApp numbers with your AI

To copy a WhatsApp automation to several numbers, ask your AI assistant through the easyCoexistence MCP connector. It reads the original with list_automations, finds the numbers with list_numbers, creates one copy per number with create_automation, switched off, and runs test_automation on each. You review the test replies, adjust per-number details such as address or hours, then ask it to turn the copies on.

1 number

Where an automation runs: each belongs to a single number, so every other number gets its own copy.

enabled: true

create_automation's default, so a copy answers customers immediately unless the request sets enabled to false.

1 key

Saved AI key per provider per account; copies on every number of the account use it without setup.

1 secret

Signing secret per automation for Call my webhook; each copy gets its own, shown on its page.

US$ 9 to US$ 0.75

Price per number per month by band; automations and their copies cost nothing extra.

How does your AI copy an automation to another number?

Through the easyCoexistence MCP tools, which work in ChatGPT, Claude, Claude Code, Codex and other MCP clients signed in to your account. Each automation belongs to one number and the dashboard editor builds one at a time, so your AI makes one copy per number. list_automations returns the original's full trigger, steps and settings; list_numbers returns the connection_id of every number; create_automation takes the same trigger, steps and settings with a new connection_id. Five tool calls cover the whole job, with the create and test calls repeated per number.

1list_numbersThe connection_id of each target number
2list_automationsThe original's trigger, steps and settings
3create_automationOne copy per number, enabled false
4test_automationA sample message on each copy
5update_automationenabled true once the tests read right

What should you ask your AI?

Name the original, the target numbers, what changes per number, and that copies start switched off. Asking for a summary table at the end makes the review quick, and naming the test message makes the replies comparable across numbers. If the numbers sit in different time zones or serve different addresses, put those details in the same request so the AI edits them while copying instead of afterwards.

One request that copies to three numbers
Copy my automation "AI assistant" from the downtown number
to the airport and mall numbers.
Create the copies switched off (enabled: false).
In each copy's instructions, replace the address and hours
with that branch's: airport ..., mall ...
Test each copy with "Where are you and when do you close?"
and show me a table: number, automation id, test reply.

What carries over, and what has to change per number?

The structure copies as is; the facts tied to one place usually do not. A Reply with AI step copied word for word gives the second branch the first branch's address, and an After hours trigger copied to a number in another city keeps the first city's Timezone. Check this list before turning copies on, or put the per-number changes in the copy request itself:

Copies as isTrigger and match, keywords and mode, step order, settings such as the 4-hour pause
Copies as isProvider and model of a Reply with AI step, since one key per provider serves every number
Change per numberName, so the list shows which branch each copy serves
Change per numberFacts in Instructions and fixed texts: address, hours, prices, the person to hand over to
Change per numberAfter hours Timezone, open days and From/To for each location
Not copiedRun history, status and the signing secret: each copy starts fresh

What has to be true on each target number?

Three things, and your AI can check each one with tools before it creates anything. First, the number must have automations on. create_automation on a number set to direct to your server succeeds but warns that the automation will not run; set_inbound_mode with mode managed fixes that, and it removes the direct webhook destination, so add the same URL as the forward URL if your system must keep receiving messages. Second, a Send a template step needs that template approved on the target number's WhatsApp Business Account: numbers in another account do not share templates, so check with list_templates. A test of that step does not call Meta, so it cannot catch a missing template. Third, a Reply with AI step needs the provider's key, which is already saved once for the whole account.

Which automation answers on the target number?

Only one automation answers a given message: keyword automations first, then First message, then After hours, then the catch-all, and the oldest first within a kind. A copy joins whatever the target number already has. If that number has an older catch-all, the copied catch-all never answers, because the older one wins every tie; if it has a keyword automation for the same word, the older one wins there too.

Ask your AI to run list_automations with each target's connection_id first and report overlaps by kind. Then you decide per number: turn the old one off, delete it, or merge both into one automation.

What does one create_automation call look like?

The same arguments as the original, with the target's connection_id, a new name and enabled set to false. Fields from list_automations that create_automation does not accept, such as id, status, last_run_at and created_at, are left out. A copy with Call my webhook keeps the URL; the payload carries the automation id and the number's phone_number_id, and each copy signs with its own secret.

create_automation for one target number (example)
{
  "connection_id": "<airport number, from list_numbers>",
  "name": "AI assistant (airport)",
  "enabled": false,
  "trigger": { "type": "message_received", "match": "any" },
  "steps": [
    {
      "type": "ai_reply",
      "provider": "anthropic",
      "model": "claude-haiku-5-5",
      "prompt": "You are the assistant of Bloom Cafe, airport branch, Terminal 2. Open 5:00 to 23:00. ...",
      "history": 10,
      "maxTokens": 1500
    }
  ],
  "settings": { "takeoverHours": 4, "aiMaxPerHour": 10 }
}

Copy or move?

Copying leaves the original where it is and creates a new automation. Moving is a different call: update_automation with a new connection_id moves the automation itself, and any run still waiting on the old number is skipped as superseded. Use a move when a branch changes phones, and a copy when a second branch should behave like the first.

Copies stay independent. A later change to the original does not reach them, so to keep several numbers in step, ask your AI to apply the same edit to each copy, reading each one first. Copying works within one easyCoexistence account, because the connector only sees the numbers of the account you signed in with.

How to set it up

  1. Name the original and the targetsAsk your AI to list your automations and numbers, and confirm which automation to copy and to which numbers.
  2. Check each target firstHave it confirm automations are on for each number, the templates the steps use are approved there, and which automations already exist.
  3. Create the copies switched offAsk for one create_automation per number with enabled false, a per-number name and the per-number facts edited in.
  4. Test every copyHave it run test_automation on each copy with the same sample message and show the replies side by side.
  5. Turn them onWhen the replies read right, ask it to set enabled to true on each copy with update_automation, then check the first runs.

Common mistakes

  • Leaving enabled out of the request. create_automation defaults to true, so each copy starts answering customers before anyone has read its test reply.
  • Copying a Send a template step to a number in another WhatsApp Business Account. The template does not exist there, the test cannot tell, and live sends fail.
  • Switching a direct number to managed for the copy without adding a forward URL. The direct destination is removed, and your own system stops receiving that number's messages.
  • Copying Instructions unchanged. The second branch then gives the first branch's address and hours to its customers.
Doing this with EasyCoexistence

easyCoexistence gives your AI the tools to copy an automation across your WhatsApp Business numbers in one request: it reads the original, creates a switched-off copy per number, tests each and turns them on when you approve, through one MCP connector with more than 30 tools. 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

Can I copy an automation from the dashboard instead?

Not with one click. In the dashboard you click New automation on the other number and rebuild the trigger and steps in the editor; for more than one or two numbers, asking your AI is faster.

Do copies update when I change the original?

No. Each copy is a separate automation. Ask your AI to make the same change on each one, and to read each copy before updating it, since update_automation replaces the whole steps list.

Is there a limit to how many numbers I can copy to?

The tools take one number per create_automation call, so the AI repeats the call per number. For a long list, ask for it in groups and review each group's summary table before the next.

Does copying need an active plan?

Yes. create_automation, update_automation and test_automation are write tools and need an active subscription; list tools keep working while billing lapses, so your AI can still read what exists.

Keep reading

Ready to get started?

Set up WhatsApp Coexistence in minutes, not months. The app keeps working on the phone.

Start Free Trial

Verified on