Webhooks

Webhooks = the glue to automations and the best way to receive data.

A webhook is basically a custom URL that you’re creating which allows you to point other services to you (your automation) - and so when you do something (eg changing a record, changing a status) you can trigger a webhook to start a flow.

When you set up a custom webhook it’s essentially willing to receive a request - you just need to send a request to this server.

What does a webhook do?
A webhook triggers a scenario when something happens in another app (eg “a new form was submitted” or “a purchase happened”). It starts your automation.

Real Examples:

• Typeform sends a webhook to MAKE when a form is submitted

• Stripe sends a webhook when someone pays you

• Zapier or custom apps send data to MAKE using a webhook URL

APIs vs. Webhooks: What is the difference?
A webhook is the opposite of an API call. Instead of you asking for data (API), the app sends you data automatically (webhook).

How it works in MAKE:

1. You add a Webhook module (first module in the scenario)

2. MAKE gives you a custom webhook URL

3. You paste that URL into the app you want to receive data from

4. When that app sends data, your scenario runs