Zapier WordPress Integration: Connect It or Replace It
You can connect WordPress to Zapier using the official Zapier for WordPress plugin, and the free Zapier plan works for basic testing. For anything beyond a handful of Zaps, you will hit task limits quickly, and for WordPress-native automation, Krom Automation handles the same workflows without per-task billing or a third-party dependency.
This guide covers both paths honestly. The Zapier integration is the right answer when you need to connect WordPress to an external service that has no native WordPress plugin. A self-hosted automation plugin is the right answer when the trigger and the action both live inside WordPress, because routing that traffic through Zapier’s servers adds latency, cost and a failure point you do not need.
We will walk through the exact setup steps for both, show you what each handles well, and be direct about where each one breaks down. If you are running this decision for a client site or an agency stack, the cost section will matter more than the setup section.
Browse the full feature list for Krom Automation if you want to see the native option before reading the setup steps.
What the Zapier WordPress Integration Actually Connects
The Zapier for WordPress plugin creates a two-way bridge. WordPress can act as a trigger source, firing a Zap when something happens on your site. It can also act as an action target, receiving data from Zapier and creating or updating content inside WordPress.
The plugin authenticates using WordPress application passwords, introduced in WordPress 5.6. You generate a password inside your user profile and paste it into Zapier during the connection flow. No OAuth app, no custom API keys, no coding required.
WordPress events you can use as Zapier triggers:
- New post published (any post type, filterable by category or tag)
- New user registered
- New comment posted
- Post updated (fires on any save, including autosave in some configurations)
- WooCommerce order created or completed (requires WooCommerce installed)
What Zapier can do inside WordPress as an action target:
- Create a new post or page with title, content, status and category
- Update an existing post by ID
- Create a new user with role, email and username
- Create a WooCommerce product or update an existing one
What Gets Synced: Field-Level Reference
| WordPress field or event | Where it lands in Zapier |
|---|---|
| Post title | post_title key in the trigger payload |
| Post content (raw HTML) | post_content key, unsanitised |
| Post author ID | post_author key as an integer |
| Post status at trigger time | post_status key (publish, draft, etc.) |
| Post permalink | guid key in most configurations |
| User email on registration | user_email key |
| User display name | display_name key |
| User role at registration | roles key as a comma-separated string |
| Comment author name | comment_author key |
| Comment content | comment_content key |
| Comment status | comment_approved key (0, 1, or spam) |
| WooCommerce order total | total key as a string with currency symbol |
| WooCommerce order status | status key (processing, completed, etc.) |
| WooCommerce customer email | billing.email nested key |
| Custom post meta fields | Not included by default; requires custom code or a Pro Zap filter |
| User meta fields | Not included by default; requires a separate HTTP Request Zap step |
The two rows at the bottom are where most Zapier setups run into trouble. Custom post meta and user meta do not appear in the default trigger payload. Pulling them requires a second Zap step that calls the WordPress REST API directly, which consumes an additional task per execution and adds conditional logic complexity.
Step-by-Step: Connecting WordPress to Zapier
Step 1: Install the plugin
Go to Plugins Add New inside your WordPress admin. Search for “Zapier for WordPress” and install the plugin listed as published by Zapier Inc.
Activate it. No settings page appears after activation because the plugin works entirely through the REST API and application passwords.
Step 2: Create an application password
Go to Users Profile for an administrator account. Scroll to the Application Passwords section near the bottom. In the “New Application Password Name” field, type something identifiable like “Zapier Integration 2026”.
Click Add New Application Password. Copy the generated password immediately. WordPress will not show it again.
The account you use here sets the permission scope for every Zap. Use a dedicated administrator account rather than your personal one, so you can revoke access cleanly if the integration is ever compromised.
Step 3: Authenticate in Zapier
Inside Zapier, create a new Zap and search for “WordPress” as the app. Choose your trigger or action and click Sign In. Zapier asks for three fields: your WordPress site URL (with https://), your WordPress username, and the application password you just generated.
Zapier will test the connection by hitting your site’s REST API. A green “Connection Successful” message confirms the link is live.
Step 4: Build your trigger
Select the WordPress event. Zapier will ask you to load sample data by fetching real recent records from your site. This step is required before you can map fields to the action.
If your site has no recent posts, users or orders, Zapier cannot load samples and the builder stalls. Create a test record in WordPress, then return to Zapier and click Load More.
Step 5: Configure the action and map fields
Choose the destination app and the action. Map WordPress trigger fields to the destination fields using Zapier’s dropdown interface.
Every mapped field counts as data that travels through Zapier’s servers. Turn on the Zap and run a live test with a real WordPress event to confirm the payload arrives correctly.
The Zapier connection takes about 15 minutes to configure. The cost of that connection compounds every month at scale, and most sites discover that cost only after the bill arrives.
Zapier Pricing: What WordPress Sites Actually Pay
The free Zapier plan allows 100 tasks per month across 5 Zaps. One task equals one action step in one Zap execution.
A Zap with two action steps consumes two tasks per trigger firing. Our detailed breakdown is in the Zapier pricing 2026 guide, but the headline numbers are these:
| Scenario | Tasks per month | Zapier plan needed | Annual cost (approx) |
|---|---|---|---|
| New post published, notify Slack | 30 to 50 | Free | $0 |
| Form submission to Google Sheets + email | 200 to 600 | Starter ($29.99/mo) | ~$360 |
| WooCommerce orders to CRM + Slack + email | 600 to 2,000+ | Professional ($73.50/mo) | ~$882 |
| Agency: 10 client sites, 3 Zaps each | 3,000 to 10,000+ | Team ($103.50/mo+) | ~$1,242+ |
That last row is what stings agencies. Every client site runs independently, but all tasks pool into one Zapier account. A busy month on one site can push you into the next billing tier for all clients simultaneously.
If your automations stay inside WordPress, paying per task for that traffic makes no sense. A user registers, gets a welcome email, and has their role set.
Those three things touch only your WordPress database. Routing them through Zapier’s servers costs money and adds an external dependency for something your own server can handle in under a second.
The Native Alternative: Krom Automation
Krom Automation is a visual workflow automation plugin that runs entirely on your WordPress server. It connects WordPress events to automated actions using a drag-and-drop canvas, with no per-task fees and no third-party account required. The free version includes 16 triggers and 21 actions covering users, posts, comments, media and WooCommerce.
For WordPress-to-WordPress automations, the workflow is: choose a trigger, drag an action node onto the canvas, map your fields using merge tags, and activate. Execution logs are stored in your own database, and the analytics dashboard shows success rate per workflow so a failing workflow does not hide behind aggregate numbers. That matters because a workflow failing silently on WordPress looks identical to a working one until you check the per-step audit trail.
The Krom Automation documentation walks through triggers, actions and workflows if you want to understand the data model before installing.
Side-by-side: Zapier vs Krom Automation for WordPress
| Dimension | Zapier + WordPress plugin | Krom Automation |
|---|---|---|
| Where automations run | Zapier’s servers (external) | Your WordPress server (self-hosted) |
| Cost model | Per task, per month | Flat annual or lifetime licence |
| Free tier limits | 100 tasks/month, 5 Zaps | No task limits, no run caps |
| Custom post meta access | Extra Zap step required | Native via merge tags |
| Execution logs | 30-day history on paid plans | Full per-step audit trail, your database |
| WooCommerce triggers (free) | Order Created, Order Completed | Order Created, Order Completed |
| WooCommerce depth (Pro) | Depends on WooCommerce Zapier add-on | Native Pro triggers and actions included |
| External service connections | 6,000+ app integrations | 24 Pro integrations (WordPress-native focus) |
| Data leaves your server | Yes, every execution | No |
| AI actions | Via OpenAI Zapier app (tasks consumed) | Built in free, bring your own API key |
The external service count is where Zapier wins outright. If you need WordPress to talk to a service that has no native WordPress plugin, Zapier is often the fastest path. If everything you are automating lives inside WordPress, paying for that reach is waste.
Every task that touches only your own database should not be paying rent to a third-party server. That cost is invisible in month one and painful by month twelve.
Running Both: The Practical Agency Stack
The cleanest setup for most agencies is not either-or. Use Krom Automation for all WordPress-native workflows and reserve Zapier for the connections that genuinely need it. This keeps task counts low, which keeps Zapier on a cheaper plan, while giving you full native automation inside WordPress.
Krom Automation Pro adds an incoming webhook receiver with a unique secret URL per workflow and HMAC-SHA256 signature verification. That receiver can accept payloads from Zapier, Make, or any external service. So you can run a Zap that collects data from an external app and fires a webhook at WordPress, and Krom Automation handles everything that happens next.
The external-to-WordPress handoff costs one Zapier task. Everything after that is free.
For agencies managing multiple sites, Krom Automation’s Enterprise plan covers unlimited sites for $369 per year. That is a flat cost regardless of how many client workflows run across how many sites.
The equivalent Zapier spend at 3,000 tasks per month is roughly $882 per year, before you factor in additional app connections or team seats. The detailed agency cost comparison lives in what client automation costs per site.
Connecting Specific Plugins to Zapier, and the Native Alternative
Most guides cover WordPress and Zapier generically. The real questions are about specific plugins. Here is where the native approach typically wins:
Form plugins: If your form submissions need to reach Google Sheets or a CRM, Zapier works but consumes tasks for every submission. Krom Automation has native integrations for Gravity Forms, WPForms, Contact Form 7, Fluent Forms, and Elementor Forms. A form submission triggers the workflow directly in WordPress, with zero external API calls for the trigger step.
Email marketing: For syncing WordPress users or form entries to Mailchimp, ConvertKit or ActiveCampaign, native integrations handle subscribe, tag and list management without routing through Zapier. The Mailchimp integration, ActiveCampaign integration, and FluentCRM integration all cover this natively.
WooCommerce: The Zapier for WordPress plugin covers basic order triggers. For deeper WooCommerce work, including subscription events, the WooCommerce Subscriptions integration in Krom Automation Pro handles subscription lifecycle events that the standard Zapier plugin does not expose at all.
Membership and LMS: MemberPress, LearnDash and MemberPress have no meaningful Zapier triggers beyond basic webhook workarounds. Krom Automation Pro includes dedicated trigger sets for MemberPress and LearnDash covering signup, expiry, course completion and quiz events.
What Does Not Transfer and What Breaks
This is the section most guides skip. Read it before you build.
Custom post meta does not appear in the default trigger payload. If you are automating custom post types with ACF or Meta Box fields, Zapier only sends the standard WordPress post fields. You will need a separate Zap step using the HTTP Request action to call the WordPress REST API for the meta, which adds cost and failure surface.
Polling delay means Zapier is not real-time. Most WordPress triggers in Zapier use polling rather than webhooks, checking for new data every 1 to 15 minutes depending on your plan. A user who registers and expects an instant response may wait up to 15 minutes for a Zap to fire. Krom Automation executes via Action Scheduler, which fires within seconds of the trigger event on a normally trafficked site.
Zap history is capped and then deleted. Zapier keeps 30 days of task history on paid plans and 7 days on free. If an automation fails and you do not notice within that window, the evidence is gone. Krom Automation stores every execution log in your own database with no automatic expiry.
Multi-step Zaps multiply task cost. A Zap that checks a condition, sends an email, and updates a CRM record consumes 3 tasks per trigger firing. On a site with 500 form submissions per month, that Zap alone costs 1,500 tasks, which is above the Starter plan’s 750-task limit.
Application password revocation is site-level. If you revoke the application password Zapier uses, every Zap connected to that site stops silently. There is no Zapier-side notification. You discover the failure when a task that should have run did not.
Silent failures are the real cost of external automation. You pay for the task whether or not the action completed, and you find out what broke only when a customer complains.
Troubleshooting: The Three Real Failure Modes
Failure mode 1: The Zap is not triggering
The most common cause is the polling interval. Zapier polls WordPress for new events on a schedule, not in real time.
If your test fires immediately after activating a Zap, Zapier may not have polled yet. Wait 2 to 5 minutes, then check the Zap history in the Zaps Task History section of your Zapier dashboard.
If no history entries appear at all, check whether the WordPress REST API is accessible. Go to yoursite.com/wp-json/wp/v2/posts in a browser.
If that returns a 403 or a redirect to a login page, a security plugin or server firewall is blocking the REST API. Common culprits are Wordfence with “Disable WordPress REST API for logged out users” enabled, or a Cloudflare rule blocking unauthenticated API requests.
Failure mode 2: Authentication errors after initial setup
Application passwords stop working when the WordPress user account is deleted, when the specific application password is revoked from Users Profile Application Passwords, or when a security plugin force-resets all application passwords after detecting a login anomaly. The fix is to generate a new application password and re-authenticate the Zapier connection. Go to Zapier Connected Accounts, find your WordPress connection, and click Reconnect.
Failure mode 3: Payload mapping errors when field names change
If you update a form plugin, a WooCommerce version, or a custom post type structure, Zapier’s saved field map may reference field names that no longer exist in the trigger payload. The Zap continues to fire but sends empty or incorrectly mapped data downstream.
The fix is to open the Zap, click Trigger Test, load fresh sample data, and remap any fields that have changed. This is a manual step that Zapier does not alert you to.
Also from wpRigel
Pollify is a Gutenberg-native poll, survey and quiz plugin. Polls are built as real blocks inside the editor, so there are no shortcodes to paste and no separate interface to learn. It is worth knowing about if you collect audience feedback alongside your automations.
Commandify is a command palette for the WordPress admin. Press Cmd or Ctrl plus K to jump anywhere, search everything, and run admin actions without clicking through menus.
It is the only command palette plugin with real WooCommerce order, product and customer commands built in. For agencies managing client sites, it replaces a significant amount of menu-clicking.
When to Keep Zapier, When to Replace It, and What We Would Do
Keep Zapier when you need to connect WordPress to a service that has no native plugin integration. Posting a new WordPress article to a LinkedIn Company Page, syncing WooCommerce orders to a fulfilment system’s proprietary API, or pushing form submissions into a Salesforce instance are legitimate Zapier use cases because those connections have no WordPress-native equivalent.
Replace Zapier with a native plugin when the trigger and the action both live inside WordPress. Welcome emails, role changes, post status automations, CRM syncs to FluentCRM, email list subscriptions, LMS enrolments, and WooCommerce order handling all fall into this category. Routing any of those through an external service adds cost, latency and a failure point that serves no one.
What we would do: install Krom Automation free from the WordPress.org plugin directory, migrate any WordPress-to-WordPress Zaps in the first week, and keep Zapier only for the connections that need its external reach. Most sites find they can drop to Zapier’s lowest paid plan or eliminate it entirely within 30 days. The 20 WordPress automations most sites should have is a useful checklist for identifying what can move to native.
See Krom Automation plan pricing to compare annual and lifetime options across 1, 5 and unlimited sites.
FAQ
Do I need a paid Zapier plan to use it with WordPress?
The free Zapier plan supports up to 100 tasks per month across 5 Zaps. That is enough for light testing or a single low-volume workflow. Most WordPress sites with active forms, user registrations, or WooCommerce orders exceed 100 tasks within the first week of real use and need at least the Starter plan at $29.99 per month.
Why does my Zap fire on post update instead of only on publish?
Zapier’s “New Post” trigger polls the WordPress REST API for posts with a publish status and a date newer than the last check. If you update a post and it triggers the Zap again, it means Zapier is seeing the updated timestamp as a new record. The workaround is to add a Zapier filter step that checks whether the post date equals the post modified date, but that filter step consumes an additional task per execution.
Can Zapier send form submissions to Google Sheets without custom code?
Yes, using a contact form plugin that supports Zapier triggers (WPForms and Gravity Forms both do via their Zapier add-ons) or by using the standard WordPress REST API. Each submission consumes one Zapier task for the trigger and one for the Google Sheets action, so a site with 300 monthly submissions uses 600 tasks for this one workflow alone. Krom Automation’s Google Sheets integration handles the same sync natively without per-row task costs.
Is it safe to give Zapier an application password for my WordPress site?
Application passwords are scoped to the WordPress REST API and cannot be used to log into the WordPress admin directly. The main risk is account-level: if the Zapier account is compromised, the attacker can create posts, users and WooCommerce products using the REST API. Mitigate this by creating a dedicated WordPress user for the Zapier connection with the minimum role needed (Editor for post creation, Administrator only if user creation is required), and review the application passwords list in your user profile monthly.
What happens to my Zaps if Zapier has an outage?
Zapier queues tasks during outages and attempts to replay them after service resumes, but the replay window is not guaranteed for all plan levels. Time-sensitive automations, like sending a password reset email or confirming a WooCommerce order, may fire minutes or hours late during an incident. Self-hosted automation runs on your own server, so the only uptime dependency is your hosting provider rather than a third-party service.