Make.com is a legitimate choice for multi-app automation, and we will say that plainly before anything else. If you need to connect Salesforce, Slack, Google Sheets, and a WordPress post in one scenario, Make.com handles that well.

The friction appears when WordPress is not just one stop on the journey but the center of it. Operation-based billing, data leaving your server, and limited access to WordPress internals create costs and constraints that most tutorials never mention.

This article covers the real setup process, the scenarios where Make.com earns its place, and the specific situations where a WordPress-native tool like Krom Automation costs less, runs faster, and gives you more control over your own data.

We are not here to push you away from Make.com if it genuinely fits your workflow. We are here to give you the information to make that call accurately.

How the Make.com and WordPress Connection Actually Works

Make.com connects to WordPress through the official Make Connector plugin, available in the WordPress.org plugin directory. You install it, generate an API key inside WordPress, and enter that key inside your Make.com scenario. The plugin exposes a subset of WordPress functionality over a custom REST endpoint.

The actions available through the connector cover the basics:

• Create or update a post
• Create a user
• Upload media
• Add a comment
• Manage tags and categories

That list is functional for simple content pipelines. It is not functional for anything that touches WordPress internals beyond post and user management. WooCommerce order data, custom post type meta, LearnDash enrollment events, MemberPress subscription changes, none of these are reachable through the connector without workarounds.

The alternative connection method, using Make’s HTTP module to hit the WordPress REST API directly with application password authentication, removes the connector plugin dependency. It also removes any pretense that the setup is beginner-friendly. You are manually constructing API calls, handling authentication headers, and parsing JSON responses for every action.

Operation-Based Billing: What It Costs in Practice

Make.com bills by operations, not by scenarios or tasks. Every module that executes in a scenario counts as one operation.

A scenario with 5 modules that runs 200 times per month consumes 1,000 operations. That arithmetic compounds quickly once you add filters, error handlers, data stores, or iterators.

Make.com Plan	Monthly Operations	Monthly Cost	Cost per 1,000 Operations
Free	1,000	$0	$0 (capped)
Core	10,000	$10.59/month	~$1.06
Pro	10,000	$18.82/month	~$1.88
Teams	10,000	$34.12/month	~$3.41

A WooCommerce store with 300 orders per month, each triggering a 6-module scenario (fetch order, transform data, send Slack message, update sheet, tag customer, log result) consumes 1,800 operations. That fits the Core plan, until you add a second automation.

The cost is not ruinous, but it is unpredictable. A traffic spike or a marketing campaign that doubles your order volume doubles your operation consumption, sometimes pushing you into the next billing tier mid-month.

Operation-based billing sounds reasonable until you count every module in every branch of every scenario. The number is almost always higher than the estimate.

For context, WordPress automation pricing varies widely across platforms. Self-hosted plugins charge once per year or per lifetime, with no per-execution cost regardless of how many workflows fire.

Where Make.com Genuinely Wins

We want to be clear about the scenarios where Make.com is the right call, because recommending the wrong tool wastes everyone’s time.

Make.com earns its place when:

• Your WordPress site is one of several systems. If a form submission needs to create a post, update a CRM record, send a Slack notification, add a row to Google Sheets, and trigger an email campaign, Make.com handles all of that in a single scenario. A WordPress-native plugin can’t reach the external services without its own integrations for each one.
• Your team lives outside WordPress. Non-developers who are comfortable in Make.com’s visual builder but would never touch a WordPress plugin settings screen may find Make.com’s interface easier to maintain.
• The trigger is always external. If a Typeform submission or a Stripe payment is what starts the automation, and WordPress is just the destination, Make.com’s trigger library is much broader than anything WordPress-native.
• You need cross-account data routing. Moving data between separate business systems that happen to include WordPress is exactly what Make.com was designed for.

Where Make.com Creates Real Problems

The friction points are specific, and they matter for a significant share of WordPress sites.

WordPress Internals Are Out of Reach

Make.com can create a post. It cannot react to a LearnDash course completion, a MemberPress subscription expiry, a WooCommerce subscription renewal, or a user role change triggered by another plugin.

These events fire inside WordPress and are only accessible to code running inside WordPress. An external platform cannot listen to them without a webhook bridge, which adds latency, failure points, and complexity.

The connector plugin exposes what the WordPress REST API exposes. Plugin-specific events, custom database tables, and internal hooks are invisible to it.

Your Data Leaves Your Server

Every scenario that processes WordPress data sends that data to Make.com’s servers for transformation before returning a result. For most content, that is a minor concern.

For sites handling personal data, payment information, or anything under GDPR, it is a compliance consideration that requires deliberate handling. A self-hosted automation plugin processes everything on your own server, in your own database, with no data leaving the environment.

The Connector Plugin Has a Documented Bug History

WordPress.org reviews for the Make Connector plugin include reports of crashes on plugin activation, memory errors on high-traffic sites, and conflicts with security and caching plugins. These are not universal, but they are consistent enough to be a factor in your evaluation.

Sites running lean plugin stacks and standard hosting are usually fine. Sites running 40+ plugins with aggressive caching have more exposure.

Debugging a Failed Scenario Is Harder Than It Looks

When a Make.com scenario fails, the error is in Make.com’s interface. The WordPress log shows nothing unless the failure produced a PHP error.

Debugging requires switching between two systems, correlating timestamps, and often re-running the scenario manually to reproduce the issue. A WordPress-native plugin writes every step to an execution log inside WordPress, where you already are.

Debugging an automation failure should not require two browser tabs, a timestamp correlation exercise, and a manual re-run. It should show you the step that failed and why.

Real Automation Recipes: What Actually Works

Here are four scenarios with honest assessments of where each tool performs better.

Scenario	Make.com	Krom Automation	Better choice
New WooCommerce order → Slack notification + Google Sheets row	Native. Connects both services in one scenario.	Needs Pro messaging and Sheets integrations.	Make.com, if you already subscribe
User registers → welcome email + role assignment	Possible via webhook, adds latency and failure points.	Native. User Registered trigger fires instantly inside WordPress.	Krom Automation
LearnDash course completed → certificate email	Not accessible without a custom webhook.	Native LearnDash trigger, no bridge required.	Krom Automation
Typeform submission → create post + notify editor	Native Typeform trigger. Clean connection.	Requires incoming webhook to receive Typeform data.	Make.com
Post published → AI-generated social captions + scheduled posts	Possible. Requires OpenAI module + social modules.	Native Post Published trigger + AI Generate Text + social Pro actions.	Krom Automation, cheaper at scale
MemberPress subscription expired → downgrade role + send email	Inaccessible. No native MemberPress trigger.	Native MemberPress trigger. See the MemberPress integration documentation.	Krom Automation

Setting Up Make.com with WordPress: What the Tutorials Skip

Most tutorials end at “you’re connected.” Here is what happens after that.

Authentication: The Make Connector plugin generates an API key you paste into Make.com. The alternative is WordPress application passwords, introduced in WordPress 5.6, which let Make’s HTTP module authenticate without the connector plugin. Application passwords are more transparent and do not add a plugin to your stack, but constructing the API calls manually takes longer to set up.

Custom fields: The connector exposes standard post fields. Custom fields require using the REST API with a plugin like ACF that exposes meta via REST, then accessing them through Make’s HTTP module. This is documented but rarely mentioned in beginner guides.

Error handling: Make.com scenarios fail silently by default unless you add an error handler route. A scenario that fails 10 percent of the time and you never notice is worse than a scenario that never ran. Build error handler routes from the start, not after something breaks.

WooCommerce data: WooCommerce does not expose order triggers through the standard WordPress REST API in a format the Make Connector understands cleanly. The functional approach is configuring WooCommerce webhooks (Settings → Advanced → Webhooks) to push order data to a Make.com webhook URL. That works, but it is an outbound push from WordPress, not an inbound pull from Make.com.

Krom Automation as the WordPress-Native Alternative

Krom Automation is a visual workflow automation plugin built entirely inside WordPress. Every trigger fires directly from a WordPress event.

Every action runs on your server. No data leaves your database unless you explicitly call an external service.

The free version includes 16 triggers, 21 actions, and 20 workflow templates. That covers the majority of WordPress-internal automation without a paid plan. The full trigger and action model is documented, so you can verify exactly what fires and what runs before committing.

The Pro version adds 80+ additional triggers, 60+ additional actions, and 24 integrations including Mailchimp, FluentCRM, ActiveCampaign, Slack, Discord, Google Sheets, LearnDash, MemberPress, and more. For sites that need both WordPress-internal events and external service connections, Pro closes most of the gap with Make.com for scenarios that start inside WordPress.

Key differences that matter in practice:

• No per-execution cost. A Pro plan at $199 per year covers 5 sites with unlimited workflow executions. A busy WooCommerce store running 10,000 operations per month on Make.com pays that annually just in subscription fees, before accounting for operation overages.
• WordPress internals are native. LearnDash, MemberPress, WooCommerce Subscriptions, and Easy Digital Downloads are reachable as triggers without webhooks or bridges. See the LearnDash integration and WooCommerce Subscriptions integration for specifics.
• Execution logs live in WordPress. Every step of every workflow run is logged in your own database. When something fails, you see exactly which step failed and what the data looked like at that point.
• AI actions are included free. GPT-4o, Gemini 2.5, and Groq Llama models are available as actions without a separate subscription. You bring your own API key and pay your provider at standard rates. wpRigel does not mark up tokens.

Self-hosted automation means your execution history, your API credentials, and your workflow logic stay in your own database. That is not a minor convenience. It is a compliance and ownership difference.

For teams evaluating costs honestly, the full pricing comparison across WordPress automation tools is worth reading before committing to an annual platform subscription.

The Connector Plugin: Known Issues Worth Knowing

The Make Connector plugin carries a set of documented issues that do not appear in the official marketing materials. These are worth knowing before you build a production workflow on top of it.

• Memory errors on activation: Reported on shared hosting plans with limited PHP memory. Raising the memory limit to 256MB resolves most cases, but not all.
• Conflicts with security plugins: Wordfence and similar plugins occasionally block the connector’s API endpoint. Whitelisting the IP range or disabling certain firewall rules is the documented fix.
• Plugin conflicts with caching layers: Full-page caching plugins that intercept REST requests can break the authentication flow. Object caching is usually fine; full-page caching requires exceptions for the Make endpoint.
• No error visibility inside WordPress: Connector failures do not write to the WordPress error log. Debugging requires Make.com’s scenario history.

None of these are dealbreakers on a well-configured server with a lean plugin stack. On a shared host running 35 plugins, they are more likely to surface.

When to Use Each Tool

The decision is not Make.com versus WordPress plugins in the abstract. It is about where your automation starts and ends.

Use Make.com when:

• The trigger is an external service (Typeform, Stripe, Airtable, Pipedrive) and WordPress is one destination among several
• Your team already manages Make.com scenarios for other business processes and WordPress is being added to an existing workflow
• You need to route data between multiple external systems and WordPress is a minor stop

Use Krom Automation when:

• The trigger is a WordPress event: a registration, an order, a course completion, a subscription change, a form submission
• You want execution logs, analytics, and workflow history inside WordPress without switching tools
• Per-execution billing would make costs unpredictable at your traffic volume
• Plugin-specific events (LearnDash, MemberPress, WooCommerce Subscriptions) are part of the automation
• Data residency or compliance requirements mean workflow data should not leave your server

Use both when your site genuinely sits at the intersection of internal WordPress events and complex external system routing. A user completes a course in LearnDash, Krom Automation fires the internal completion trigger and updates their WordPress role, then sends a webhook to Make.com, which updates your CRM, assigns a deal stage, and notifies the sales team. The two tools can work sequentially without competing.

Practical Cost Comparison at Different Site Scales

Scenario	Make.com annual cost	Krom Automation annual cost	Notes
1 site, 5 simple workflows, low volume	$0 (free tier, if under 1,000 ops/month)	$0 (free plugin, permanent)	Make.com free tier is real but operation-capped
1 site, 10 workflows, medium volume (~5,000 ops/month)	~$127/year (Core plan)	$119/year (Basic Pro, 1 site)	Similar cost; Krom has no exec cap
5 sites, agency, multiple workflows each	$127 to $226/year per account, or more	$199/year (Standard Pro, 5 sites)	Krom is one price for all 5 sites
High volume store, 500 orders/month, 6-module scenario	3,000 ops/month. Core plan covers it, until volume grows.	$119/year, no exec cost regardless of volume	Make.com cost scales with volume; Krom does not

Our Verdict

Make.com is a strong platform for what it was designed to do: routing data between external services in visual, multi-step scenarios. If your WordPress site is a destination inside a larger multi-app workflow, it is a reasonable choice and we would not talk you out of it.

If WordPress is the center of your automation, not a stop along the way, building on Make.com means accepting external data processing, operation billing that scales with volume, limited access to WordPress-internal events, and debugging that requires two separate interfaces. Those are real costs, not hypothetical ones.

For WordPress-first automation, Krom Automation fits the job better. The free version covers the most common internal event scenarios at no cost, permanently.

The Pro version adds the external integrations that close the gap with Make.com for workflows that start inside WordPress. You can download the free plugin from the WordPress.org plugin directory and build your first workflow without a credit card.

If you are currently paying for Make.com primarily for WordPress tasks, that is the clearest case for switching. The comparison page walks through the differences in detail: see how Krom Automation compares.

Review Krom Automation pricing and plans to find the right fit for your site count and workflow needs.

Frequently Asked Questions

Can Make.com trigger automations from WooCommerce order events?

Not natively through the Make Connector plugin. The functional approach is configuring WooCommerce’s built-in webhook system to push order data to a Make.com webhook URL when an order event fires. This works but requires setup on both the WordPress and Make.com sides, and adds a failure point if the outbound webhook times out.

Is it possible to use Make.com with WordPress without installing the connector plugin?

Yes. Make’s HTTP module can call the WordPress REST API directly using application password authentication.

You construct the API request manually inside Make.com, including the endpoint, headers, and body. It removes the connector plugin dependency but requires more technical setup for each action.

Does Krom Automation replace Make.com entirely for WordPress sites?

For workflows where the trigger and most actions are WordPress-internal, yes. For workflows where the trigger is an external service (a form tool, a payment platform, or a CRM that is not WordPress-native), Make.com’s broader trigger library still has an advantage. The two tools can also work together, with Krom Automation handling internal events and passing data outward via its HTTP Request action or incoming webhook.

Why does the Make Connector plugin sometimes crash WordPress?

Reported crashes are usually linked to insufficient PHP memory on shared hosting, conflicts with security plugins that block the connector’s REST endpoint, or interference from full-page caching layers. Raising PHP memory to 256MB, whitelisting the connector’s endpoint in your firewall, and excluding the REST API path from full-page caching resolves most cases.

How does Make.com handle WordPress authentication?

The Make Connector plugin generates an API key you enter in Make.com’s connection settings. The alternative is WordPress application passwords: create one in Users → Profile, then use it as the password in Make’s HTTP module with basic authentication. Application passwords do not require the connector plugin and give you granular control since each password can be revoked independently.

The WordPress automation pricing comparison most sites publish tells you the starting price and stops there. That is the wrong number. What you pay in month one is rarely what you pay in month 13, especially if your site grows or you add a second project.

This article models a small WooCommerce store, a busy store and a ten-site agency across every major pricing model: per-task cloud tools, flat annual plugins and lifetime licences. Every figure is real and sourced. The goal is a cost table you can use to make a decision, not a list of features you could find on any product page.

There are three pricing models in play for WordPress automation in 2026. Per-task cloud tools like Zapier and Make charge based on how many workflow runs you consume each month. Flat annual plugins like Uncanny Automator charge per year per site regardless of volume.

Lifetime licence plugins charge once and run forever on your server. Each model has a different breakeven point, and the right answer depends almost entirely on your task volume and how many sites you manage.

The scenarios below use consistent assumptions so the numbers are comparable. A small store runs 2,000 automated tasks per month: order confirmations, welcome emails, tag updates in Mailchimp, a few Slack notifications.

A busy store runs 15,000 tasks per month: the same categories but at higher order volume, with conditional branching, delayed follow-ups and LearnDash course enrollments triggered by purchases. A ten-site agency manages client sites at mixed volumes averaging 3,000 tasks per site per month, so roughly 30,000 tasks total but spread across separate WordPress installs.

Browse the full Krom Automation feature list

How Each Pricing Model Works

Understanding the mechanics matters because the costs compound in different ways. Per-task tools count every action step in a workflow, not just every workflow run.

A three-step workflow that fires 1,000 times consumes 3,000 tasks, not 1,000. That multiplier catches a lot of buyers off guard in the first billing cycle.

Flat annual plugins charge a fixed fee per year, usually tiered by number of sites. Volume is unlimited. Running a workflow 10,000 times costs the same as running it 100 times.

The catch is that the base plugin often covers only native WordPress triggers and actions. Connecting to Mailchimp, FluentCRM, LearnDash or Slack requires purchasing integration add-ons separately, and those add-ons carry their own annual renewal fees.

Lifetime licence plugins work the same way as flat annual plugins except you pay once. The real question is whether the plugin will still be actively developed in three to five years.

A lifetime licence on an abandoned plugin is worth nothing. On a maintained one, it is the lowest total cost of ownership of any model.

A three-step workflow firing 1,000 times consumes 3,000 tasks on per-task billing. Most buyers discover this at their first renewal, not at signup.

The Pricing Models Side by Side

Model	How you’re billed	Volume risk	Multi-site cost	Add-on risk
Per-task cloud (Zapier, Make)	Monthly, per task/operation consumed	High. Overages billed at 1.25x base rate or upgrade forced	One account covers all sites; task pool shared	Low. Integrations included
Flat annual plugin (Uncanny Automator, AutomatorWP)	Annual per site, fixed	None. Unlimited runs	Linear. Each site needs its own licence or a higher tier	High. Premium integrations sold separately
Lifetime licence plugin (Krom Automation Pro)	Once, per site allotment	None. Unlimited runs	Tiered. 1, 5 or unlimited sites	Low. All integrations included at every tier

Scenario 1: The Small WooCommerce Store (2,000 Tasks Per Month)

At 2,000 tasks per month, per-task cloud tools look affordable on the surface. Zapier’s Starter plan at $29.99 per month covers 750 tasks. That is not enough.

The Professional plan at $73.50 per month covers 2,000 tasks. Over 12 months that is $882 per year.

Make’s Core plan at $10.59 per month covers 10,000 operations, so the small store fits comfortably here at $127 per year. Make is genuinely cheap at this volume.

A flat annual plugin like Uncanny Automator’s Personal plan costs $149 per year for one site with unlimited runs. That base covers WordPress-native triggers and actions.

Adding a Mailchimp integration costs an additional $49 per year on some add-on bundles. A realistic small-store setup with two or three integrations lands around $200 to $250 per year.

A lifetime licence eliminates the annual renewal entirely. The small store scenario fits a single-site licence.

After the one-time payment, year two and every subsequent year costs nothing additional. The breakeven against a $200 per year annual plan is reached in roughly 18 to 24 months.

Small Store Cost Over Three Years

Tool / Model	Year 1	Year 2	Year 3	3-Year Total
Zapier Professional	$882	$882	$882	$2,646
Make Core	$127	$127	$127	$381
Uncanny Automator Personal (~2 add-ons)	$230	$230	$230	$690
AutomatorWP Personal + add-ons	$180	$180	$180	$540
Krom Automation Pro Basic (lifetime)	$299	$0	$0	$299
Krom Automation Pro Basic (annual)	$119	$119	$119	$357

At low volume, Make is the cheapest cloud option by a wide margin. For a self-hosted plugin, Krom Automation’s annual plan at $119 per year undercuts every flat annual alternative, and the lifetime licence is the lowest three-year total of any option shown.

Scenario 2: The Busy WooCommerce Store (15,000 Tasks Per Month)

Volume is where per-task pricing gets painful. At 15,000 tasks per month, Zapier’s Professional plan at 2,000 tasks is not remotely sufficient. The Business plan covers 50,000 tasks at $588 per month, or $7,056 per year.

Make’s Team plan handles higher volumes and costs roughly $34 per month for 10,000 operations. At 15,000 operations per month you need the next tier or pay overage, landing around $480 to $600 per year. Make remains the cheapest cloud option even at this volume.

Flat annual plugins do not care about volume. Uncanny Automator’s Growth plan covers up to 5 sites at $299 per year, but for a single busy site the Personal plan at $149 per year is the right tier.

Add the integrations the busy store actually uses: LearnDash for course triggers, Mailchimp for list sync, Slack for internal notifications. Depending on which add-on bundle applies, a realistic total is $250 to $320 per year for a well-integrated busy store.

The self-hosted lifetime licence cost does not change with volume. A busy store running 15,000 tasks per month pays the same $299 once as a site running 200 tasks per month. That is the most important sentence in this article for high-volume operators.

At 15,000 tasks per month, Zapier costs over $7,000 a year. A self-hosted lifetime licence costs $299 once. Volume is the entire story.

Busy Store Cost Over Three Years

Tool / Model	Year 1	Year 2	Year 3	3-Year Total
Zapier Business	$7,056	$7,056	$7,056	$21,168
Make (Team tier, ~15k ops)	$600	$600	$600	$1,800
Uncanny Automator Personal + add-ons	$300	$300	$300	$900
AutomatorWP Personal + add-ons	$220	$220	$220	$660
Krom Automation Pro Basic (lifetime)	$299	$0	$0	$299
Krom Automation Pro Basic (annual)	$119	$119	$119	$357

The gap between cloud and self-hosted widens dramatically at this volume. Even Make, which is genuinely well-priced, costs six times the lifetime licence over three years. The only argument for cloud tools at 15,000 monthly tasks is if you need automation between two external services that have no WordPress involvement at all.

Scenario 3: The Ten-Site Agency (30,000 Tasks Total, 10 Sites)

This is where flat annual plugins’ per-site pricing model becomes the deciding factor. Cloud tools benefit agencies because one account covers all client sites from a shared task pool. Self-hosted plugins require a licence that covers 10 installations.

Zapier’s Business plan covers all 10 sites from one account. At 30,000 tasks total that is still the Business tier at $7,056 per year.

Make’s Team plan handles the same at roughly $600 per year, depending on exact operation counts. These figures apply equally regardless of site count.

Flat annual plugins charge per site. Uncanny Automator’s Agency plan covers up to 30 sites at $599 per year.

AutomatorWP has similar agency tiers. Add integration add-ons for the full set of client-site needs, typically Mailchimp, FluentCRM, Gravity Forms or WPForms, and an agency setup runs $700 to $900 per year for a well-equipped licence.

Krom Automation’s Enterprise plan covers unlimited sites. Annual is $369 per year. Lifetime is $799 once.

Over three years, the annual plan costs $1,107 and the lifetime costs $799. Both include every integration across all 24 Pro integrations, with no per-integration add-on fees.

Ten-Site Agency Cost Over Three Years

Tool / Model	Year 1	Year 2	Year 3	3-Year Total
Zapier Business (30k tasks shared)	$7,056	$7,056	$7,056	$21,168
Make Team (30k ops shared)	$600	$600	$600	$1,800
Uncanny Automator Agency + add-ons	$850	$850	$850	$2,550
AutomatorWP Agency + add-ons	$750	$750	$750	$2,250
Krom Automation Pro Enterprise (annual)	$369	$369	$369	$1,107
Krom Automation Pro Enterprise (lifetime)	$799	$0	$0	$799

The agency scenario is the clearest case for self-hosted. Make is competitive on cloud, but every automation still runs through an external server, which means API credentials, execution logs and client workflow data leave the WordPress environment. For agencies with clients in regulated industries, that is a real concern, not a theoretical one.

The Hidden Costs That Do Not Appear in Any Pricing Page

Every comparison article shows the headline price. Almost none of them model what gets added once you actually set up a real site. Here is what actually accumulates:

• Add-on fatigue on annual plugins: AutomatorWP’s free plugin handles basic WordPress triggers. Connecting it to Mailchimp, WooCommerce Subscriptions, LearnDash and Gravity Forms requires four separate premium add-ons. Each carries its own renewal. A site with four integrations can easily pay 2x the base plugin price in add-ons alone. We have covered this in detail in our AutomatorWP add-on cost breakdown.
• Task overages on cloud tools: Zapier charges 1.25x the per-task base rate for usage above your plan limit. A campaign that fires 3,000 unexpected automations in a week costs money before you can downgrade or pause.
• Developer time for workflow migration: Moving from Zapier to a self-hosted plugin is not import-and-run. Each workflow must be rebuilt manually. At a contractor rate of $75 to $120 per hour, a 20-workflow migration takes 6 to 10 hours, adding $450 to $1,200 in one-off cost to the switch.
• Renewal discount cliffs: Several annual plugins offer a 20 to 30 percent first-year discount. Year two renews at full price. Budget using the renewal price, not the introductory price.
• AI action costs: Some platforms charge a platform fee on top of AI usage. Tools that mark up API calls or gate AI behind a paid tier add an invisible per-call cost that scales with volume.

Developer time for migration is real money. A 20-workflow move from Zapier runs 6 to 10 hours at contractor rates, money that never appears in any pricing comparison.

What the Free Tier Actually Covers

Every tool in this space offers a free tier of some kind. The question is whether it is a real working tool or a demo with a wall in front of it.

• Zapier Free: 100 tasks per month, single-step workflows only. Multi-step flows require a paid plan. Essentially a proof-of-concept tier, not a production option.
• Make Free: 1,000 operations per month. Multi-step scenarios included. Genuinely usable for a low-volume site testing automation before committing.
• Uncanny Automator Free: Unlimited runs on a limited set of WordPress triggers and actions. No premium integrations. Functional for simple internal workflows but limited by integration depth.
• AutomatorWP Free: Similar to Uncanny Automator Free. Core WordPress triggers and actions with no external platform connections.
• Krom Automation Free: 16 triggers, 21 actions, 20 ready-made workflow templates, a visual drag-and-drop canvas, AI actions (bring your own API key), conditional branching, delays, execution logging, and a full analytics dashboard. No run caps, no trial period, no feature gated behind a paywall. You can download Krom Automation free from the WordPress.org plugin directory and run it in production indefinitely.

The practical difference is that Krom Automation’s free tier handles a complete automation stack for a straightforward site. The AI actions in the free version use your own OpenAI, Google Gemini or Groq API key, so wpRigel never charges per call and never marks up tokens. You pay your AI provider directly at standard rates, which is the honest model.

See how Krom Automation compares across the full feature set

Which Plan Covers Which Scenario

Scenario	Best flat annual option	Best lifetime option	Best cloud option	Avoid
Small store, under 3k tasks/month	Krom Basic annual ($119/yr)	Krom Basic lifetime ($299)	Make Core ($127/yr)	Zapier at any volume
Busy store, 10k to 20k tasks/month	Krom Basic annual ($119/yr)	Krom Basic lifetime ($299)	Make Team (~$600/yr)	Zapier Professional or Business
Agency, 10+ sites	Krom Enterprise annual ($369/yr)	Krom Enterprise lifetime ($799)	Make Team (shared pool)	Per-site annual plugins at scale
Automation between two external services, no WordPress	Not applicable	Not applicable	Make or Zapier	Any WordPress plugin

What Krom Automation Pro Adds and What It Costs

For completeness, Krom Automation Pro adds 80+ additional triggers, 60+ additional actions and 24 integrations covering forms, email marketing, CRM, LMS, membership, messaging and more. The Pro features overview lists every integration included.

There are no add-on fees. Every integration ships with the licence.

Pricing is straightforward:

• Basic annual: $119 per year, 1 site
• Standard annual: $199 per year, 5 sites
• Enterprise annual: $369 per year, unlimited sites
• Basic lifetime: $299 once, 1 site
• Standard lifetime: $499 once, 5 sites
• Enterprise lifetime: $799 once, unlimited sites

Every plan includes a 14-day money-back guarantee and every Pro feature. The only variable is site count.

There are no run limits, no task caps and no per-AI-call fees at any tier. The free vs Pro comparison breaks down exactly what changes between the two versions.

For agencies evaluating the switch from Uncanny Automator, our piece on why agencies are switching from Uncanny Automator covers the migration considerations in detail.

Honest Limitations to Factor In

No pricing comparison is honest without naming what each model does not do well.

• Self-hosted plugins depend on WordPress Cron for delayed actions. On very low-traffic sites, WP-Cron fires late unless a real server cron job is configured. This is a setup step, not a dealbreaker, but it matters for time-sensitive delays.
• Cloud tools handle service-to-service automation that has no WordPress involvement. If you need Salesforce to update a Google Sheet with no WordPress in the chain, Krom Automation is not the right tool. Make or Zapier is.
• Migration from cloud to self-hosted is manual work. Plan for it in the budget. It is a one-time cost, but it is real.
• Lifetime licences carry platform risk. A one-time payment is only as good as the company behind it. Evaluate the plugin’s development history and roadmap before committing.

The Verdict: Who Should Act on What

If you run a single WooCommerce store with meaningful automation volume, the flat annual plugin market has become very competitive and the per-task cloud model rarely makes economic sense above 5,000 tasks per month. Make is the exception worth considering for low-volume sites that need service-to-service connections outside WordPress.

For agencies managing 5 or more sites, the per-site pricing of most annual plugins compounds fast. An unlimited-sites lifetime licence at $799 covers the entire client roster with no renewal and no per-integration add-on fees. That is the lowest total cost of ownership in the market for that use case.

The free tier is always the right starting point. Download the free plugin, build a real workflow, and verify it handles your triggers and actions before spending anything. Krom Automation’s free version runs in production without a trial period or run cap, which is the most honest way to evaluate a tool before committing.

See full pricing details and compare all three plans

Frequently Asked Questions

Does per-task billing really add up that fast?

Yes, because most tools count each action step in a workflow, not each workflow run. A four-step workflow firing 2,000 times per month consumes 8,000 tasks. At Zapier’s rates, that pushes you from the Starter tier to the Professional tier immediately.

Are lifetime licence plugins safe to rely on long-term?

That depends entirely on the specific plugin and company. Check how frequently the plugin updates, whether the company has other active products, and whether there is a public roadmap. A plugin with a transparent development history and multiple active products carries less platform risk than a one-off tool with no visible roadmap.

Can I use a free plugin in production, or is free just a demo?

It varies by tool. Some free tiers are deliberately crippled to force upgrades.

Krom Automation’s free version has no run caps, no trial period and no features hidden behind a paywall. It runs 16 triggers, 21 actions and a full visual workflow builder in production indefinitely.

Do I need to pay separately for integrations like Mailchimp or FluentCRM?

On some platforms, yes. AutomatorWP and some other flat annual plugins sell premium integrations as separate add-ons with their own renewal fees.

On Krom Automation Pro, all 24 integrations are included in every plan at no additional cost. Check the add-on model before comparing headline prices.

What is the breakeven point for a lifetime licence versus annual billing?

At $119 per year for the Basic annual plan and $299 for the Basic lifetime plan, the breakeven is reached partway through year three. From year three onward, the lifetime licence saves $119 per year compared to annual billing. At the Enterprise tier ($369/year annual versus $799 lifetime), breakeven comes in the third year as well.

The best wp fusion alternative depends entirely on what you are actually using WP Fusion to do. If your site passes user data between WordPress and a CRM as its core function, WP Fusion is built precisely for that job. If you need broader automation, such as sending welcome emails, tagging users after course completions, or posting to Slack when an order ships, a general-purpose automation plugin like Krom Automation covers the same territory and costs between $119 and $369 a year, compared to WP Fusion’s $297.

These are not the same kind of tool, and framing one as simply better or worse than the other misses the point. WP Fusion does one thing with exceptional depth.

A general automation plugin does many things, some of which overlap with WP Fusion and some of which go far beyond it. The right question is not which plugin wins, but which one matches the problem you are actually solving.

This guide breaks that decision down by use case, by what each approach costs over time, and by what the alternatives genuinely cannot do, because that is the part most comparison pages leave out.

Browse the full feature list for Krom Automation to see how far the overlap goes before reading further.

What WP Fusion Actually Does

WP Fusion is a CRM sync layer for WordPress. Its core job is to read what happens on your WordPress site, such as a user enrolling in a course or purchasing a membership, and write that event into your CRM as a tag, a field update, or a contact record. It then listens for changes in your CRM and reflects them back in WordPress, for example, by granting or revoking content access based on a tag.

That bidirectional sync is what separates WP Fusion from most alternatives. It does not just push data outward.

It pulls CRM state back into WordPress and uses it to control access. That capability requires deep integration with each CRM, and WP Fusion supports over 65 of them.

What WP Fusion does not do is general WordPress automation. It does not send a transactional email when a post is published. It does not post to Slack when a WooCommerce order ships.

It does not generate AI content, create users on a schedule, or fire HTTP requests to arbitrary endpoints. Those are not gaps or failures. They are simply not what the plugin was built for.

WP Fusion is a precision instrument for CRM sync. Expecting it to handle general workflow automation is like using a scalpel to build a cabinet.

What a General Automation Plugin Covers

A general automation plugin connects WordPress events to responses across a broad range of systems. Krom Automation works on a trigger-and-action model: something happens on your site and the plugin responds automatically, in sequence, with optional conditions and delays.

In the free version alone, Krom Automation includes 16 triggers and 21 actions, covering users, posts, comments, media and WooCommerce. The Pro version adds 80-plus additional triggers, 60-plus additional actions, and 24 integrations with forms plugins, email marketing platforms, CRMs, LMS plugins, membership plugins and messaging tools.

The CRM-relevant integrations include:

• ActiveCampaign: add contacts, apply tags, update fields when WordPress events fire
• FluentCRM: create or tag contacts from user registration, form submission, or purchase
• Mailchimp, ConvertKit, MailerLite, MailPoet: subscribe or unsubscribe based on WordPress events
• WooCommerce: trigger actions on order creation or completion, sync buyer data outward

For a site that needs to push WordPress events into a CRM without pulling CRM state back to control content access, that covers the job. The question is whether your use case requires the bidirectional piece.

The Decision Table: Which Tool Fits Which Situation

Use this table to identify your situation before spending time on a detailed comparison.

Your primary need	WP Fusion	General automation plugin
Tag users in CRM based on WordPress content access	Yes, this is the core feature	Partial: pushes tags outward, does not sync access bidirectionally
Grant or revoke content access based on CRM tags	Yes	No
Sync MemberPress membership status to ActiveCampaign	Yes, with field-level mapping	Yes, via MemberPress triggers and ActiveCampaign actions
Sync LearnDash course completions to a CRM tag	Yes	Yes, via LearnDash integration
Send a welcome email sequence when a user registers	No, delegates to the CRM	Yes, natively
Post to Slack when a WooCommerce order ships	No	Yes
Generate an AI-written product description on post creation	No	Yes, free AI actions included
Connect WordPress to 65-plus named CRMs with deep field mapping	Yes	24 integrations in Pro; not comparable at that breadth
Fire webhooks to external services on WordPress events	Limited	Yes, HTTP Request action plus incoming webhook receiver in Pro

Cost Over Time: Year One and Beyond

Pricing is where the comparison gets genuinely interesting, because the gap is not just the headline number. It is the compounding effect over multiple years on multiple sites.

Scenario	WP Fusion (annual)	Krom Automation (annual)	Krom Automation (lifetime)
1 site, year 1	$297	$119	$299 (once)
1 site, year 3 cumulative	$891	$357	$299
5 sites, year 1	$597 (Plus plan)	$199	$499 (once)
5 sites, year 3 cumulative	$1,791	$597	$499
Unlimited sites, year 1	$897 (Professional)	$369	$799 (once)

WP Fusion’s pricing is taken from its published plans at the time of writing. Krom Automation’s figures are exact: $119 per year for 1 site, $199 for 5 sites, $369 for unlimited, with lifetime options available. All Krom Automation Pro plans come with a 14-day money-back guarantee.

The cost difference is significant enough to matter even if WP Fusion is technically the right fit. If your use case sits in the overlap zone shown in the table above, the $178 annual difference on a single site is worth a serious evaluation of whether you actually need the bidirectional sync.

The cheapest tool is not always the right one. But paying for depth you do not use is a tax on your own site’s operating budget.

Where General Automation Genuinely Falls Short

This is the section that most comparison pages skip, because most of them are written by vendors selling you an alternative. We are also selling you something, so we will be direct: there are use cases where a general automation plugin is the wrong answer, and buying one to replace WP Fusion on those use cases will leave you rebuilding in six months.

Situations where WP Fusion is likely the better choice:

• Your content access model is controlled by CRM tags. You grant access to a course or a protected page based on whether someone has a specific tag in ActiveCampaign or HubSpot. WP Fusion reads that tag and enforces access inside WordPress. A general automation plugin can write tags to a CRM; it cannot read them back to gate content.
• You need field-level sync between WordPress user meta and CRM contact fields. WP Fusion maps individual fields in both directions. A general automation plugin handles discrete events, not continuous field state.
• Your CRM is one of WP Fusion’s 65-plus integrations that sits outside the 24 integrations in Krom Automation Pro. If you are on Zoho, Infusionsoft, Drip, or a niche CRM, check the integration list before switching.
• You are running a complex membership or course business where access rules change frequently based on CRM data. The maintenance overhead of rebuilding that logic in a general automation plugin is real.

Situations where a general automation plugin is the better or equal choice:

• You need to push WordPress events into Mailchimp, ActiveCampaign, ConvertKit, MailerLite or FluentCRM without pulling CRM state back to WordPress. The Mailchimp integration and ActiveCampaign integration handle this directly.
• You want automation that goes beyond CRM sync: notifications, content generation, order processing, user management, and external API calls in the same tool.
• You are managing multiple sites with different automation needs and a single annual plan covering all of them at $369 makes more economic sense than $897.
• You want the automation data to stay in your own database. Krom Automation stores execution logs, workflow data, and API credentials in your WordPress database, not in a third-party cloud.

Can FluentCRM Replace WP Fusion?

This question comes up often, and the honest answer is: FluentCRM replaces WP Fusion for about 60 percent of use cases and creates new work for the other 40 percent. FluentCRM is a self-hosted CRM that lives inside WordPress.

It handles contact management, email sequences, tagging, and basic automation natively. For sites that want their CRM inside WordPress rather than external to it, FluentCRM removes the need for a sync layer entirely, because the CRM is already there.

Where it falls short: if you have an existing external CRM that your sales team or agency manages, FluentCRM does not replace that relationship. It is a separate CRM, not a bridge to the one you already have. Combining FluentCRM with Krom Automation via the FluentCRM integration gives you contact tagging, list management, and event-based automation without the $297 annual cost of WP Fusion, but it only works if FluentCRM can fully replace your external CRM.

Migration: What Actually Transfers and What Does Not

If you are moving away from WP Fusion, understand what you are dismantling before you cancel. No competing page addresses this, so we will.

What migrates with moderate effort:

• Tagging logic: rebuild as trigger-and-action workflows in Krom Automation. A user who purchases a MemberPress membership triggers a tag added to their ActiveCampaign contact. This is a 10-minute workflow build.
• Email notifications: rebuild as Send Email actions triggered by the same events. Krom Automation’s visual email builder handles transactional email design without code.
• Form-to-CRM connections: rebuild via the relevant form plugin integration. Krom Automation supports Gravity Forms, WPForms, FluentForms, Contact Form 7, Elementor Forms and Ninja Forms as triggers.

What does not transfer and requires manual work:

• Bidirectional field sync. There is no equivalent in a general automation plugin. If your site reads CRM fields to personalise content or control access, that logic has no direct replacement.
• Historical CRM data already tagged under WP Fusion’s field mapping. Existing contacts retain their tags; the sync layer that keeps new data flowing is what stops.
• Content protection rules tied to CRM tags. If you have pages or posts protected by WP Fusion’s access control module, those rules are gone when the plugin is removed. You need an alternative access control plugin before deactivating WP Fusion.

A reasonable migration estimate for a mid-size membership or course site: 4 to 8 hours of workflow rebuilding, plus testing. A developer would bill $400 to $800 at typical rates. Factor that into the cost comparison before deciding that $178 in annual savings is the whole picture.

Who Should Use Krom Automation as a WP Fusion Alternative

Krom Automation makes sense as a WP Fusion alternative when the work you are actually doing sits inside the overlap zone: syncing WordPress events to email marketing platforms, tagging new members or course completers in a CRM, sending notifications, and automating post-purchase or post-registration sequences.

It makes additional sense when you want automation that goes beyond CRM sync, such as generating AI content on post creation, sending Slack alerts, posting social updates, or managing Google Sheets data from WordPress. These are things WP Fusion does not address at all.

The 101 Pro workflow templates include pre-built flows for MemberPress, LearnDash, WooCommerce, and form plugins, which means the most common automation patterns are already built and ready to activate. The MemberPress integration covers signup, subscription, expiry and payment triggers. The LearnDash integration covers enrollment, completion, quiz and group triggers.

If your automation list has tasks a CRM-sync specialist cannot touch, you are paying $297 a year for half a solution.

What to Check Before You Decide

Run through these four questions in order. Each one narrows the decision.

1. Do you use CRM tag-based content access control? If yes and that logic is central to your site, stay on WP Fusion or find a dedicated replacement for that specific feature before switching anything else.
2. How many CRM integrations does WP Fusion’s breadth actually serve you? If you use one or two named CRMs that are already in Krom Automation’s 24 Pro integrations, the breadth gap is irrelevant.
3. What percentage of your automations go beyond CRM sync? If the answer is more than half, you are paying WP Fusion’s specialist price for generalist work.
4. What does the migration cost in developer hours? Add that to year one’s cost difference before declaring one option cheaper.

You can download Krom Automation free from the WordPress.org plugin directory and install it alongside WP Fusion on a staging site to test the overlap before committing to any change. The free version’s 16 triggers, 21 actions, and visual workflow builder are enough to validate whether your primary use cases are covered.

For a broader comparison of automation plugin options available in 2026, the roundup of best WordPress automation plugins covers the field in more detail.

Our Verdict

WP Fusion earns its price if bidirectional CRM sync and tag-based content access are genuinely central to how your site works. It is a specialist tool doing a specialist job, and the depth of its CRM support is not matched by any general automation plugin at any price.

If your use cases sit in the overlap zone, or if you need automation well beyond what a CRM sync layer provides, Krom Automation is the more cost-effective and more capable choice. The $119 entry price, free AI actions, visual workflow builder, and 24 Pro integrations cover the majority of what most membership, course and WooCommerce sites actually need from WP Fusion without the $297 annual commitment.

What we would do: install the free version of Krom Automation, map your current WP Fusion workflows against its trigger and action library, and identify which ones have no equivalent. If that list is short, the switch makes economic sense. If the list is long and the missing pieces are the ones your site depends on, WP Fusion stays.

See all Krom Automation plans and pricing, including the lifetime option that makes the long-term cost comparison straightforward.

Frequently Asked Questions

Is there a free alternative to WP Fusion?

Krom Automation’s free version includes 16 triggers and 21 actions and covers basic CRM-adjacent automation like user registration events, WooCommerce order triggers, and HTTP requests to external services. It does not replicate WP Fusion’s bidirectional CRM sync or tag-based content access control. For those specific features, there is no fully free equivalent.

What is the difference between WP Fusion and FuseWP?

They are different products from different companies. WP Fusion is the original plugin focused on deep CRM sync with 65-plus integrations.

FuseWP is a separate, cheaper plugin that positions itself as a simpler alternative with fewer integrations. They share a similar concept but are not related.

Can I use Zapier or Make instead of WP Fusion?

For one-directional event pushing, yes. Zapier and Make can receive WordPress events via webhooks and update a CRM.

They cannot grant or revoke WordPress content access based on CRM tags. They also add per-task billing that compounds quickly at scale, which a self-hosted plugin avoids.

Does WP Fusion have a lifetime deal?

WP Fusion does not publicly offer a lifetime deal. Krom Automation does: $299 for 1 site, $499 for 5 sites, $799 for unlimited sites, all paid once with no renewal.

Can Krom Automation handle MemberPress and LearnDash automation without WP Fusion?

Yes, for outbound automation. Krom Automation’s Pro plan includes MemberPress triggers for signup, subscription, expiry and payment, and LearnDash triggers for enrollment, completion, quiz and group events.

These can push data to ActiveCampaign, FluentCRM, Mailchimp and other platforms. What it cannot do is read CRM tags back to control MemberPress access levels, which is WP Fusion’s distinct capability.

The best free WordPress automation plugin in 2026 is Krom Automation. Its free tier includes a visual drag-and-drop canvas, AI actions at no cost, no execution caps, and a trigger and action set large enough to cover the workflows most WordPress sites actually need. Every other plugin we compared either locks AI behind a paid tier, caps monthly executions, or restricts triggers and actions so tightly that real workflows hit a wall within days.

This article compares free tiers only. We are not interested in what each plugin can do if you pay. We are interested in what you can actually build before you spend anything. That is a different question, and the answers are more honest than most roundups admit.

We cover Krom Automation, Uncanny Automator, AutomatorWP, FlowMattic, and WP Webhooks. Each has a genuine free tier on WordPress.org. We checked trigger counts, action counts, run limits, AI availability, and the failure-handling tools that determine whether a workflow is reliable or just a demo.

Browse the full Krom Automation feature list

What the Free Tier Numbers Actually Look Like

Most automation plugin pages advertise the Pro version. The free tier details live in the small print, the FAQ, or the WordPress.org listing. We pulled the numbers from each plugin’s repository listing and documentation as of mid-2026.

Plugin	Free Triggers	Free Actions	Run Cap (Free)	AI Included Free	Visual Canvas
Krom Automation	16	21	None	Yes	Yes
Uncanny Automator	Limited selection	Limited selection	25,000/month	No	No
AutomatorWP	Core WordPress events only	Core WordPress only	None stated	No	No
FlowMattic	Limited	Limited	Yes, undisclosed	No	Yes
WP Webhooks	3 to 5 webhook triggers	3 to 5 webhook actions	None	No	No

The run cap on Uncanny Automator’s free tier matters more than the trigger count. At 25,000 executions per month, a mid-size membership site with active users can exhaust that budget in under two weeks. Once the cap is hit, automations stop running until the billing cycle resets.

AutomatorWP’s free version covers core WordPress triggers and actions, which is usable for simple tasks. The integration library, the part that connects to WooCommerce, LearnDash, or Mailchimp, is entirely paid. WP Webhooks is genuinely useful for developers routing data between services, but it is not a general-purpose workflow builder for a non-developer.

What Krom Automation’s Free Tier Actually Covers

The free tier includes 16 triggers spanning four event categories. User events cover registration, profile updates, login, logout, role changes, deletion, and password resets. Post events cover publishing, updating, deleting, and status changes.

Comment events cover submission and approval. WooCommerce events cover order creation and order completion. You can see the complete list in the Krom Automation documentation.

The 21 free actions cover the responses most sites need most often:

• Email: Send Email, with merge tags for dynamic personalisation using live event data
• User management: Create User, Update User Meta, Change User Role, Send Password Reset
• Post management: Create Post, Update Post, Update Post Field, Change Post Status, Add Post Meta, Delete Post
• Comment management: Add Comment, Update Comment Status, Add Comment Label, Add Comment Meta
• HTTP Request: GET, POST, PUT, PATCH, and DELETE with JSON response parsing
• AI: AI Generate Text, AI Content Moderation, AI Auto-Tag
• WooCommerce: Create Coupon, Update Order Status

The HTTP Request action alone makes the free tier more capable than it first appears. It lets you push data to any external service that accepts an API call, which covers a significant portion of what Zapier handles for WordPress users at $20 to $50 per month.

A free tier that caps executions is not a free tier. It is a trial with an unpublished expiry date.

The AI Question: Who Gets It Free and Who Charges for It

Every automation plugin we reviewed treats AI as a Pro feature, with one exception: Krom Automation includes three AI actions in the free version. There are no paywalls, no trial limits, and no per-call charges from wpRigel. You bring your own API key from OpenAI, Google Gemini, or Groq, and you pay your provider directly at standard rates.

Supported AI providers in the free version:

• OpenAI: GPT-4o Mini and GPT-4o
• Google Gemini: Gemini 2.0 Flash, Gemini 2.5 Flash Preview, Gemini 2.5 Pro Preview
• Groq: Llama 3.3 70B and Llama 3.1 8B

The practical consequence is that you can build a workflow that auto-tags new posts using AI the day you install the plugin, without touching a paid plan. For content-heavy sites publishing 20 or more posts per month, that saves 30 to 60 minutes of manual tagging time each month, at a cost of roughly $0.01 to $0.05 per post in API fees depending on your chosen model.

The AI actions documentation covers setup, configuration, and common use cases if you want to see exactly how the provider connection works.

The Reliability Problem Nobody Talks About

Every automation plugin comparison focuses on setup and feature counts. None of them spend time on what happens when an automation fails. That omission matters, because automations fail.

API calls time out. WooCommerce hooks fire in unexpected order. A user registers and the welcome email never arrives. If your plugin has no way to surface that failure, you do not know it happened until a user complains.

Here is what each free tier gives you when something goes wrong:

• Krom Automation: Full per-step execution logging, failure notifications by email, automatic retry with configurable backoff, and a workflow simulator for dry-run testing with zero side effects
• Uncanny Automator: Basic execution log available, no automated failure alerts in free tier
• AutomatorWP: Minimal logging in the free version, log detail is a paid feature
• FlowMattic: Execution history available but failure alerting is limited in free tier
• WP Webhooks: Raw request logs, no structured failure alerts

A workflow failing 20 percent of the time looks identical to a working one until you check the logs. Most free tiers do not give you logs worth checking.

The workflow simulator documentation deserves a specific mention. It lets you run a full workflow dry, tracing every step without triggering real actions. You can verify that a welcome email would go to the right address, or that a post status change would fire in the right sequence, before any live data is touched. That is not a feature we found in any competing free tier.

How Run Caps Change the Real Cost Calculation

A plugin with a run cap is effectively a freemium product with a hidden trial clock. Once your site crosses the threshold, you either upgrade or your automations silently stop. The table below shows what that upgrade costs in year one versus ongoing for the plugins with meaningful run caps or feature gates.

Scenario	Krom Automation	Uncanny Automator	AutomatorWP (with add-ons)
1 site, basic WooCommerce + email automations	Free forever	Free up to 25,000 runs/month, then $149/year	Free core, $69 to $149/year per add-on needed
1 site, needs AI actions	Free forever (bring your own API key)	Paid tier required	Paid tier required
1 site, Pro upgrade year 1	$119/year (Basic)	$149/year	$149 to $299/year depending on add-ons
5 sites, Pro upgrade year 1	$199/year (Standard)	$299/year	Add-on costs multiply per site or require agency plan

AutomatorWP’s pricing structure is the most important thing to understand before you start building. The free core is genuinely free, but each integration is a separate paid add-on. If you need WooCommerce, Mailchimp, and LearnDash connected, you are purchasing three separate add-ons. That cost adds up faster than the headline price suggests.

What You Can Build on Each Free Tier: Real Workflow Examples

Abstract trigger and action counts only mean something when you map them to real tasks. These are workflows a non-developer can build on each free tier, ordered by how many sites would genuinely use them:

Krom Automation free tier workflows:

1. Send a personalised welcome email when a user registers, using merge tags to pull in the user’s first name and site name
2. Automatically change a user’s role from Subscriber to Customer when an order completes in WooCommerce
3. Create a draft post and auto-tag it using AI when a form submission arrives via HTTP Request
4. Send an email alert to the admin when a comment is submitted on any post
5. Push new order data to a Google Sheet or CRM via HTTP Request without a paid Zapier account

Uncanny Automator free tier workflows:

1. Basic trigger-action pairs using the limited free integration set
2. Simple WooCommerce to email sequences up to the 25,000 monthly run limit

AutomatorWP free tier workflows:

1. WordPress user role changes triggered by core WordPress events
2. Basic post creation triggered by user actions, using core WordPress only

The gap is visible in the list length. If you are a WooCommerce store sending 500 orders a month and you want to auto-tag customers, change roles, and send a follow-up email, Krom Automation handles all three steps in a single free workflow. Uncanny Automator handles it free up to 25,000 total monthly executions. AutomatorWP requires paid add-ons for WooCommerce integration.

The Visual Builder Question

Most free-tier automation plugins use a list-based rule editor: pick a trigger from a dropdown, pick an action from another dropdown, save. That works for single-step automations. It breaks down the moment you need conditional branching, a delay step, or a second action depending on a first action’s result.

Krom Automation’s free version includes the full visual drag-and-drop canvas, built on ReactFlow with auto layout. You can add Yes and No branches, insert delay steps set to minutes, hours, days, or weeks, and connect multiple actions in sequence. The visual workflow builder documentation shows exactly how the canvas works.

FlowMattic also offers a visual canvas in its free tier, which is worth noting. The execution cap and limited free action set are the constraints there, not the interface. If you need a visual canvas but cannot use Krom Automation for some reason, FlowMattic is the alternative worth testing.

A list-based rule editor is fine for one trigger and one action. The moment you need a branch or a delay, it becomes a different problem that requires a different tool.

Does Running a Free Automation Plugin Slow Down Your Site?

This is one of the most common questions we see, and it has a specific technical answer. Automation plugins that execute workflows during page loads will slow your site down. Plugins that execute workflows in the background do not.

Krom Automation runs all workflow execution via Action Scheduler, a background processing library also used by WooCommerce. Nothing executes during a page load. The impact on frontend performance is effectively zero. The Krom Automation documentation explains the execution architecture in detail.

The caveat that applies to all WordPress automation plugins is WP-Cron timing. WordPress’s built-in cron fires when a visitor hits the site. On very low-traffic sites where hours pass between visits, a scheduled delay of “30 minutes” might actually fire after 2 hours.

This is a WordPress platform constraint, not specific to any plugin. Configuring a real server cron job resolves it completely, and takes about 5 minutes on most hosts.

What the Free Templates Tell You About Each Plugin

Ready-made workflow templates are an underrated indicator of how seriously a plugin takes its free tier. Templates show you which use cases the developer thought were important enough to pre-build, and they lower the time-to-value for new users from hours to minutes.

Krom Automation includes 20 pre-built workflow templates in the free version, across six categories plus a blank canvas starter. These cover user onboarding, WooCommerce order handling, content workflows, and more. You can import a template, review it on the visual canvas, and have it running in under 10 minutes. Templates are exportable and importable as JSON, so sharing a workflow between sites or team members requires no special tooling.

Most competing free tiers include either no templates or fewer than 5. That gap translates directly into setup time. A developer building a welcome email sequence from scratch in a list-based editor takes 20 to 40 minutes the first time. The same workflow from a Krom template takes under 5.

What the Free Tier Does Not Cover in Any Plugin

Being honest about limitations is more useful than pretending a free tier handles everything. Here is what you will not get from any free tier across this comparison, and what upgrading actually unlocks in Krom Automation specifically:

• Third-party integrations: Connections to Mailchimp, FluentCRM, LearnDash, MemberPress, Gravity Forms, WPForms, Slack, and Google Sheets require Krom Automation Pro. The free tier’s HTTP Request action can reach some of these manually, but native integrations with two-way data flow are a Pro feature.
• Incoming webhooks: Receiving data from an external service and triggering a workflow requires the Pro webhook receiver, which includes HMAC-SHA256 signature verification and 9 security layers.
• Schedule trigger: Running a workflow on a recurring schedule (hourly, daily, weekly) requires Pro. The free tier runs workflows in response to events, not on a clock.
• AI workflow generation: Describing an automation in plain English and getting a working workflow generated automatically is a Pro feature.
• Visual email builder: The block-based email designer powered by the Gutenberg editor is Pro only. Free users send emails using a standard text and merge-tag composer.

If your current need is a WooCommerce welcome email, auto-tagging posts with AI, or routing form data via HTTP to an external CRM, the free tier handles that completely. If you need Mailchimp lists updated automatically when a LearnDash course completes, that is a Pro workflow. The free vs Pro feature comparison lists every boundary in detail.

A Note on Self-Hosting vs. External Automation Platforms

Zapier and Make handle automation between two external services. They are not WordPress-native tools. When your trigger is a WordPress event (a user registers, an order completes, a post publishes), routing that event through an external platform adds latency, introduces a dependency on a third-party service staying online, and sends your data outside your server. A Zapier plan that covers a WordPress store’s automation volume typically costs between $50 and $100 per month.

Krom Automation keeps all of that inside your WordPress install. Execution logs, workflow data, API credentials, and event history stay in your own database across 9 custom tables. There is no per-execution billing because nothing leaves your server unless you explicitly configure an HTTP Request or a Pro integration to do so.

Our Verdict: Who Should Use Which Free Tier

If you run a WordPress site and want to automate user management, WooCommerce order responses, post workflows, or AI-assisted content tasks without paying anything, install Krom Automation. Its free tier covers more real workflows than any other option we tested, there is no execution cap to plan around, and the AI actions are genuinely included rather than used as an upgrade prompt.

If you are a developer connecting two external services where WordPress is barely involved, WP Webhooks is the more focused tool. If you are already inside the Uncanny Automator ecosystem with existing paid integrations, the switching cost probably outweighs the free-tier comparison.

Who should not start with Krom Automation free: sites that immediately need native Mailchimp list syncing, LearnDash course completion triggers, or recurring schedule-based workflows. Those require Pro. Our honest assessment is that if you need more than 3 of those Pro integrations from day one, start on a paid plan rather than building free workflows you will need to restructure later.

The free plugin is available in the WordPress.org plugin directory. Install it, run the first workflow, and you will know within 20 minutes whether the free tier covers your current needs.

Compare all three Krom Automation plans

Download Krom Automation free from the WordPress.org plugin directory and start your first workflow today with no account creation, no trial clock, and no feature locked away.

Frequently Asked Questions

Is Krom Automation’s free version really free forever, or does it expire?

The free version is free forever. There is no trial period, no execution cap, and no feature that unlocks for a few days and then locks again. The triggers, actions, and AI actions in the free tier are permanently available at no cost.

Can I connect WooCommerce to my email marketing tool for free using these plugins?

Partially. Krom Automation free includes WooCommerce triggers (Order Created, Order Completed) and an HTTP Request action that can push data to any email platform with an API. Native integrations with Mailchimp, MailerLite, or ConvertKit require Krom Automation Pro.

Do free WordPress automation plugins work with Contact Form 7 and WPForms?

Form plugin integrations are typically Pro features. Krom Automation Pro includes native integrations for Contact Form 7, WPForms, Gravity Forms, Fluent Forms, Elementor Forms, and Ninja Forms. On the free tier, you can route form submission data manually via the HTTP Request action if your form plugin supports webhook output.

What happens when a free automation plugin hits its run cap?

Automations stop executing until the billing cycle resets. The plugin does not queue the missed runs for later. Events that fired while the cap was reached are lost unless you have a separate logging mechanism. Krom Automation has no run cap on any tier, free or paid.

Are free automation plugins safe to run on a production site?

Yes, provided the plugin uses background execution rather than running during page loads. Krom Automation uses Action Scheduler for all workflow execution, so your site’s frontend performance is not affected. Test any new workflow using the dry-run simulator before enabling it on live data.

If you are looking for a FunnelKit alternative, the first question is not “which tool is cheaper?” It is “what are you actually automating?” FunnelKit is genuinely excellent at WooCommerce checkout funnels, order bumps, one-click upsells, and cart abandonment recovery. If that is your entire need, you should probably stay with FunnelKit. The situation where a switch makes sense is when your automation needs grow beyond the cart and into the rest of your site, because that is where FunnelKit stops and a tool like Krom Automation begins.

This article is not a takedown of FunnelKit. It is a map of where each tool’s strengths end. Understanding that boundary is what lets you make the right call for your site in 2026, rather than paying for two overlapping tools or stretching one into a job it was not designed for.

We will cover what FunnelKit does well, where it runs out of scope, who genuinely needs a broader alternative, and what to look for when the cart is only part of the picture.

Browse the full Krom Automation feature list if you want to see what site-wide WordPress automation looks like in practice.

What FunnelKit Actually Does Well

FunnelKit (formerly WooFunnels) was built specifically for one problem: converting WooCommerce shoppers more efficiently. It does that job with real depth.

The core feature set covers checkout page customization, multi-step funnels, order bumps at checkout, one-click post-purchase upsells, and cart abandonment email sequences. Those are not bolt-on features. They are what the plugin was designed around from day one.

The FunnelKit Automations layer adds a CRM, contact timelines, broadcast emails, and visual email sequences. For a store owner whose entire marketing operation runs through WooCommerce, that is a coherent, well-integrated stack. You do not need a separate CRM or email marketing tool if FunnelKit covers it.

FunnelKit is not overpriced for what it does. It is priced correctly for a WooCommerce-first marketing platform. The problem arises when you are paying for a marketing platform and only needed a checkout optimizer.

The honest case for staying with FunnelKit looks like this:

• Your site runs WooCommerce and the store is the primary business model
• Cart abandonment recovery and post-purchase sequences drive meaningful revenue
• You want a CRM that is native to WooCommerce customer data
• You build landing pages and checkout flows regularly
• Your team thinks in terms of funnels and conversion rates, not workflow automation

If that list describes your situation, this article’s conclusion is simple: FunnelKit is a strong fit and switching would cost you more than it saves.

Where FunnelKit Runs Out of Scope

FunnelKit’s scope is the purchase journey. Everything it does connects to a contact record, a WooCommerce order, or an email sequence aimed at converting or retaining a buyer. That is not a criticism. It is the design intent.

The scope limit becomes a problem when your site generates important events outside the purchase journey. Consider what FunnelKit does not handle natively:

• A new WordPress user registers but has not purchased anything yet
• A post is published and needs to notify a Slack channel or create a row in Google Sheets
• A Gravity Forms or WPForms submission triggers a follow-up action on the contact record
• A LearnDash course completion should unlock a discount or update a user role
• A MemberPress subscription expires and needs to trigger a re-engagement sequence and change the user’s access level
• A media upload or comment event needs to route somewhere or log something

FunnelKit does not fire on these events because they are not purchase events. You can work around some of them with third-party integrations, but you are extending a funnel tool into territory it was not built for. That is where general-purpose WordPress automation earns its place.

The Real Distinction: Funnel Automation vs Workflow Automation

These are two genuinely different categories, and the naming confusion is where most buyers go wrong.

Capability	FunnelKit	Krom Automation (Free)	Krom Automation Pro
WooCommerce checkout optimization	Yes, core feature	No	No
Order bumps and one-click upsells	Yes	No	No
Cart abandonment sequences	Yes, native	Via WooCommerce trigger + delay	Via WooCommerce trigger + delay
WooCommerce order triggers	Yes	Yes (Order Created, Order Completed)	Yes, 80+ additional triggers
WordPress user lifecycle events	Limited	Yes, 7 user triggers	Yes, extended
Post, comment, media triggers	No	Yes	Yes
Form integrations (Gravity Forms, WPForms)	Via FunnelKit forms only	No (Pro feature)	Yes, 24 integrations
LMS integrations (LearnDash, TutorLMS)	No	No (Pro feature)	Yes
Visual drag-and-drop workflow canvas	Linear sequence editor	Yes, full canvas	Yes, full canvas
AI actions included	No	Yes, 3 AI actions	Yes, extended
Execution logs per workflow step	Limited	Yes, full audit trail	Yes
Self-hosted, data stays on your server	Yes	Yes	Yes

The column that matters is the one matching your actual use case, not the one with the most checkmarks. A site that only needs checkout optimization has no use for 16 triggers covering users, posts, and comments. A site running a membership program alongside a store needs both columns.

What a FunnelKit Alternative Actually Needs to Cover

When someone searches for a FunnelKit alternative, they are usually in one of three situations. Knowing which one applies changes what you should look for.

Situation 1: You Want Cheaper WooCommerce Funnel Features

CartFlows is the most frequently cited alternative here, and it earns that position for straightforward checkout funnel needs. SellKit competes on price and covers the core order bump and upsell use cases. If checkout conversion is the only problem, either of those tools is a legitimate choice and this article is not the right guide for you. Search for a direct CartFlows or SellKit comparison instead.

Situation 2: You Need Automation Beyond the Cart

This is where Krom Automation becomes the relevant answer. You are not replacing FunnelKit’s funnel features. You are adding automation that covers the parts of your site FunnelKit does not reach. In some cases, you run both: FunnelKit handles the checkout experience and Krom Automation handles everything else.

Situation 3: You Are Paying for FunnelKit Automations but Using 20 Percent of It

FunnelKit Automations is a substantial product. If your actual need is “send a welcome email when a user registers” and “notify me when an order fails,” paying for a full marketing automation platform with a CRM is a significant overspend. The free version of Krom Automation covers both of those workflows with zero cost.

The free version of Krom Automation covers the automation needs of most WordPress sites that are not primarily running commerce funnels. Paying for a funnel platform to get a welcome email trigger is a budget problem, not a features problem.

Krom Automation: What It Covers and What It Does Not

Krom Automation is a visual workflow automation plugin for WordPress. The mental model is “if this happens on your site, do this automatically,” built on a drag-and-drop canvas rather than a linear list. It is not a funnel builder, a checkout optimizer, or a CRM. Those distinctions matter.

The free version ships with 16 built-in triggers and 21 built-in actions. That is enough to automate the majority of site-wide events without touching a paid plan. The free tier includes:

• 7 user triggers: registration, login, logout, profile update, role change, deletion, password reset
• 4 post triggers: published, updated, deleted, status changed
• 2 WooCommerce triggers: Order Created and Order Completed
• 2 comment triggers and 1 media upload trigger
• 21 actions covering email, user management, post operations, HTTP requests, and 3 AI actions

The AI actions (AI Generate Text, AI Content Moderation, AI Auto-Tag) are included in the free version with no paywall. You bring your own API key for OpenAI, Google Gemini, or Groq, and pay your AI provider directly at their standard rates. Krom Automation never charges per AI call and never marks up tokens.

For execution reliability, every workflow runs via Action Scheduler in the background, so nothing executes during a page load. Every step has a full audit trail in the execution logs. The analytics dashboard shows total executions, active workflows, estimated time saved, and failed execution count, which matters because a workflow failing 20 percent of the time looks identical to a working one until you check the logs.

You can test any workflow with the built-in workflow simulator before it goes live. Dry runs produce no side effects, which removes the risk of accidentally emailing your entire user list during a setup test.

See how Krom Automation works on the product page.

Where Krom Automation Pro Changes the Equation

The Pro version adds 80+ additional triggers, 60+ additional actions, and 24 integrations. That is where the comparison to a broader FunnelKit Automations subscription becomes concrete.

Pro integrations include form plugins (Gravity Forms, WPForms, Fluent Forms, Contact Form 7), email marketing platforms (Mailchimp, FluentCRM, ActiveCampaign, ConvertKit, MailerLite), LMS platforms (LearnDash, TutorLMS), membership plugins (MemberPress), and messaging tools (Slack, Discord, Twilio, Telegram). There are also Google Sheets, Google Calendar, and social media posting integrations.

Two Pro features deserve specific mention for anyone coming from FunnelKit:

The incoming webhook receiver gives each workflow a unique secret URL with HMAC-SHA256 signature verification and 9 security layers. That means any external service, including a payment processor, a form tool, or a SaaS platform, can trigger a WordPress workflow without a custom plugin. The documentation for setting up the incoming webhook receiver covers the full configuration.

The Schedule trigger lets workflows fire on a recurring schedule: hourly, daily, weekly, monthly, or at a custom interval. That is useful for things like weekly digest emails, recurring data syncs to Google Sheets, or monthly membership renewal reminders. See the schedule trigger documentation for setup details.

Cost Comparison: What You Actually Pay Per Site

This table answers the decision most buyers are actually making: what does each option cost in year one, and what does it cost to maintain?

Option	1 Site, Year 1	1 Site, Year 2+	5 Sites, Year 1	Funnel Features Included
Krom Automation Free	$0	$0	$0	No
Krom Automation Pro Basic (annual)	$119/year	$119/year	N/A (1-site plan)	No
Krom Automation Pro Standard (annual)	$199/year	$199/year	$199/year	No
Krom Automation Pro Basic (lifetime)	$299 once	$0	N/A (1-site plan)	No
Krom Automation Pro Standard (lifetime)	$499 once	$0	$499 once	No
FunnelKit (funnel + automations)	Varies by plan	Annual renewal required	Varies by plan	Yes

The lifetime plans shift the math significantly for agencies and developers managing multiple sites. The Standard lifetime plan at $499 covers 5 sites with no renewal cost. If you are managing 5 client sites and paying $199 per year on an annual plan, the lifetime plan pays for itself in 2.5 years. A developer managing 10 or more sites should look at the Enterprise lifetime plan at $799 for unlimited activations.

All Pro plans include a 14-day money-back guarantee. Compare all three plans before deciding.

Who Should Run Both Tools Together

This is the option most articles in this space ignore. FunnelKit and Krom Automation are not mutually exclusive. A WooCommerce store with serious funnel revenue and a growing community or membership program is a legitimate case for running both.

FunnelKit owns the checkout experience: the page templates, order bumps, upsells, and post-purchase email sequences tied to purchase behavior. Krom Automation owns everything else: user registration flows, role changes when a membership activates or expires, content publishing notifications, form submission routing, and cross-platform data sync.

Running two specialized tools that each do one thing well is almost always cleaner than running one bloated tool that half-covers two jobs.

The combined annual cost of both tools at their entry tiers is still less than many all-in-one marketing platforms. The tradeoff is two plugins to maintain, which is a real consideration for smaller teams. If you have a developer or the technical confidence to manage the integration, the combination is worth it. If you need a single dashboard for everything, that is a different conversation.

Hidden Costs and Limitations Worth Knowing

No comparison article is complete without naming what the marketing pages leave out.

For FunnelKit, the practical limitations are:

• The full value requires FunnelKit Automations, which is a separate product from the funnel builder. Buyers sometimes purchase one expecting both.
• The CRM contact model is purchase-centric. Non-purchasing users (subscribers, forum members, course students) are second-class citizens in the data model.
• Heavy customization of checkout templates can create page builder dependency that is difficult to migrate away from later.

For Krom Automation, the honest constraints are:

• Delay scheduling relies on WordPress Cron. On very low traffic sites where nothing visits for hours, WP-Cron fires late unless a real server cron job is configured. The delays and scheduling documentation covers this and the recommended server cron setup.
• AI actions require supplying your own API key. There is no built-in AI if you do not have an OpenAI, Gemini, or Groq account.
• Krom Automation does not replace a checkout optimizer. If your revenue depends on order bumps and one-click upsells, you still need FunnelKit or CartFlows for those features.

For a broader look at how to evaluate WordPress automation tools against each other, the guide to choosing a WordPress automation plugin covers the full decision framework.

Practical Signals: Which Tool Fits Your Situation

Work through this list in order. The first row that matches your situation is your answer.

Your situation	Recommended direction
WooCommerce store, revenue depends on funnel conversion and cart recovery	Keep or start with FunnelKit
Need checkout optimization AND site-wide automation across users, LMS, or forms	FunnelKit for funnels, Krom Automation for the rest
Paying for FunnelKit Automations but only using welcome emails and order notifications	Krom Automation free tier covers both; reconsider your FunnelKit plan
Membership or LMS site with no serious funnel revenue	Krom Automation Pro with MemberPress or LearnDash integration
Content or community site with no WooCommerce	Krom Automation free tier, likely sufficient
Agency managing 5+ client sites with mixed needs	Krom Automation Standard or Enterprise lifetime plan
Need automation between two external SaaS tools with no WordPress involvement	Neither tool. Use Zapier or Make for external service connections.

The Verdict

FunnelKit is not a tool people should switch away from lightly if they are running serious WooCommerce funnels. The checkout optimization features, order bumps, and native cart abandonment sequences are genuinely good and the CRM is well integrated with purchase data. If that is your world, the search for a FunnelKit alternative is probably the wrong search.

The right search is for a FunnelKit alternative when your automation needs have grown beyond the cart. User lifecycle events, form submissions, LMS completions, membership expirations, content publishing, and cross-platform data sync all require a different kind of tool. Krom Automation was built for exactly that scope, and the free version covers enough ground that most non-funnel WordPress sites never need to pay for it.

If you are paying for FunnelKit Automations and using less than half of it, start there. Download Krom Automation free from the WordPress plugin directory, build your first workflow, and see whether it covers what you actually need before renewing anything. The free version has no run caps, no trial period, and no features locked away. That is the lowest friction way to find out whether the scope fits.

See Krom Automation Pro pricing and plans when you are ready to expand beyond the free tier.

Frequently Asked Questions

Is CartFlows a better FunnelKit alternative than Krom Automation?

For checkout funnels and order bumps, CartFlows is a direct FunnelKit competitor and a legitimate alternative. Krom Automation is not a checkout funnel tool. If your need is funnel-specific, compare CartFlows and FunnelKit directly. If your need is site-wide automation beyond the cart, Krom Automation is the relevant comparison.

Can Krom Automation handle WooCommerce order automation?

Yes. The free version includes Order Created and Order Completed triggers. The Pro version adds 80+ additional triggers, covering a wider range of WooCommerce events.

What Krom Automation does not do is optimize the checkout page itself or add order bumps. Those remain FunnelKit’s territory.

Does Krom Automation have a free version with no time limit?

Yes. The free version is free forever with no trial period, no execution caps, and no features locked behind a paywall. It includes 16 triggers, 21 actions, 20 workflow templates, a visual canvas, AI actions, execution logs, and analytics. There is no expiry date and no pressure to upgrade.

What happens to my FunnelKit workflows if I switch?

FunnelKit workflows do not migrate automatically to Krom Automation. Any sequences, automations, or email templates built in FunnelKit would need to be rebuilt. Checkout pages built with FunnelKit’s page templates are also not transferable. Plan for 2 to 5 hours of rebuild time depending on the number and complexity of existing automations.

Is there a FunnelKit alternative that works without WooCommerce?

Krom Automation works without WooCommerce. The WooCommerce triggers and actions become available automatically if WooCommerce is installed, but the plugin functions fully on any WordPress site without it. For non-commerce sites, all 16 free triggers and 21 free actions remain available.

Can I run FunnelKit and Krom Automation on the same site?

Yes, and for stores with serious funnel revenue and broad automation needs, running both is a practical option. FunnelKit handles the checkout experience and post-purchase sequences tied to purchase behavior. Krom Automation handles user lifecycle events, form integrations, LMS completions, and anything else outside the cart. There is no known conflict between the two plugins.

Knowing how to choose a WordPress automation plugin is less about comparing feature tables and more about asking the questions that marketing pages never answer. The wrong plugin does not announce itself on install day.

It reveals itself six months later when you hit a run limit you did not know existed, or when you discover your API credentials are stored on someone else’s server, or when you try to cancel and find that every workflow you built stops working.

This guide is a decision framework, not a product pitch. Work through the seven questions below before you touch a plugin page. Each question is followed by what a good answer looks like and what a bad answer costs you.

If you want to see how one plugin answers all seven, browse the full Krom Automation feature list and check for yourself.

The Seven Questions That Separate a Good Pick From an Expensive Mistake

Question 1: Does It Have Run Limits, and What Do They Actually Cost?

This is the question most buyers skip, and it is the one that causes the most regret. Some plugins charge per task, per trigger fire, or per “automation credit.” Those costs are invisible at low volume and painful at scale.

A site with 500 new user registrations per month, each triggering a 3-step welcome sequence, generates 1,500 task executions monthly from a single workflow. Cloud-based tools that charge per task can turn that into a $30 to $80 monthly line item before you have automated anything else.

• Good answer: Flat fee per year or lifetime. No per-execution billing. No monthly task caps.
• Acceptable answer: A tiered plan where the limit is published clearly and you can see exactly when you would hit it.
• Bad answer: Vague language about “unlimited automations” that turns out to mean unlimited workflow rules, not unlimited executions.
• Worst answer: No pricing page. A “contact us for volume pricing” response to a direct question about limits.

Self-hosted plugins generally win here because execution happens on your own server at no marginal cost. Cloud platforms generally lose here because every execution is a billable event somewhere in their cost model, even if they absorb it at low volume. The comparison between self-hosted and cloud is not just philosophical. At 10,000 executions per month it is often the difference between a $150 annual fee and a $600-plus annual fee for the same work.

A plugin that looks free at 200 executions per month and costs $80 per month at 2,000 executions is not a free plugin. It is a variable-rate subscription in disguise.

Question 2: What Is the Licensing Model When You Need More Sites?

Single-site licensing is fine until it is not. Agencies, freelancers managing client sites, and anyone running more than one WordPress property need to know the per-site cost before they fall in love with a plugin.

The table below shows how three common licensing structures play out across different site counts. Prices are illustrative of the patterns you will encounter, not quotes from any specific product.

Licensing model	1 site	5 sites	20 sites
Single-site only (buy per site)	$X	5X	20X
Tiered (1, 5, unlimited)	$X	1.5X to 2X	2X to 3X
Unlimited sites, flat fee	$X	$X	$X

Krom Automation’s Pro pricing is tiered across three plans. The Basic plan covers 1 site at $119 per year or $299 lifetime. Standard covers 5 site activations at $199 per year or $499 lifetime.

Enterprise covers unlimited sites at $369 per year or $799 lifetime. Every plan includes every Pro feature. The only variable is how many sites you can activate.

The lifetime option changes the maths significantly for stable sites. At $499 lifetime for 5 sites, the break-even against the $199 annual plan is reached in year three. After that, it is pure savings.

Question 3: Can You Test Before It Runs Live?

A workflow that sends 800 duplicate welcome emails to your entire user list because you misconfigured the trigger is not a hypothetical. It has happened to real sites. The question is whether the plugin gives you a safe way to test before execution.

Look for three things specifically:

• A dry-run or simulator mode that traces a workflow step by step without firing any real actions. This lets you verify conditional branching logic, merge tag output, and delay behaviour before anything touches live data.
• A staging-environment-safe flag that prevents workflows from firing on clone sites used for testing.
• Per-workflow pause controls so you can deactivate a specific workflow without disabling the entire plugin while you edit it.

Krom Automation includes a workflow simulator for dry-run testing with zero side effects. You can trace any workflow, inspect what each action would produce, and confirm the logic before enabling it. Most list-based automation plugins do not offer this at any tier.

Question 4: What Does Execution Visibility Look Like?

A workflow that fails silently is worse than no workflow at all. It creates the impression that automation is running while nothing is actually happening. Execution visibility covers three layers: whether executions are logged, whether failures surface as alerts, and whether per-step detail is available when something goes wrong.

A workflow failing 20 percent of the time looks identical to a working one until you check the logs. Most plugins put per-step logging behind a paid tier or omit it entirely.

When evaluating any plugin, ask these four questions directly:

• Is there a log of every execution, successful and failed?
• Does the log show which specific step failed and what the error was?
• Are failure notifications sent by email automatically, or do you have to check manually?
• Is there an automatic retry with configurable backoff, or do failed executions just disappear?

Krom Automation includes a full per-step audit trail in the free version, automatic email failure notifications, and automatic retry with configurable backoff. It also includes an analytics dashboard showing total executions, active workflows, failed execution count, and an execution trend chart. You can read how the execution model works before you install anything.

Question 5: Where Do Your Credentials Live?

Every automation plugin that connects to an external service needs API credentials: keys for Mailchimp, tokens for Slack, authentication details for Google Sheets. The question is where those credentials are stored and who can access them.

Cloud-based automation platforms store your credentials on their servers. That is not inherently bad, but it means you are trusting a third party with keys that can send email on your behalf, write to your spreadsheets, and post to your social accounts. It also means that if the platform is acquired, breached, or simply shut down, your credentials are exposed or inaccessible.

Self-hosted plugins store credentials in your own WordPress database. Your keys never leave your server. The tradeoff is that your server security is now the limiting factor, but for most site owners that is a tradeoff they are comfortable making because they already trust their host with their customer data.

• Self-hosted storage: Credentials stay in your database. No third-party access. Security depends on your host.
• Cloud storage: Credentials held by the platform. Convenient. Dependent on that platform’s security and continued existence.
• Hybrid: Some plugins store tokens locally but relay executions through a cloud middleware. Check which model applies before connecting anything sensitive.

For sites handling WooCommerce orders, membership data, or anything regulated, the self-hosted model is almost always the better answer. Execution logs, API credentials, and workflow data all stay in the site’s own database.

Question 6: Does It Cover the Integrations You Actually Need?

Integration lists on plugin marketing pages tend toward maximalism. The real question is whether the specific connection you need works correctly, not whether a logo appears in a grid.

Start with your non-negotiables. If your site runs WooCommerce and you need to sync new customers to Mailchimp, confirm that the WooCommerce order trigger and the Mailchimp subscribe action are both present, both free, and both tested against your version of WooCommerce. Do not assume.

Some common integrations to verify specifically:

• Forms: Gravity Forms, WPForms, Fluent Forms, Contact Form 7, Elementor Forms. Many automation plugins treat form submissions as a Pro-only trigger.
• Email marketing: Mailchimp, ConvertKit, MailerLite, ActiveCampaign, FluentCRM. Check whether tagging and list management are included, not just basic subscribe.
• LMS and membership: LearnDash, TutorLMS, MemberPress. Course completion and membership expiry triggers are frequently missing from free tiers.
• Messaging: Slack, Discord, Twilio, Telegram. Useful for internal alerts on order events or new user registrations.

Krom Automation’s Pro version covers 24 integrations across forms, e-commerce, CRM, email marketing, LMS, membership, messaging, social media, data storage, productivity, and affiliate. The documentation pages for Gravity Forms, Mailchimp, LearnDash, and Slack, Discord, Twilio, and Telegram each include setup steps and real automation examples, so you can confirm fit before purchasing.

If your site uses a tool not covered by any WordPress-native plugin, a self-hosted plugin with an HTTP Request action gives you a manual escape hatch. You can call any REST API directly from a workflow without waiting for a native integration to be built.

Question 7: What Happens When the Licence Lapses?

This is the question nobody asks until they need to cancel. The answer varies enormously between plugins and between plugin companies.

Three possible outcomes when a licence expires or is cancelled:

• All workflows keep running: The plugin continues to function. You lose access to Pro features and updates, but automations built during the licence period still execute. This is the buyer-friendly model.
• Workflows pause until renewed: The plugin disables itself or puts all workflows into a suspended state until a payment is made. Common with SaaS-style plugins.
• Workflows are deleted or inaccessible: The worst case. All workflow data is tied to an active subscription. Cancellation means losing the work, not just the features.

The question to ask every automation plugin vendor before buying is simple: if I cancel my licence next year, do my automations keep running? The answer tells you everything about how they think of you.

Always confirm the lapse behaviour in writing, in the terms of service, or through a support ticket before purchasing. Lifetime plans sidestep this issue entirely for features available at purchase time, which is one reason they are worth evaluating seriously even at a higher upfront cost.

The related question is migration cost. If you decide to switch plugins in 18 months, what transfers? Most workflow builders are proprietary.

There is no universal import format. You are rebuilding from scratch on the new platform. Factor 2 to 4 hours of rebuild time per complex workflow into your switching cost estimate, plus any overlap period where you run both plugins simultaneously.

A Decision Matrix: Matching Plugin Type to Your Situation

The right answer to “which plugin” depends on what your site actually needs. This table maps four common situations to the type of tool that fits best.

Your situation	Best fit	Why
WordPress-only triggers and actions, budget matters	Self-hosted plugin, free tier	No per-execution cost. Data stays on your server. Free tier covers most common events.
Need to connect two external services with no WordPress involvement	Cloud platform (Zapier, Make)	WordPress-native plugins need a WordPress event on one side of the workflow.
WooCommerce store with order and customer automation	Self-hosted plugin with WooCommerce integration	Order volume makes per-task billing expensive. Native integration avoids webhooks.
Agency managing 10+ client sites	Plugin with unlimited-site licence	Per-site licensing multiplies fast. Unlimited plans pay for themselves at 4 to 5 sites.
Sensitive credential storage (membership, regulated data)	Self-hosted, credentials in own database	Third-party cloud storage adds a dependency and a potential breach surface.

What the Marketing Pages Do Not Tell You

Every plugin’s features page shows what it can do. None of them explain the following with any specificity.

WP-Cron dependency for delayed actions. Plugins that use WordPress’s built-in scheduler to fire delayed actions depend on site traffic to trigger the cron job. On a low-traffic site, a delay set for “2 hours from now” might fire 4 or 6 hours later if no one visits during that window. The fix is a real server cron job, which requires hosting access.

This is not a flaw unique to any one plugin. It is a WordPress infrastructure issue, but it is almost never explained upfront.

Performance impact during execution. Background execution via Action Scheduler (the same library WooCommerce uses) keeps workflow processing off the page load path. Plugins that execute synchronously during a request can add 200 to 800 milliseconds to page load time on complex workflows. Check how background processing is handled, not just whether it exists. You can read more about WordPress admin performance if this is a concern for your site.

Conflict risk between two automation plugins. Running two automation plugins simultaneously is a common mistake, especially when one handles WooCommerce and another handles user onboarding. Hook priority conflicts can cause the same event to fire twice, or cause one plugin to intercept an event before the other sees it. The practical rule: use one automation plugin per site and cover edge cases with the HTTP Request action rather than a second plugin.

The true cost of “free” add-ons. Some automation ecosystems have a low base plugin price and a large catalogue of paid extensions. A $49 base plugin plus $29 each for WooCommerce support, email marketing, and LMS integration becomes $136 before you have built a single workflow. Map out your full required integration list and price the complete setup, not just the base plugin. For a realistic picture of what add-on costs accumulate to, this breakdown of AutomatorWP add-on costs shows how the numbers stack up.

The Free Version Evaluation Approach

The most reliable way to evaluate any automation plugin is to use the free version seriously before spending money. Not a trial. Not a sandbox demo. Real workflows on a staging site that mirrors your production environment.

Three things to test specifically during a free evaluation:

• Build one workflow you actually need and verify that it fires correctly end to end. Not a test workflow. The real thing.
• Deliberately trigger a failure by using an invalid email address or a bad API key, and check whether the failure surfaces in the log within 5 minutes.
• Export the workflow as a file and confirm the format is something you can re-import. Portability matters if you ever need to move between environments or back up your work.

Krom Automation’s free version includes 16 triggers, 21 actions, the full visual workflow builder, execution logging, a workflow simulator, and import and export as portable JSON. There is no trial period and no run cap. Download the free plugin from the WordPress.org plugin directory and run it on a staging site before deciding whether Pro features are worth the investment for your specific use case.

For a structured comparison of what the free and Pro versions each include, the free vs Pro feature comparison covers every difference in one place.

A Note on AI-Powered Automation

Several plugins now include AI features. The questions to ask are the same as for any other feature, plus two additional ones specific to AI.

• Does the AI run on the plugin vendor’s infrastructure, or do you bring your own API key? Vendor-hosted AI means your content goes through their servers and their markup. Bring-your-own-key means you pay the AI provider directly at standard rates with no intermediary.
• Which models are supported? GPT-4o and Gemini 2.5 Pro are meaningfully different in capability and cost from smaller models. A plugin that says “AI included” without specifying the model is not telling you the full story.

Krom Automation supports OpenAI (GPT-4o Mini and GPT-4o), Google Gemini (Gemini 2.0 Flash, Gemini 2.5 Flash Preview, Gemini 2.5 Pro Preview), and Groq (Llama 3.3 70B, Llama 3.1 8B) in the free version. You supply your own API key and pay your AI provider directly. There is no per-call markup and no paywall on the AI actions themselves.

What the Landscape Looks Like in 2026

The WordPress automation plugin market has matured significantly. There are now several credible options across the self-hosted and cloud-hybrid categories. Uncanny Automator, AutomatorWP, and WP Fusion have established user bases and large integration catalogues built over multiple years. Newer entrants including Krom Automation offer visual canvas builders and built-in AI that older tools are adding retroactively.

The practical implication is that switching costs are real and rising. The more complex your workflows, the more expensive it becomes to migrate between platforms. Choosing well the first time is worth the extra evaluation time. A week spent on due diligence using the framework above is less expensive than rebuilding 20 workflows 18 months from now.

Cloud platforms like Zapier and Make remain the better answer when automation spans two external services with no WordPress involvement on either side. For anything where WordPress is the source of the trigger or the target of the action, a self-hosted plugin almost always wins on cost, data control, and integration depth. This comparison of Zapier costs for WordPress tasks shows where the crossover point tends to land.

Our Verdict

If your site runs on WordPress and you are primarily automating things that happen on that site, start with a self-hosted plugin. Work through the seven questions above before installing anything. Pay particular attention to run limits, lapse behaviour, and credential storage, because those are the three answers that bite people most often and that marketing pages most reliably obscure.

For most WordPress sites in 2026, the combination of a capable free tier and a flat-fee Pro plan with unlimited executions is the correct structure. It removes per-task billing risk, keeps data on your own server, and gives you a predictable annual cost that does not scale with your workflow volume. If that matches what you need, review the Krom Automation plan options and see whether the feature set covers your specific integrations before committing to anything.

If you need automation between two external cloud services with no WordPress involvement, use a cloud platform for that job and do not try to force a WordPress plugin to do it. The tools that win at one job are not always the tools that win at both.

Frequently Asked Questions

What is the difference between a WordPress automation plugin and using Zapier?

A WordPress automation plugin runs on your own server and fires from WordPress events natively. Zapier runs on Zapier’s servers and typically requires a webhook or polling connection to reach your WordPress site. Self-hosted plugins are usually more cost-effective for high-volume WordPress tasks and keep your data on your own server. Zapier is the better choice when both the trigger and the action involve external services with no WordPress involvement on either side.

Will adding an automation plugin slow down my site?

A plugin that processes workflows in the background using Action Scheduler adds no measurable latency to page loads. A plugin that processes synchronously during a request can add 200 to 800 milliseconds depending on workflow complexity. Always confirm that background processing is used, not just advertised.

On the admin side, 9 custom database tables is a reasonable footprint for a plugin with full execution logging. Check your staging environment under realistic load before going live.

How do I know if two automation plugins will conflict with each other?

Hook priority conflicts between two automation plugins can cause the same event to fire twice or cause one plugin to intercept an event before the other sees it. The safest approach is to run one automation plugin per site. If you have edge cases not covered by your primary plugin, use its HTTP Request action to call external services rather than installing a second automation tool.

How many automations can I run before hitting limits or extra fees?

That depends entirely on the plugin’s billing model. Self-hosted plugins with flat-fee licensing have no per-execution cost. A 500-user registration month with a 3-step welcome workflow generates 1,500 executions at zero marginal cost.

Cloud platforms that bill per task can charge $30 to $80 for the same volume. Read the pricing page carefully and look for the word “executions” or “tasks,” not just “automations” or “workflows.”

Can one plugin handle everything, or do I need several for different tasks?

One well-chosen plugin should cover most automation needs for a typical WordPress site. The exception is when you need automation between two external services with no WordPress involvement, where a cloud platform like Zapier or Make is the right tool. Beyond that specific case, running two WordPress automation plugins simultaneously increases conflict risk and rarely adds capability that a single plugin with an HTTP Request action could not cover.