WhatsApp Flows in Make.com: Free Download 🚀

Let’s head on over to make.com and set everything up! Firstly, we are assuming that you are all setup and receiving data when someone messages your number. If you aren’t please see this guide.
Important – please also note your permanent access token.

Step 1: Import the template scenario

I’ve added a template scenario for you to download here so you have somewhere to start! You’ll need to import this by pressing the ‘import scenario’ button on a blank scenario.

Step 2: Google Sheets Spreadsheet

Set up a basic google sheets spreadsheet with Number, First Name, Surname, Email and Completed Sign Up Form. Map this spreadsheet to the initial spreadsheet in the make.com scenario.

This will serve as a basic database (you can use your own CRM or other platform to store your data) that we can query when someone messages us.

The concept here is that someone must complete a sign up form before they can then proceed to the next stage.

Step 3: Your Permanent Access Token

Add your permanent access token to the set variable module. This will provide the authorisation required to send WhatsApp messages.

Step 4: Understanding a flow token

A Flow Token is a unique identifier that connects the specific WhatsApp flow that the user has completed. Think about it as the way that you know what form a user has completed.

Step 5: Completing the set multiple variables module

Now you can explore the multiple variables module. This should be pretty self explanatory, but is the way messages are sent back to the user. You can customise this based on your setup and what you want to send back to the user.

Step 6: Handling the response from the user

Now we know when the user completes the form, we want to do some clever stuff with that data. 

• Note the filter ‘message type = interactive’ in the first router. This will then send the message down a different path.
• You’ll also note the filter which shows that the user hasn’t completed the welcome form.
• Then also notice the filter with the ‘flow token’ – this is how we know the user has completed a ‘sign up form’ (or any other token of your choice).
• Now we can just use a normal make.com WhatsApp module to reply to the message saying ‘thanks for signing up’.
• Finally, we add that data to the google sheets file, so next time they message we know they’ve already completed the sign up process and we can just query the first_name field to reply directly to the user, making it feel ‘super personalised’.

Step 7 (Alternative): Using a response message as apposed to a template message

One of my preferred options is to just use a ‘response message’ as apposed to a template message, so you don’t have to go through the laborious approval process with meta. To do this – note the ‘Example > Individual Message’ HTTP module. In here, you’ll find the fields mapped and you can just edit the body text in the set variables module. 

Step 8 (Alternative): Creating a flow without a template

If you are confident creating JSON, then I would suggest using my example JSON as a starting point.

You can then just build out a WhatsApp flow, utilising meta’s WhatsApp flow builder. Then all you need to do is query this in your set variables module (Flow Name, Flow Token, Flow ID, Screen and Button Text). This allows you to reply to messages without the need to use the template builder.