Complete Guide To Webhooks In Make (Formerly Integromat)

Hideyuki Shibata
6 min readOct 31, 2023

--

If you have been using Make for a while, you might have heard the word webhook here and there. In this post, I’ll cover everything you need to know about webhooks in Make.

Why even use a webhook?

The time-based trigger in Make is good and all, but it’s definitely not a one-size-fits-all method for triggering scenarios.

Problem with the time-based trigger

Say you have a scenario where you want to trigger as soon as you give it an input, but that only happens once every 5 days and you don’t even know when you’ll be giving that input. If you use a time-based trigger in thie case, you’ll be wasting a lot of operations as you would have to let the scenario watch your action every minute for nothing 99% of the time for the remaining 1% where you do finally give an input.

Meet webhook

That’s where webhooks come in. With webhooks, you are able to send information to Make, meaning you don’t have to force your scenario to keep watching if you gave it an input or not. When you give an input, send that information over to Make using a webhook.

Want no-code automation tips and secrets? I got you covered.

Subscribe to my newsletter. Don’t worry. I can’t code either.

Step by step guide: how to use webhooks in Make

I’m going to be using Airtable in addition to Make to demonstrate how to use webhooks.

1. Choose Custom webhook

I won’t go too deep into what Custom mailhook is now as what you are probably after is Custom webhook. I’ll cover Webhook response later in this article. Now, hit Add, then Save. You can leave the IP restriction field empty.

You will end up with a screen like this:

The blue URL is what you after. You open this URL either manually or programatically to send information to Make. Hit Copy address to clipboard.

2. Setting up a button field in Airtable

I’m just going to create an empty base for the sake of this demo. Let’s create a button column.

As you can see, I have pasted the webhook URL into the URL formula field as a part of the following formula.

"https://hook.eu1.make.com/32m5lbte31ukhmajpzlu6svv5vp2q5q5"&"?record_id="&RECORD_ID()

What this button does is when you click the button, it opens up a new tab with the webhook URL with the record ID of the row your button is located in. RECORD_ID() is a Airtable’s native formula that gives you the ID of whatever row you are working with.

When this button is clicked, you are letting Make know that you are sending the current record ID. Why send the record ID? Because we’ll be using the record ID in the next step.

Now, let’s give the Airtable some input. It can be anything but you can create something similar to mine just for the sake of this demo.

Lastly, let’s press one of the buttons. Any button will do. A new tab should open that says “Accepted” with the URL that looks like this:

https://hook.eu1.make.com/32m5lbte31ukhmajpzlu6svv5vp2q5q5?record_id=recUAfQPwJ3WcrFiN

What it’s basically saying is “Hey Make I’m triggering a notification for you. Please remember the record ID recUAfQPwJ3WcrFiN.”

3. Back to Make: receiving a notification

Now, if you go back to Make, you should see the message “Successfully determined”. You don’t have to worry about what it exactly means for now, but what it’s basically saying is that “I’ve successfully received your notification with the record ID.”

Press OK.

4. Set up a Get a Record module

Now that you’ve successfully sent a notification to Make, it’s time to work with the actual content. To get the content from Airtable, you set up a Get a Record module. This is where you use the record ID that was sent via the webhook call.

Now, once you choose the module and choose the right Base and Table, your screen should look like this:

For the Record ID field, you specify the one you received via the webhook call.

Press OK.

4. See it in action!

Let’s hit Save 💾 and then press Run once ▶️. The scenario is now ready and listening to your action. Now, go back to Airtable and press any button you want to press. I’ll press the button that belongs to the record that contains Apple.

Did a new tab pop open and say “Accepted”? Then you are good to go! Close the tab and go back to Make. You should see this screen:

It’s always nice to see these green checks and know things are working. If you click on the 1 signabove the Airtable module, you should see the output with the content you sent.

Let’s try with another button. I’ll go with the button that belongs to the row that contains Microsoft:

Voila! Now you have Microsoft in Make.

This is a very simple demo but imagine you had a company description, company URL, name of the CEO, etc. in other columns. You could retrieve all that information in Make and do a whole lot of things.

Press a button in Airtable and:

  • send an email to acompany
  • make AI write content on acompany

The rest is up to your imagination.

Moving on

This post only scratches the surface of what you can do with webhooks in Make! There’s a lot more you can do as you dig deeper. I’ll cover them in another post.

--

--

Hideyuki Shibata
Hideyuki Shibata

Written by Hideyuki Shibata

Automation enthusiast. Come see my Bento: bento.me/hide

No responses yet