Resources · Make integration

Simplified Webhooks Make integrationAutomate Simplified Webhooks with Make.

Need Make to notice when an Airtable record appears, changes or disappears? The Simplified Webhooks Make integration gives you 3 scheduled triggers and 1 API module. This guide is for teams new to Make: link your account, then build a first working scenario.

Try the Simplified Webhooks integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Simplified Webhooks Make integration do for you?

The Simplified Webhooks integration lets Make start a scenario, the automation you build in Make, when your Simplified Webhooks account reports Airtable records that are new, updated or deleted. You pick the change to follow, and the modules after it decide what happens next.

Catch fresh records. Watch New Airtable Records hands each new record to the rest of your scenario as a bundle, one item passed from module to module, so an order or a lead can reach the tool that needs it.

Keep a copy in sync. Watch Updated Airtable Records picks up edited records, which suits a sales team that mirrors Airtable data in another app and wants the copy to follow every correction.

Clean up after a deletion. Watch Deleted Airtable Records tells the scenario which records were removed, so the matching entry elsewhere can be archived instead of lingering.

What this app does not offer: there is no instant trigger and no ready-made action besides Make an API Call. All three triggers are scheduled, so Make checks on the scenario's schedule rather than the moment a record moves. For anything else, the API module calls the service directly. The same app may also exist in n8n; our n8n vs Make comparison lays out how the two tools differ. Before you choose a plan, Make pricing explains how operations are counted, and Make training helps if scenarios are brand new to you.

Connect

How do you connect Simplified Webhooks to Make?

  1. 01

    Create an API key

    You need an active Simplified Webhooks account. Open your profile settings there, click the button that creates a new API key, and copy the key shown on screen. Make asks for it in the last step.

  2. 02

    Open the connection window

    In your Make account, add any Simplified Webhooks module to a scenario and click Create a connection. A connection is your account linked to Make once, then reused by every module of this app.

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear label helps when you run several accounts. Paste the API key you copied, or follow the on-screen instructions, to create the connection.

First scenario

Build your first scenario with Simplified Webhooks

GoalWhen a new Airtable record shows up through Simplified Webhooks, Make passes it to an API request on the same account.

  1. 01

    Start a blank scenario

    From the Scenarios page, create a new scenario and click the big + in the middle of the editor. That empty circle becomes your first module, the brick that starts everything.

  2. 02

    Add the trigger

    Search for Simplified Webhooks, pick Watch New Airtable Records, then click Create a connection and paste your API key. Fill the fields Make shows you for that module.

  3. 03

    Chain the API module

    Click the + on the right of the trigger and add Make an API Call. It reuses the same connection, and you can map values from the record the trigger received into the request.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles each module received, so you can check the record data before anything runs on its own.

  5. 05

    Schedule and switch on

    Open the clock on the first module. A new scenario checks every 15 minutes by default. Adjust it if your plan allows a shorter interval, then switch the scenario on.

Triggers

Triggers: what starts your scenario

3 modules start a scenario when something happens in Simplified Webhooks. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Simplified Webhooks as soon as it happens.

Simplified Webhooks1Watch Deleted Airtable Records

Watch Deleted Airtable Records

triggerIn the docs only

Gives your scenario the Airtable records that were removed, so whatever depended on them elsewhere can be tidied up instead of pointing at nothing. The Make documentation lists this module by name only, so read the fields it shows you once the connection exists.

How it fires
scheduled, Make checks the app on the scenario's schedule.
When to use it
a customer record disappears from Airtable and the matching contact in your mailing tool should be archived too.
Watch out
a deletion rarely comes with an undo, so test with Run once on a dummy record before you point it at real data.
Simplified Webhooks2Watch New Airtable Records

Watch New Airtable Records

triggerIn the docs only

This is the module most first scenarios start with: every record created in Airtable arrives as its own bundle, ready to feed the next module. Each bundle that a later module processes costs an operation, the unit Make counts on your plan.

How it fires
scheduled, Make checks the app on the scenario's schedule.
When to use it
a new order lands in your Airtable base and your team wants it passed to another tool without copying it by hand.
Watch out
since the check is scheduled, a busy base can deliver several records in one run, so plan the next modules for more than one bundle.
Simplified Webhooks3Watch Updated Airtable Records

Watch Updated Airtable Records

triggerIn the docs only

You get the records whose content changed, which is what keeps a second copy of your data honest when someone fixes an address or a status in Airtable. Choose it over the new-records trigger when edits matter more than creation.

How it fires
scheduled, Make checks the app on the scenario's schedule.
When to use it
a deal moves to a new stage in Airtable and the same stage must appear in the CRM your sales team reads.
Watch out
if a later module writes back to the same Airtable record, the change can be picked up again, so avoid editing the watched record inside this scenario.
Modules

Modules: what else Simplified Webhooks can do

Simplified Webhooks gives you 1 module. For each one: what it does for you, when to reach for it, and what to watch out for.

Simplified Webhooks1

Make an API Call

ActionIn the docs only

Reach any endpoint of the Simplified Webhooks API from your scenario, reusing the connection you already created. Because the app ships no other action, this module is how you go past the three triggers.

When to use it
you need something the listed modules do not cover, and the Simplified Webhooks API offers it.
Watch out
you write the request yourself, so keep the API reference of Simplified Webhooks open and check the response in Run once before switching on.
Need help

Need help automating Simplified Webhooks with Make?

A person reads every message.

FAQ

Simplified Webhooks and Make: frequent questions

01Is the Simplified Webhooks Make integration free?
Yes, on the Make side. Simplified Webhooks is a standard app, so it works from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution at most and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) go down to a 1 minute interval and count usage in credits per month. You still need your own Simplified Webhooks subscription, whose price is set by the vendor on its pricing page.
02What is needed to connect Simplified Webhooks to Make?
An active Simplified Webhooks account and an API key from it. In your profile settings, click the button that creates a new key and copy it. Then add a Simplified Webhooks module in Make, click Create a connection, optionally name the connection, and paste the key. The same connection then serves the three triggers and the API module, so this setup only happens once per account you want to link.
03Does the Simplified Webhooks trigger react in real time?
No. Going by their names (the Make documentation lists them without a type), all three triggers, for new, updated and deleted Airtable records, are scheduled: Make checks the app on the scenario's schedule instead of being called the moment a record changes. A new scenario checks every 15 minutes by default. The Free plan keeps at least 15 minutes between scheduled runs, while paid plans can go down to 1 minute. For a faster reaction, shorten the schedule on a paid plan.
04What if a Simplified Webhooks module is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the Simplified Webhooks API with the connection you already have, so you are not limited to the three triggers. You write the request based on the vendor's API reference, then test it with Run once to read the response before turning the scenario on. The Make documentation for this app is AI-generated from the vendor docs, so confirm important details with Simplified Webhooks.
05Make or n8n for the Simplified Webhooks integration?
It depends on the tool your team already works in. On Make, this app gives you 3 scheduled triggers and Make an API Call, all sharing one connection, plus the visual editor with Run once for testing. The same app often has an n8n node as well, so if your automations already live in n8n, check that node first. The choice rests on your existing workflows and the modules each tool lists, not on a general ranking.
Same platform

Other docs you might need on this stack.

Browse all integrations