Log inStart Free Trial
Meta Tech Provider

20 WhatsApp automation recipes you can copy

A WhatsApp automation recipe is one trigger plus a short flow of steps that a business copies onto its own number. The twenty below cover greetings, opening hours, menus, button taps, common questions, AI replies, lookups in your own system, opt-outs and follow-ups. Each names the trigger, the match and the steps, so you can build it in an editor or ask your AI to create it.

easyCoexistence runs these recipes on the WhatsApp Business number you keep in the app, through Meta's official Cloud API: fixed texts, approved templates, AI replies on your own key, and your own systems through a signed webhook.

4 matches

Message triggers: Every message, Has keyword, First message, After hours. A tag added or your system calling a URL start without a message.

30 steps

Most steps per line, 60 in all, branches nested 4 deep: Reply with text, Reply with AI, Wait, Stop, questions, branches, agents.

20 seconds

How long Call my webhook waits for your system's answer; a {"reply"} in it is sent to the customer.

1,380 minutes

Longest Wait step, 23 hours; a reply from your phone in the meantime skips the steps after it.

4 hours

Default pause on a chat after you answer it from the WhatsApp Business app, adjustable from 0 to 168 hours.

How is each recipe written?

Every recipe has a name, then the trigger and its match, then the steps in order, then one line on when to use it. The trigger on a number is usually A message arrives, and the match is one of four: Every message, Has keyword (with Contains, Starts with or Is exactly), First message or After hours; two other triggers, A contact gets a tag and Your system calls a URL, start without a message. Steps use the editor's names. Text in quotes is ready to paste; words in brackets are yours to fill in. {{first_name}}, {{name}}, {{message}} and {{phone}} are filled in from the customer's chat when the step runs. Any recipe can be built in the editor under New automation, or by asking ChatGPT or Claude, which turn it into one create_automation call.

Which recipes greet customers and cover your hours?

Five recipes handle the moments when a customer writes first or writes while nobody is there. The welcome recipes run on First message, which fires the first time a chat reaches the automations, and again after about 30 quiet days. The hours recipes run on After hours, whose Timezone, Open on days and From and To times decide when the business counts as closed. A template step can go out at any time; text steps need the customer to have written in the last 24 hours, which is the case when they just did.

1. Welcome textFirst message → Reply with text: "Hi {{first_name}}! Thanks for writing. How can we help?" Use: greet new contacts.
2. Welcome couponFirst message → Send a template, an approved one with the code in its body and {{1}} = {{first_name}}. Use: a first-order discount.
3. Away noticeAfter hours, Open on Mon to Fri, From 09:00 To 18:00 → Reply with text with your reopening time. Use: nights and weekends.
4. One away reply per burstAfter hours → Wait 2 min → Reply with text. Use: a customer who sends five messages in a row gets one notice.
5. Vacation noticeAfter hours with no day ticked under Open on → Reply with text with your return date. Use: closures and holidays.

Which recipes answer common questions?

Six recipes answer the questions that come in all day with the same words. Five of them use Has keyword, because keyword automations are checked before every other kind, so they answer ahead of an AI or a welcome; the menu option is a path inside the menu automation. Contains suits distinctive words inside a sentence. Is exactly suits short replies such as a menu number or a button label, where the whole message must be the keyword. Capital letters and the spaces around the message do not matter; accents and punctuation do, so list the variants customers type.

6. Price listHas keyword, Contains: price, prices, how much → Reply with text with your price link. Use: the question you get most.
7. Address and mapHas keyword, Contains: address, location, where are you → Reply with text with a map link. Use: walk-in customers.
8. Payment detailsHas keyword, Contains: pix, payment, bank transfer → Reply with text with how to pay. Use: exact details, never improvised.
9. Menu with buttonsHas keyword, Is exactly: menu, hi, hello → Ask a question with buttons Prices, Hours and Talk to a person, saved to a field → Split into paths on that field. Use: let customers pick a topic with a tap.
10. Menu optionInside the menu automation, one path of Split into paths per option: the field is Prices → Reply with text for that option → Go back to a step (the menu). Use: add an option by adding a path, not another automation.
11. Button tap answerHas keyword, Is exactly: the button's label, such as See prices → Reply with text. Use: answer a quick reply button.

Which recipes put your own AI to work?

Four recipes put your own AI to work: three use Reply with AI, which needs your own key from Anthropic, OpenAI or OpenRouter saved under AI keys. The model reads your Instructions and up to 20 earlier messages of the chat (10 by default), then writes the reply, while an Agent answers step hands the chat to an AI agent with its own instructions, knowledge files and tools. A talk-to-a-person line is added to the instructions for you, and when you answer the chat from the phone, the automation steps back on it. AI replies are capped at 10 per chat per hour by default, so two automated systems cannot loop on your key.

12. AI assistantEvery message → Reply with AI with your prices, hours and policies in Instructions. Use: anything the keyword recipes do not catch.
13. AI after hoursAfter hours → Reply with AI. Use: your AI covers the night, and you answer from the app during the day.
14. Talk to a personHas keyword, Is exactly: person, human, agent → Reply with text: "A person from our team will answer here." → Hand to a person. Use: a clear exit that pauses the bot on that chat and emails you.
15. Log, then answerEvery message → Call my webhook that saves the message and returns no reply → Reply with AI. Use: a record in your sheet or CRM.

Which recipes hand the message to your own system?

Three recipes use Call my webhook, which POSTs the message and the chat's last 10 messages to your URL, signed with X-EC-Signature. If your system answers {"reply": "..."} within 20 seconds, that text goes to the customer. This is how an automation reaches data it does not hold, such as an order's status, and how n8n, Make, Zapier or your backend take part. To read or write data without building a reply endpoint, a Call an API step calls any https API and keeps its JSON answer for later steps. A system that answers with no reply field simply records the message, and the run moves on to the next step.

16. Order statusHas keyword, Starts with: order, track → Call my webhook; your store looks up the order and returns {"reply"}. Use: "where is my order?"
17. Your n8n agentEvery message → Call my webhook to an n8n workflow that writes the reply. Use: an agent with your tools and memory.
18. STOP and unsubscribeHas keyword, Is exactly: stop, unsubscribe → Reply with text confirming → Call my webhook marks the contact opted out.

Which recipes follow up later or handle voice notes?

Two recipes use what arrives differently. A Wait step parks the run for 1 to 1,380 minutes, and the steps after it are skipped if you answer that chat from the phone in the meantime; a new message that starts the same automation again also replaces it. Media reach automations as text: photos arrive as [image] followed by the caption, and voice notes as [voice message] followed by the words, written out on your own OpenAI or OpenRouter key; with no such key a voice note is the placeholder alone, which a keyword rule can match to ask the customer to type.

19. Quote follow-upHas keyword, Contains: quote, estimate → Reply with text → Wait 120 min → Reply with text: "Any questions about the quote?"
20. Voice note replyHas keyword, Is exactly: [voice message] → Reply with text: "Thanks for the audio! Could you type your question?" Use: voice notes that could not be written out, when no OpenAI or OpenRouter key is saved.

How do several recipes run together on one number?

Only one automation answers a given message. When several match, keyword automations go first, then First message, then After hours, then Every message; within the same kind, the one created first wins. That order lets you stack recipes safely: keyword answers (6 to 9, 11, 14, 16, 18, 20) take their words, the welcome takes new chats, the away or vacation notice takes closed hours, and the AI assistant or n8n agent takes the rest. Two catch-alls never both run, and a second one on the same number stays silent, so keep one.

How to set it up

  1. Pick a recipeChoose one from the grids and note its trigger, match and steps.
  2. Open a new automationIn the Automations tab, click New automation, then Use this on the closest example, or Start from scratch.
  3. Set the triggerUnder When a message arrives, pick the match, then the keywords and Where the word has to be, or the hours.
  4. Add the stepsUnder Then, add the steps in the recipe's order and paste the texts, filling in your details.
  5. Test, then switch it onSave with the switch Off, run Try it from the Test button, then switch it On and click Save.

Common mistakes

  • Stacking two catch-alls, such as an AI assistant and an n8n agent, both on Every message. Only the older one ever answers, and nothing warns you; keep one, or give one of them keywords.
  • Adding a step after Call my webhook when your system already returns a reply. Both go out, so the customer gets two messages; let the webhook answer alone, or return no reply.
  • Putting a short word such as hi in Contains. It also matches this and shipping; use Is exactly for greetings and menu numbers.
  • Expecting a Wait follow-up to cancel when the customer's answer is caught by another automation. It goes out anyway unless you replied from the phone; keep follow-ups for replies you expect to be silent.
Doing this with EasyCoexistence

Build them by asking ChatGPT or Claude through the connector, or in the editor, with no extra charge for automations; Meta bills any messages to your own WhatsApp Business Account and your AI provider bills the tokens. 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 my AI build several recipes in one request?

Yes. Ask for them together, such as a welcome, an away notice and a price list. The assistant calls list_numbers once, then create_automation for each recipe and test_automation on each, and reports what it created.

Do any of these recipes need an AI key?

Only the ones with Reply with AI, recipes 12, 13 and 15. Fixed texts, templates, waits and webhooks run without a key; recipe 17 uses whatever AI your n8n workflow calls, on that workflow's own account.

Can a recipe send a picture or a PDF?

Yes. A Send a picture or file step sends one of your pictures or PDFs, with a caption if you like, inside the 24 hours after the customer last wrote, and an AI agent can send them by itself. A link in a text reply also works, and Reply with text itself sends text.

Can I copy a recipe to another number?

Yes. Ask your AI to read the automation with list_automations and create the same one on the other number's connection_id, then test it there; in the editor, change the Connection of a saved automation to move it.

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