Resources · Make integration

WP Webhooks Make integrationAutomate WP Webhooks with Make.

Need other tools to write straight into your WordPress site? The WP Webhooks Make integration gives you 1 action module, Webhook Action, that sends data to WordPress. This guide is for site owners new to Make: connect the account, then build a first working scenario.

Try the WP Webhooks integration on MakeSee the 1 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the WP Webhooks Make integration do?

It lets a Make scenario, the automation you build in Make as a chain of bricks, push data into your WordPress site through the WP Webhooks plugin. Each brick is a module. WP Webhooks offers only one, Webhook Action, so the data always comes from another app and lands in WordPress.

Turn a sign-up into a WordPress user. Someone books a slot or joins a list in another tool, and Webhook Action passes their details to your site so the account exists without anyone typing it. The Make docs cite creating a user as a typical use.

Publish a post from a spreadsheet row. A content team drafts in a table, for example with the Airtable Make integration, and a finished row becomes a post on the site. Creating a post is the other example the docs give.

Feed WordPress from your CRM. A deal or contact changes in a sales tool, and the scenario forwards the useful fields to WordPress, where WP Webhooks receives them.

What Make does not do here: WP Webhooks has no trigger in Make, so nothing on your site can start a scenario through this app, and there is no Make an API Call module to reach anything beyond Webhook Action. If you weigh other tools for this job, the n8n vs Make comparison lays out the differences, and Make training helps if you start from zero.

Connect

How do you connect WP Webhooks to Make?

  1. 01

    Add the module and open the connection

    In your scenario, add the Webhook Action module, then click Create a connection. A connection is your WP Webhooks access linked to Make once and reused by every module of the app.

  2. 02

    Name it so you recognize it

    Giving the connection a name is optional, but useful as soon as you run more than one WordPress site: a name that matches the site saves you from sending data to the wrong one.

  3. 03

    Authorize and save

    Authorize Make on the page WP Webhooks shows you, or paste the key the app gives you, depending on what Make asks for. Then click Save and the module is ready to fill.

First scenario

Your first scenario with WP Webhooks

GoalWhen a new entry arrives in another app, Make sends its details to WordPress through Webhook Action.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Because WP Webhooks has no trigger, this first module comes from the app where your data starts, such as a form or a table.

  2. 02

    Pick the source and connect it

    Search that app by name, choose the module that watches new entries and click Create a connection. Each new entry becomes a bundle, one item passed from module to module.

  3. 03

    Add Webhook Action

    Click the + on the right of the first module, search WP Webhooks and pick Webhook Action. Connect your site, then map the values from the previous module into the fields, bold ones first.

  4. 04

    Test with Run once

    Click Run once, add a test entry in the source app, and read the bundles each module received. Then check WordPress to confirm the data arrived where you expected.

  5. 05

    Schedule and switch on

    Set the schedule on the first module. A new scenario checks every 15 minutes by default, which is also the shortest interval on the Free plan. Switch the scenario on and it runs by itself.

Modules

What the WP Webhooks module does

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

WP Webhooks1

Webhook Action

Action

In Make“Sends Data to your WordPress website.”

Webhook Action hands data collected elsewhere in your scenario to your WordPress site, where the WP Webhooks plugin turns it into something concrete, such as a user or a post.

When to use it
when data lives in another tool and WordPress should reflect it without copy and paste, like a new customer who needs a site account.
Watch out
each run counts as one operation, meaning one execution of the module on one bundle, and every bold field must be filled or the run stops.
Need help

Need help automating WP Webhooks with Make?

A person reads every message.

FAQ

WP Webhooks and Make: common questions

01Is the WP Webhooks Make integration free?
Yes. WP Webhooks is a standard app in Make, so it works on the Free plan. That plan allows 2 active scenarios, runs them at most every 15 minutes, caps each run at 5 minutes and files at 5 MB, with 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute, remove the limit on active scenarios and allow 40 minutes per run. Usage is counted in operations, so each time Webhook Action processes one item it uses one.
02What does it take to connect WP Webhooks to Make?
The Make documentation lists no specific prerequisite for this app. In practice you add the Webhook Action module, click Create a connection, optionally give it a name, then either authorize Make on the page WP Webhooks shows or paste the key it gives you, and click Save. The connection is stored once and reused every time the module appears in a scenario, so you only go through these steps a single time per site.
03Can WP Webhooks trigger a Make scenario in real time?
No. In Make, WP Webhooks has no trigger module at all, only Webhook Action. To start a scenario that ends in WordPress, open it with a trigger from another app, such as a form or a table, or simply let Make run it on a schedule. A new scenario runs every 15 minutes by default, and the Free plan cannot go below that. On a paid plan you can shorten the interval to 1 minute.
04What if a WP Webhooks module is missing in Make?
It depends on what you need. The app offers a single module, Webhook Action, and no Make an API Call module, so you cannot reach other parts of WP Webhooks from Make. If your data needs to be reshaped first, do it in the modules placed before Webhook Action. If the job goes beyond sending data to WordPress, look for another app in Make that covers it, or ask the team to review your setup with you.
05Is Make or n8n better for WP Webhooks?
It depends on the tool you already use. The same app often has an n8n node as well, so the choice rarely comes down to WordPress itself. On the Make side you get the Webhook Action module, a visual editor with Run once for testing and a Free plan that covers 2 active scenarios. If your other automations already run in n8n, check its node for this app, then compare it with Webhook Action on your real use case.
Same platform

Other docs you might need on this stack.

Browse all integrations