No-code WhatsApp automation: how to build your first flow

Every shop has one job that someone does the same way twenty times a day. A wholesale buyer writes "pikari dam koto?", and someone replies with the same three questions: business name, which items, how many pieces. Then they copy the answers into a sheet and forward the chat to the owner.

That job is the perfect first automation. It has a clear start, the same questions every time, and a clear end. Building it takes about half an hour on a no-code canvas, and it runs every time a buyer asks, including at 1 am.

This walkthrough builds that flow from scratch, step by step, then covers the WhatsApp rules every flow has to respect and how to test it safely.

What are the parts of a WhatsApp automation flow?

A flow is one trigger followed by a chain of steps. Whatever builder you use, the parts are the same.

A flow runs for one contact each time it is triggered, and it ends when that contact reaches the last step.

Which flow should you build first?

Pick the job that is most repetitive and least risky. If the flow goes wrong, it should cost you a confused chat, not a lost order.

We will build the wholesale flow.

How do you build a wholesale enquiry flow step by step?

The flow has six steps: trigger, first reply, three questions, a condition, a tag and assignment, then testing.

Step 1: Choose a specific trigger

Use a keyword trigger with words only wholesale buyers use: "wholesale", "pikari", "bulk". Avoid broad words like "price" or "dam", which half your customers send.

Good keyword matching ignores capital letters, so "Wholesale" and "WHOLESALE" both work. Also add the keyword to your Page's About section and any wholesale post: "Pikari dam janate 'wholesale' likhe message din."

Step 2: Send a first reply

Confirm what they asked for and tell them what comes next. People answer questions more readily when they know there are only three.

Assalamu alaikum! Pikari order er jonno 3 ta choto proshno korbo, tarpor amader wholesale team apnake dam janabe.

Step 3: Ask three questions and save each answer

Add three question steps. Each one sends a message, waits for the reply and saves it.

1. "Apnar dokan ba business er naam?" Save as business_name.
2. "Kon product gulo lagbe?" Save as products.
3. "Proti item koto piece? Shudhu number likhun." Save as quantity.

Then add an update-contact step that writes the three answers into contact fields, so they stay on the customer record after the flow ends. "Shudhu number likhun" (numbers only) matters for step 4.

Step 4: Branch on the quantity

Add a condition: if quantity is greater than 100, follow the "big order" branch; otherwise the "small order" branch. Numbers compare cleanly, which is why step 3 asked for numbers only.

Step 5: Tag and assign

• Big order: add the tag "wholesale: large" and assign the chat to the owner or the senior salesperson.
• Small order: add the tag "wholesale: small" and assign to the regular sales team.

End both branches with a message: "Dhonnobad! 30 minute er moddhe amader team apnake dam pathabe." Only promise a time your team can keep.

Optionally, add a Google Sheets step that appends a row with the three answers, so the owner sees every wholesale lead in one sheet.

Step 6: Test, then activate

Run a dry run first. It shows what each step would do without sending anything. Then activate the flow, send "wholesale" from a second phone, and answer the questions as a buyer would, including a wrong answer like "onek" instead of a number. See what happens, and fix the flow before real buyers find the gap.

What WhatsApp rules does every flow have to follow?

A flow does not get special permissions. The same WhatsApp rules apply as when a person sends the message.

• The 24-hour window. Within 24 hours of the customer's last message, a flow can send any message. After that, only an approved template. Read more on the 24-hour window.
• Templates for anything later. A "wait 2 days, then send" step needs a template at the send step, because the window has probably closed.
• Opt-in for marketing. Promotional messages should only go to contacts who agreed to hear from you.
• Other channels are stricter. On Messenger, Instagram and Telegram, a flow can only reach a contact who messaged you first.

If you plan order updates, our guide to order status templates that get approved has wording that passes review.

How do flows and an AI chatbot work together?

Let the flow handle the fixed job and the AI handle open questions. Problems start when both answer the same message.

Three habits keep them apart:

• Keyword rules first. A message that matches your keyword starts the flow; everything else goes to the AI.
• Assignment stops the bot. Once the flow assigns the chat to a person, an AI chatbot should stop replying there. In SaleMag it does.
• Test the whole conversation. Send the keyword, then ask an off-script question in the middle, and check that only one voice answers.

How does SaleMag's flow builder handle this?

SaleMag's automation flow builder is a visual canvas with all the parts above. Triggers include keywords, any incoming message, new contacts, orders placed, fulfilled or cancelled, abandoned carts and incoming webhooks. Steps cover WhatsApp text, media, buttons, list messages and templates, SMS and email, ask-question steps that save answers, conditions, waits in minutes, hours or days, tags, contact updates, assignment, Google Sheets and an HTTP request.

You can also describe the flow in plain words, such as "when someone writes wholesale, ask business name, products and quantity, tag and assign to sales", and the AI drafts the steps on the canvas for you to review. Every run is logged step by step, a run stops after 100 steps, and one contact cannot be in two runs of the same flow at once. Waits are relative, so "wait 1 day" works but "wait until 5 March" does not.

Which mistakes break a first automation?

Most broken flows have a trigger that is too broad or a question that accepts any answer.

• Broad keywords. "Price" as a trigger hijacks every price question.
• Free-text answers in conditions. "Onek" is not greater than 100. Ask for numbers or offer buttons.
• Promises the team cannot keep. "Reply in 30 minutes" at midnight sets up a complaint.
• No owner at the end. A flow that collects details and assigns nobody just moves the backlog.
• Never reading the log. The first week of runs shows you where real customers go off script.

When you have several flows tagging contacts, see customer segmentation with tags for keeping tags tidy.

Next steps

Write down the one job your team repeats most, with its exact questions. Build it as a six-step flow, dry-run it, and test it from a second phone. Read a week of run logs before you build the second one. To try it in SaleMag, start free or see pricing.