To connect WordPress to Zapier, install and activate the Zapier for WordPress plugin, then on Zapier's Apps page add a connection, choose WordPress and enter your site's Base URL, username and password. Your site must be public, and the user should have Editor or Administrator permissions. Security plugins and plain permalinks are the usual causes of errors.
WordPress and Zapier connect so that new posts or comments can trigger actions elsewhere, and so other apps can create posts or users on your site. Getting the connection to stick is mostly about clearing the way past security settings.
What you need first
- The Zapier for WordPress plugin, installed and activated. WordPress.com users need a plan that allows plugins.
- A launched, publicly accessible site. Zapier recommends SSL to protect your login credentials.
- A WordPress user with Editor or Administrator permissions; at least Editor if you want to post as other authors.
Connecting your site
- Install and activate the Zapier for WordPress plugin.
- In Zapier, go to the Apps page, click + Add connection, search for WordPress and select it.
- Enter your Base URL, without /wp-admin/ or wp-login.php, plus the Username and Password.
- Click Yes, Continue to WordPress.
- Create a Zap using a WordPress trigger such as New Post, or an action such as Create Post.
Triggers, actions and searches
| Type | Options |
|---|---|
| Triggers | New Post, Updated Post, New Comment, New Media, New User, Updated User |
| Actions | Create Post, Update Post, Upload Media, Create User, Update User, API Request (Beta) |
| Searches | Find Post, Find User, Find or Create User |
Find User doesn't search users with custom roles created by plugins, so if a membership plugin adds its own roles, plan around that.
Popular builds include sharing every new post to social channels, sending new comments to Slack, and creating draft posts from a form or spreadsheet. My guide to automating WordPress publishing goes deeper on that last one.
Why the connection fails
| Problem | Likely cause | Fix |
|---|---|---|
| Authentication errors | Default plain permalink structure | Switch permalinks to Post Name |
| 403 or blocked requests | Security or caching plugin | Allow Zapier in the plugin's settings |
| Blocked at the edge | Cloudflare | Add an allowlist rule for Zapier |
| IP allowlist doesn't hold | Zapier's IP addresses aren't static | Use another method, or a static IP connection where your Zapier plan offers it |
Zapier names the plugins known to interfere: Jetpack, Wordfence Security, iThemes Security, WP Rocket, JWT Authentication, Limit Login Attempts Reloaded and WPS Hide Login. If you run any of them, check its settings before you connect.
Security plugins and allowlists
The Zapier Help Center sums up the main trap: a caching or security plugin such as Wordfence, Jetpack Protect or WPS Hide Login, or plain permalinks, can block Zapier with 403 or authentication errors. And because Zapier's IPs aren't static, IP allowlisting isn't reliable unless you're on a plan with a static IP address connection. Fix permalinks first, then work through your security plugins one at a time.
Three starter Zaps
New posts to social
Use the New Post trigger and send each published post to your social scheduling app, so nothing gets forgotten after you hit Publish.
Comments to Slack
Use the New Comment trigger to post each new comment into a Slack channel, so someone on the team replies quickly.
Drafts from a form
Use a form or spreadsheet app as the trigger and Create Post as the action. Set the post status to draft so a person checks it before it goes live, and use Upload Media if the form collects images.
Before you switch it on
- Permalinks set to Post Name, not plain.
- SSL on the site.
- A dedicated Editor or Administrator user for Zapier.
- Security and caching plugins checked against Zapier's list.
- Cloudflare, if you use it, set to allow Zapier.
Another automation route
n8n lists WordPress among its built-in app nodes, if you'd rather run automations on a platform you host. My n8n and Zapier comparison sets out the differences, and my list of WordPress plugins worth installing helps if you're reviewing your security stack at the same time.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
My advice for WordPress and Zapier
Set permalinks to Post Name and make sure the site's on SSL before you connect. Create a dedicated Editor user for Zapier rather than using your own admin login. If the connection fails, check your security plugins and Cloudflare before anything else. Start with one simple Zap, such as New Post to a Slack channel, and build from there.
Want your tool on this list? Featured spots and reviews here are paid partnerships. Here's how to partner with me.
Frequently asked questions
Do I need a plugin?
Yes. The Zapier for WordPress plugin must be installed and activated.
What permissions does the WordPress user need?
Editor or Administrator is recommended; at least Editor to post as other authors.
Why do I get a 403 error?
Security plugins, caching, a firewall or Cloudflare may be blocking Zapier.
Can I create posts from Zapier?
Yes, with the Create Post action.
Does it work on a private site?
No. The site must be publicly accessible.


