WhatsApp Flow Template in Make.com: Practical Setup Guide

Quick answer

Ok, let's clear up the confusing bit first.

Make provides a WhatsApp Business Cloud app with modules including Watch Events, Send a Message and Send a Template Message.

The official module list includes Send a Template Message, but it does not list a separate module called WhatsApp Flow or Flow Builder.

So, if you are searching for a WhatsApp Flow template in Make, think of the customer-facing form and the Make automation as separate parts. Use Make to receive the event, check stored customer details, route the interaction and continue the workflow.

For conditional routing, see this guide to the Make.com if() function.

Is there a free WhatsApp Flow template to download?

Make also publishes reusable workflow automation templates in its template library.

I could not verify an official Make template named WhatsApp Flows in the template library or the WhatsApp Business Cloud module list.

Instead of treating an unverified file as an official template, use the scenario blueprint below as your starting point. You can adapt the modules and field mappings to fit your own WhatsApp setup, CRM and customer journey.

The basic concept

Think of the customer-facing part as the form and the Make scenario as the automation around it.

A sensible scenario shape is:

WhatsApp event
  -> Router
  -> Look up the contact
  -> Choose the correct response
  -> Store submitted details
  -> Continue the customer journey

For example, you might ask a new contact for their name and email address. After receiving the response, your scenario could save those details in your chosen CRM or spreadsheet. When that contact gets in touch again, the scenario can follow the returning-customer route instead of repeating the sign-up process.

Before building the scenario

Get the connection and incoming event working before adding lots of routing or field mapping.

The WhatsApp Business Cloud app documentation uses a webhook to pass event data into a Make scenario.

If webhooks are new to you, start with my beginner's guide to Make.com webhooks. Run a test event and inspect the data Make receives before building the rest of the scenario.

You should also decide:

• Where customer details will be stored.
• Which field will identify an existing contact.
• What should happen when no matching contact is found.
• Which response should be sent after a successful submission.
• Where access credentials will be stored securely.

Build the Make.com WhatsApp scenario

Receive the WhatsApp event

Start with Watch Events and run the scenario in test mode. Send a suitable test interaction to the connected WhatsApp account, then inspect the resulting bundle.

Avoid guessing field paths from screenshots or examples. Map the values from the payload received by your own scenario.

Add a contact lookup

Add a lookup against your CRM, database or spreadsheet. Use a consistent contact identifier from the incoming event and decide how the scenario should behave when it finds a match.

Keep the first version simple:

• No matching contact: start your chosen sign-up route.
• Existing contact: continue to the normal enquiry route.
• Submitted details received: update the contact and send a confirmation.

This retains the useful idea from the original setup: ask for the required details before continuing with the remaining automation.

Route the interaction

Add a router after the event trigger or contact lookup. Give each route a clear purpose and add filters that are easy to test.

Useful route names might include:

• New contact.
• Existing contact.
• Form response received.
• Unsupported message type.
• Manual review required.

Do not try to handle every possible interaction in the first version. Get one route working properly, then add the others.

Choose the appropriate WhatsApp action

Use Send a Message or Send a Template Message according to the action required by your setup. Do not assume that Send a Template Message is a built-in Flow Builder.

Keep message content, field mapping and routing logic separate where possible. That makes the scenario easier to test when a message changes or a new customer route is added.

Store the submitted details

Map the returned customer values into your chosen storage system. A basic record might contain:

• WhatsApp contact identifier.
• First name.
• Surname.
• Email address.
• Sign-up status.
• The route the customer completed.

Only collect information that your workflow genuinely needs. Add validation and a fallback route for missing or unexpected values.

Send a confirmation

After storing the response, send a short confirmation and continue the customer journey. Keep this branch separate from the original sign-up request so that retries and duplicate events are easier to inspect.

Troubleshooting

I cannot find a WhatsApp Flow module

The documented module list does not show a standalone WhatsApp Flow or Flow Builder module. Use the available WhatsApp Business Cloud modules for the surrounding automation rather than searching for a module with that exact name.

The webhook receives no data

Check the connection, webhook selection and scenario status. Run the scenario in test mode and confirm that the relevant event reaches Make before adding routers or filters.

The scenario follows the wrong route

Inspect the value used by each filter. Compare the received payload with the filter condition rather than relying on what you expect the field to contain.

Returned fields are difficult to map

Keep a sample payload and work through each nested object or array carefully. For more complicated arrays, use my Make.com map() function guide as a reference.

The template does not appear

Check that the correct WhatsApp account and Make connection are selected. Confirm the name and configuration in the account connected to the scenario before rebuilding the module.

Ideas for using the blueprint

Once the basic route works, you could adapt it for:

• Lead capture and qualification.
• Appointment requests.
• Customer onboarding.
• Support triage.
• Feedback collection.
• Enquiry routing.
• CRM updates.
• Follow-up reminders.

Pick one clear use case and test the complete journey from the customer's first interaction through to the stored result. That is much easier to debug than building a huge scenario in one go.

Final thoughts

The useful part of this setup is not a mystery download. It is the structure: receive an event, identify the contact, choose a route, store the response and continue the conversation.

Start with that small blueprint. Once it works reliably with your own payload and connection, add more routes, personalisation and integrations.