Zapier Make integrationAutomate Zapier with Make.
Already running Zaps and starting to build in Make? The Zapier Make integration gives you 5 modules, including 1 instant trigger, so both tools can hand data to each other. This guide shows how the link works, how to set up the webhook, and how to build a first scenario.
Verified Trustpilot reviews · AI, automation & growth agency
What does the Zapier Make integration do?
The Zapier Make integration is a bridge between two automation tools. A Zap in Zapier can push data into Make, where a scenario (the automation you build in Make, a chain of modules) picks it up and carries on. In the other direction, a Make scenario can send data back to a Zap.
Keep a Zap you trust, extend it in Make. Add a Webhooks by Zapier step to the end of the Zap, point it at the address Make gives the Receive data trigger, and the rest of the process lives in a Make scenario. Handy when a team is moving work over step by step instead of rebuilding everything at once.
Feed a Zap from Make. When the data starts in a Make scenario but a colleague maintains the follow-up as a Zap, the Send data action hands it over. Each tool keeps the part its owner already knows.
Test the handoff with sample data. The Make doc has the new webhook wait for a first sample, so the setup is really three moves: create the webhook, copy its address into Zapier, send one test.
What the integration does not do: it has no search module and no generic API call module, so it cannot read your Zaps or list your Zapier history. It only moves data you send through it. The same app often has an n8n node too; the n8n vs Make comparison covers how the two tools differ. For the Make basics, see the Make review, and when a webhook refuses to fire, Make troubleshooting is the place to start.
How do you connect Zapier to Make?
- 01
Add a Zapier module
In your scenario, click the + and search for Zapier. For a Zap that sends data, pick Receive data. Make then asks you for a webhook, which is the address the Zap will post to, or for a connection, your account linked once to Make.
- 02
Create the webhook or connection
Click Add (or Create a connection), give it a name you will recognize later, such as the name of the Zap feeding it, and click Save. If a Zapier page opens, authorize Make there.
- 03
Paste the address into your Zap
Copy the webhook URL Make just generated. In Zapier, open the Zap, click Add a Step, choose Webhooks by Zapier, set the method to POST, click Continue and paste the address.
Your first scenario with Zapier and Make
GoalWhen a record changes in an app already wired into Make, Make sends it to a Zap that a teammate maintains in Zapier.
- 01
Create the scenario
On the Scenarios page, create a new scenario and click the + to add the first module. Pick the app where the data starts, for example your CRM or your form tool.
- 02
Set up the starting module
Click Create a connection for that app and fill its fields. Once the account is linked, Make shows the folders, sheets or objects it can read, so you pick instead of typing.
- 03
Add Send data
Click the + on the right of the first module, search for Zapier and pick Send data. Map the values from the first module into its fields by clicking them in the panel Make opens.
- 04
Test with Run once
Click Run once. Make runs the scenario one time; open the bubble above each module to read the bundles it received (a bundle is one item, like one contact).
- 05
Schedule and switch it on
Open the clock on the first module. A new scenario runs every 15 minutes by default, and 15 minutes is also the shortest interval on the Free plan. Set the schedule, then switch the scenario on.
The Zapier trigger in Make
1 module starts a scenario when something happens in Zapier. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Zapier as soon as it happens.
Receive data
Instant triggerIn Make“Receives data from the Zap.”
Receive data turns a Zap into the starting point of a Make scenario: whatever the Zap posts lands in Make as a bundle, ready for the next module. It pairs with a Webhooks by Zapier step on the Zap side.
What the Zapier modules do
Zapier gives you 4 modules in 3 groups. For each one: what it does for you, when to reach for it, and what to watch out for.
Step 1: Setup a new Zap or go to an existing one that contains the modules from which you wish to send data to Make.
1 moduleChoose POST as the method under the Webhooks by Zapier and click 'Continue'
Click on 'Add a Step' to insert the action Webhooks
ActionIn the docs onlyThis entry is not a module you drop into a scenario: it is the first setup step the Make documentation lists, and it happens inside Zapier. It gives your Zap a Webhooks by Zapier step, the piece that actually sends data out to Make.
Step 2: Create a new Make on Make using the Zapier - Receive data as the first module in your Make.
2 modulesCopy the newly generated webhook URL and let the webhook wait to receive sample data
Click the 'Add' button to create a new webhook
ActionIn the docs onlyHere the work moves to Make. Clicking Add on the Receive data trigger creates the webhook, a private address that belongs to your scenario and gives the Zap somewhere to post. Without it, the trigger has nothing to listen on.
Name your webhook and click Save
ActionIn the docs onlyNaming the webhook saves you guesswork later, when a list of webhooks sits in your account and you need the one tied to a given Zap. After Save, Make generates the URL you copy into the Zap step.
Other modules
1 moduleSend data
ActionIn Make“Sends data to the Zap.”
Send data goes the other way: it pushes values from your Make scenario into a Zap, so a process built in Zapier can pick up where Make stops.
Need help automating Zapier with Make?
A person reads every message.
