Resources · Make integration

WordPress Make integrationAutomate WordPress with Make.

Your site can publish, moderate and tidy itself while you work on something else. The WordPress Make integration hands you 40 modules for posts, comments, media, users and tags, chained inside a scenario, the automation you build in Make. Here is where to start.

Try the WordPress integration on MakeSee the 39 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the WordPress Make integration actually cover?

Make reaches your site through the Make Connector plugin, then treats WordPress like any other app: you place modules, one brick each, and chain them. Posts, categories, comments, media items, users, tags and taxonomies all have their own set, 40 modules in total, and seven of them can start a scenario on their own.

Three jobs come back on almost every site. Publishing: Watch Posts catches what goes live and the rest of the scenario carries it wherever your readers are. Moderation: Watch Comments, Search Comments and Delete a Comment keep the threads readable without you living in the admin. Housekeeping: Search Media Items and Update a Media Item walk the library file by file and fix what nobody ever has time to fix.

Now the honest part. Nothing here is live. All seven triggers are scheduled, which means Make reads the site when the scenario runs, not the second something happens. Everything also travels through the API of your site, the door apps use to talk to each other, at the address /wp-json/. If a CDN or a caching plugin keeps a copy of that address, Make gets stale or empty answers and a write can vanish, so that path has to stay out of the cache. The doc publishes no quota for this app: the ceilings you meet are the ones on your Make plan.

The same site can be driven from n8n, and the choice deserves five minutes. n8n vs Make lays out the criteria, and the WordPress n8n integration page shows the node by node version. When a scenario that worked starts misbehaving, Make troubleshooting covers the Make side of the problem.

Connect

How do you connect your site to Make?

  1. 01

    Install the Make Connector plugin

    Make talks to WordPress through a plugin. Download the Make Connector plugin from its page, then in your WordPress admin open Plugins, click Add Plugins, then Upload Plugin, pick the zip file, click Install now and finish with Activate Plugin.

  2. 02

    Copy your API key

    In the WordPress sidebar, open the Make Connector plugin and stay on the General Settings tab. Click Reveal next to the API key, copy the value and store it somewhere safe. The same tab regenerates the key later if it ever leaks.

  3. 03

    Create the connection in Make

    Add any WordPress module to a scenario and click Create a connection. Put https://your-site.com/wp-json/ in the WordPress REST API base url field, paste the key in API Key, then Save. That connection is your account linked to Make once, reused by every WordPress module.

First scenario

Your first scenario: reply to every new comment

GoalWhen a new comment arrives on your site, Make answers it so nobody waits.

  1. 01

    Start the scenario

    On the Scenarios page, create a new scenario and click the + to place the first module. Type WordPress in the search, then pick Watch Comments.

  2. 02

    Link your site

    Click Create a connection, paste the base URL and the API key, and save. From there Make can read the site and fills the lists inside the module for you.

  3. 03

    Add the answer

    Click the + on the right of the trigger and add Create a Comment. Map the ID the trigger hands you into the new module so the answer lands on the right thread.

  4. 04

    Test with Run once

    Leave a comment on the site, then click Run once, the button that plays the scenario a single time. Open each module and read its bundles: one bundle here is one comment.

  5. 05

    Set the clock and switch on

    Open the clock on Watch Comments. A new scenario runs every 15 minutes, which is also the shortest interval on the Free plan. Flip the switch and it keeps going.

Triggers

What can start a WordPress scenario?

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

WordPress1Watch Posts

Watch Posts

Scheduled trigger

In Make“Triggers when a new post is added.”

A post goes live and this trigger hands it to the scenario, with the content the site has just published. It is the usual entry point when what you want to automate starts with publication.

How it fires
Make checks the site on the scenario's schedule, so a post arrives on the next run, not the second it appears.
When to use it
an editorial team that wants every new article pushed to a newsletter, a social queue or a second site without anyone copying and pasting.
Watch out
the doc names this module in its caching trap. If a CDN or a caching plugin sits in front of /wp-json/, recent posts can stay invisible, so keep that path out of the cache.
WordPress2Watch Posts Updated

Watch Posts Updated

Scheduled trigger

In Make“Watches for updated posts.”

Publication is one event, editing is another. This one watches posts that change after they are online and sends the updated version into the scenario.

How it fires
scheduled, like every WordPress trigger here. On each run, Make asks the site what moved since the previous check.
When to use it
a price, a legal mention or a product description that lives inside an article and has to be mirrored somewhere else once it changes.
Watch out
a page that gets edited all day keeps feeding the scenario, and every bundle handled is an operation, the unit Make counts on your plan.
WordPress3Watch Categories

Watch Categories

Scheduled trigger

In Make“Triggers when a new category is added.”

Sections move more often than people expect. Watch Categories reacts when a new one shows up on the site and passes it to the rest of the scenario.

How it fires
Make polls the site at the interval set on the first module, and WordPress never pushes anything to Make here.
When to use it
a shop or a magazine where editors open sections themselves, and a map of the site has to stay in sync somewhere else.
Watch out
it sees the section arriving, nothing about what gets filed in it later. Pair it with Search Posts when you need the content too.
WordPress4Watch Comments

Watch Comments

Scheduled trigger

In Make“Triggers when a new comment is added.”

Every comment that lands on the site comes through this trigger, thread by thread, ready for the next module to read.

How it fires
on each run of the scenario. Make asks for the comments that appeared since the previous pass.
When to use it
moderation duty on a busy blog, or a support-style post where a quick answer changes the reader's day.
Watch out
a post that takes off sends a burst of comments at once, and each one is a separate bundle to handle, so keep the modules behind it light.
WordPress5Watch Media Items

Watch Media Items

Scheduled trigger

In Make“Triggers when a new media item is added.”

Anything dropped into the media library wakes this trigger. A photo, a PDF, a logo, each one travels into the scenario as a media item.

How it fires
Make reads the library at the rhythm you set on the first module, down to 15 minutes on the Free plan.
When to use it
a photographer or a shop where files arrive in batches, and someone always has to rename them afterwards.
Watch out
the Free plan handles files up to 5 MB and 512 MB of transfer. A heavy library belongs on a paid plan.
WordPress6Watch Users

Watch Users

Scheduled trigger

In Make“Triggers when a new user is added.”

A new account appears on the site and the scenario starts from it. Watch Users is the entry point for everything that happens around people rather than content.

How it fires
scheduled. The account waits for the next run of the scenario before Make sees it.
When to use it
a membership site, a training space, or a team blog where each new contributor needs a welcome message and a line in a tracker.
Watch out
personal data starts moving the moment this trigger runs, so carry into the next modules only what you actually need.
WordPress7Watch Tags

Watch Tags

Scheduled trigger

In Make“Triggers when a new tag is added.”

Someone invents a tag, this trigger catches it. The new label reaches the scenario as soon as Make notices it.

How it fires
nothing is pushed from WordPress. Make looks for new tags each time the scenario runs, then stops until the next one.
When to use it
keeping a tag list under control when several authors write, and each of them names things their own way.
Watch out
tags multiply quietly. Watch Tags tells you they exist, Search Tags and Delete a Tag are what actually clean the list.
Modules

What WordPress can do inside a scenario

WordPress gives you 32 modules in 8 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Posts

5 modules
WordPress1

Create a Post

Action

In Make“Creates a post.”

Feeds the site a new post built from whatever the scenario carries, and the article exists on WordPress at the end of the run.

When to use it
a content calendar in a spreadsheet, an approved draft sitting in a project tool, a report that always looks the same.
Watch out
the doc names this one in the caching trap. If the answer comes back without a post ID, the write never reached WordPress and /wp-json/ is being cached.
WordPress2

Update a Post

Action

In Make“Updates a post specified by its ID.”

Takes an article that already exists, found by its ID, and replaces what you map into it.

When to use it
a brand name that changed and now sits in a pile of old articles, or a banner sentence you keep at the top of a series.
Watch out
what you map wins over what is on the site, so try it on a single post with Run once before pointing it at a search.
WordPress3

Delete a Post

Action

In Make“Deletes a post specified by its ID.”

Removes a post from the site, by ID, with nothing left to click on afterwards.

When to use it
clearing the articles a test scenario created, or retiring pages an old import brought in.
Watch out
there is no undo here. Chained behind Search Posts it deletes everything the search returned, so read those results with Run once first.
WordPress4

Get a Post

Action

In Make“Returns info about a post specified by its ID.”

Reads one article and hands its content to the modules that follow, without changing anything on the site.

When to use it
a notification that should carry the real text and not just a link, or a check before another module writes over it.
Watch out
it works from an ID, so something before it, a trigger or a search, has to provide that ID.
WordPress5

Search Posts

Search

In Make“Searches for specific posts.”

Asks the site for the posts that match what you describe and sends them on, one bundle per post.

When to use it
a cleanup pass over old content, or a digest where the scenario needs the list before it can write anything.
Watch out
a search returns zero, one or many results, and everything after it runs once per result, each one costing an operation. The caching trap hits this module too.

Categories

5 modules
WordPress6

Create a Category

Action

In Make“Creates a category.”

Opens a new section on the site, ready to receive content.

When to use it
a shop launching a product family, or a magazine that opens a section for an event and closes it once the event is over.
Watch out
a scenario that runs often can recreate the same section again and again, so check the result with Run once before you switch it on.
WordPress7

Update a Category

Action

In Make“Updates a category specified by its ID.”

Rewrites a section you already have, identified by its ID.

When to use it
a rebrand where every section label changes at once, or a seasonal name you swap when the season turns.
Watch out
the new wording is what readers see on the site, so keep the old label in your notes before running this on the whole list.
WordPress8

Delete a Category

Action

In Make“Deletes a category specified by its ID.”

Takes a section off the site for good, by ID.

When to use it
the end of a cleanup, once the content has moved and the section only holds dust.
Watch out
no undo, and nothing asks you twice. Get the ID from Search Categories, look at what came back, then delete.
WordPress9

Get a Category

Action

In Make“Returns info about a category specified by its ID.”

Brings one section back into the scenario so the next module knows exactly what it works with.

When to use it
a routing step where the scenario checks the section before it decides what to do next.
Watch out
one ID in, one category out. To work from a name instead, put Search Categories in front of it.
WordPress10

Search Categories

Search

In Make“Searches for specific categories.”

Goes through the sections of the site and returns those that match, one bundle each.

When to use it
building the list of sections before a bulk rename, or checking a section exists before creating it twice.
Watch out
zero results is a normal answer, and the modules behind it simply do not run. Plan for that case instead of assuming a match.

Comments

5 modules
WordPress11

Create a Comment

Action

In Make“Creates a comment.”

Publishes a comment on the site, written by the scenario rather than by a reader.

When to use it
an acknowledgement under every question, or an editorial note the team drops on each new article.
Watch out
it writes in public. Send it through Run once and read what shows up on the site before the scenario runs on its own.
WordPress12

Update a Comment

Action

In Make“Updates a comment specified by its ID.”

Edits a comment that is already online, from its ID.

When to use it
a support thread where the first answer is a placeholder and the real one arrives later.
Watch out
readers who already saw the comment will see the new version, so keep the edits useful rather than cosmetic.
WordPress13

Delete a Comment

Action

In Make“Deletes a comment specified by its ID.”

Wipes a comment off the site.

When to use it
the spam a filter let through, or a thread that turned sour while nobody was around.
Watch out
gone is gone. Behind Search Comments it clears every match at once, which is exactly what you want and exactly what hurts if the search was too wide.
WordPress14

Get a Comment

Action

In Make“Returns info about a comment specified by its ID.”

Pulls a single comment back, text and all, without touching it.

When to use it
a moderation queue where a human reads the comment somewhere else before anything is decided.
Watch out
it needs the ID, which usually comes from Watch Comments or Search Comments right before it.
WordPress15

Search Comments

Search

In Make“Searches for specific comments.”

Sweeps the comments of the site and returns the ones that match, one bundle per comment.

When to use it
a moderation pass on an old post, or a list of questions to answer that you want out of the admin and inside your own tools.
Watch out
a popular site sends back a long list, and every result costs an operation. Narrow the search before you widen it.

Media Items

5 modules
WordPress16

Create a Media Item

Action

In Make“Creates a media item.”

Uploads a file into the media library and gives the scenario the media item that comes out of it.

When to use it
product photos arriving from a supplier, documents that belong on the site, a cover image produced earlier in the scenario.
Watch out
the Free plan stops at files of 5 MB and 512 MB of transfer, so a library of heavy pictures needs a paid plan.
WordPress17

Update a Media Item

Action

In Make“Updates a media item specified by its ID.”

Reworks a file already in the library, found by its ID.

When to use it
a batch of images uploaded in a hurry that nobody documented, and a scenario that goes back over them one by one.
Watch out
the file itself stays where it is. What changes is only what you map into the module.
WordPress18

Delete a Media Item

Action

In Make“Deletes a media item specified by its ID.”

Drops a file out of the library.

When to use it
the leftovers of an import, or visuals from a campaign that ended and still weigh on the site.
Watch out
anything that displayed that file shows a hole afterwards. Check with Search Media Items before deleting in bulk.
WordPress19

Get a Media Item

Action

In Make“Returns info about a media item specified by its ID.”

Returns one media item so the rest of the scenario can work from it.

When to use it
attaching the right visual to a message the scenario is about to send somewhere else.
Watch out
one ID gives one item. For a set of files, Search Media Items is the module you want.
WordPress20

Search Media Items

Search

In Make“Searches for specific media items.”

Combs the library and hands back the files that match, one at a time.

When to use it
an audit of what the site actually stores, or the list a cleanup scenario needs before it touches anything.
Watch out
results come as separate bundles, so a wide search turns into a lot of operations before you notice.

Users

5 modules
WordPress21

Create a User

Action

In Make“Creates a user.”

Creates an account on the site from data the scenario already carries.

When to use it
a training space where every buyer gets access, or a newsroom where freelancers come and go.
Watch out
an account is not a small thing to hand to a robot. Run once, check what landed on the site, then let it run on its own.
WordPress22

Update a User

Action

In Make“Updates a user specified by its ID.”

Modifies an existing account, found by its ID.

When to use it
a contributor whose details changed, or a batch of profiles to bring back in line after a migration.
Watch out
mapping an empty value writes an empty value. Prepare the data before the module, not after.
WordPress23

Delete a User

Action

In Make“Deletes a user specified by its ID.”

Closes an account and removes it from the site.

When to use it
an offboarding routine, or the accounts a wave of bot registrations left behind.
Watch out
the harshest delete of the set, with no step back. Get the list out with Search Users, read it, then run the deletion.
WordPress24

Get a User

Action

In Make“Returns info about a user specified by its ID.”

Looks one account up and passes it on, read only.

When to use it
checking who is behind a comment or an article before the scenario decides anything.
Watch out
what comes out is personal data. Keep it inside the scenario and send on only what the next module really needs.
WordPress25

Search Users

Search

In Make“Searches for specific users.”

Runs through the people registered on the site and returns those that match.

When to use it
a synchronization with your CRM, or the census that comes before a cleanup of dormant accounts.
Watch out
zero, one or many, as always with a search. Everything behind it repeats per result, which adds up fast on a big site.

Tags

5 modules
WordPress26

Create a Tag

Action

In Make“Creates a tag.”

Adds a tag to the list your site uses.

When to use it
a campaign that needs its own label, created by the scenario rather than by hand in the admin.
Watch out
the same tag created twice under a slightly different spelling is how a tag list falls apart. Search Tags first, create second.
WordPress27

Update a Tag

Action

In Make“Updates a tag specified by its ID.”

Corrects a tag that is already in use, by ID.

When to use it
a typo spotted after the fact, or a naming rule the team agreed on once the list had already grown.
Watch out
the label changes everywhere it appears on the site, which is the point and also the risk.
WordPress28

Delete a Tag

Action

In Make“Deletes a tag specified by its ID.”

Retires a tag from the site.

When to use it
the end of a tag cleanup, once the useful labels have been kept and the rest is noise.
Watch out
no way back, and a tag removed by mistake takes real time to rebuild. Keep the list from Search Tags before you start.
WordPress29

Get a Tag

Action

In Make“Returns info about a tag specified by its ID.”

Returns a single tag to the scenario.

When to use it
a check inside a bigger scenario, when the next module has to be sure the label exists.
Watch out
it answers on an ID only. Names go through Search Tags.
WordPress30

Search Tags

Search

In Make“Searches for specific tags.”

Scans the tag list and returns what matches, one bundle per tag.

When to use it
the inventory before any tag cleanup, and the safety net you place in front of Create a Tag.
Watch out
the answer can be empty, which simply means nothing matched. Handle that case before the modules behind it try to work on nothing.

Taxonomies

1 module
WordPress31

Search Taxonomies

Search

In Make“Searches for specific taxonomies.”

The Make directory lists a second taxonomy search next to the one from the doc. Same family, same output shape: zero, one or several bundles.

When to use it
the same exploration work, from the module the directory shows in its own list.
Watch out
two modules with nearly the same name live in this app. Try both in a test scenario and keep the one that answers.

Other

1 module
WordPress32

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Calls any endpoint of the WordPress API with the connection you already created, which covers what the other modules leave out.

When to use it
a corner of the API the module list never touches, or a very specific read you cannot get any other way.
Watch out
the safety rails stop here. You write the call yourself, and the same caching rule applies to /wp-json/.
Need help

Need help automating WordPress with Make?

A person reads every message.

FAQ

Questions people ask next

01Is the WordPress Make integration free?
Yes. WordPress is a standard app in Make, so it works from the Free plan. What the Free plan limits is scale: 2 active scenarios, 15 minutes minimum between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of transfer. Paid plans bring the interval down to 1 minute, lift the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations, one operation being one module handling one bundle, so a scenario that searches and then loops over results costs more than a single write.
02What do you need before connecting WordPress to Make?
A WordPress account with the Make Connector plugin enabled, and nothing else. You install the plugin from its plugin page, upload the zip through Plugins, Add Plugins and Upload Plugin, then activate it. Once active, the plugin appears in the WordPress sidebar with a General Settings tab, where Reveal shows your API key. On the Make side you paste that key and the base URL of your site's API, the one ending in /wp-json/. The connection is created once and every WordPress module in your scenarios reuses it.
03Do WordPress triggers fire in real time?
No. All seven WordPress triggers are scheduled, which means Make asks your site what is new each time the scenario runs. Nothing is pushed from WordPress: an instant trigger would be a webhook, a call the app sends to Make the moment something happens, and this app does not offer one. In practice you wait one interval, 15 minutes by default on a new scenario and on the Free plan, 1 minute on a paid plan. For editorial or moderation work that gap goes unnoticed. If you truly need the exact second, that is a different design.
04What if a module you need is missing?
Make an API Call is the answer. It reuses the connection you already created and reaches any endpoint of the WordPress API, so anything the listed modules skip is still within reach of the scenario. Before writing a call, check the trap the doc describes: Make talks to WordPress at /wp-json/, and a CDN, a host or a caching plugin that stores copies of that address hands back stale or empty answers. Write requests must never be cached. The documentation publishes no quota for this app, so the limits you meet come from your Make plan.
05Make or n8n for WordPress?
It depends on who maintains the automation. Make is built around a visual scenario where each module is a bubble you connect, which suits a team that wants to read the flow at a glance and can start on the Free plan. n8n leaves more room to people comfortable with code and with hosting the tool themselves. Both cover WordPress. The honest way to choose is to look at the modules you need, the interval you can live with, and who will fix the thing when it breaks at the worst moment. The comparison linked higher up goes through the criteria one by one.
Hack'celeration Lab

Get our weekly automation tips.

No spam. Unsubscribe anytime.

Same platform

Other docs you might need on this stack.

Browse all integrations