You can send a welcome email when a user registers on WordPress using Krom Automation, a free visual automation plugin. Set the User Registered trigger, connect a Send Email action, drop in merge tags like {{user.display_name}} and you are done. The whole setup takes under 10 minutes and the free plugin covers everything, no Pro required for a single welcome email.

WordPress ships with a bare-bones notification that goes to the admin, not the user, and when it does reach the user it is plain text with no branding and no call to action. That email does almost nothing to onboard a new member, customer or student. A personalised welcome message sent within seconds of registration is one of the highest-open-rate emails a site will ever send, because the reader just took an action and the context is still fresh.

This guide walks through the exact setup in Krom Automation: trigger, delay, personalised body with merge tags, a dry-run test using the built-in simulator, and an AI-generated variant for sites that want something more tailored. We also cover role-based branching, deliverability, and the WP-Cron timing issue that trips up low-traffic sites.

Browse the full feature list or jump straight to the walkthrough below.

Quick Summary

Goal	What you need	Free or Pro?
Send one welcome email on registration	User Registered trigger + Send Email action	Free
Personalise with the user’s name and username	Merge tags in the email body	Free
Delay the email by 5 minutes	Delay node (minutes, hours, days)	Free
Test without sending a real email	Workflow Simulator	Free
AI-written personalised email body	AI Generate Text action	Free (bring your own API key)
Send different emails by user role	Conditional branching (Yes/No paths)	Free
Multi-step onboarding sequence	Multiple Send Email actions with delays	Free
Branded HTML email with a visual builder	Visual Email Builder	Pro
Trigger from a form plugin (Gravity Forms, WPForms, Fluent Forms)	Form-specific trigger	Pro

Why the Default WordPress Registration Email Falls Short

Out of the box, WordPress sends two emails on registration: one to the admin saying a new user joined, and one to the user containing only their username and a password reset link. Both are plain text. Neither carries your branding, your product name, or any guidance on what to do next.

Research consistently shows that welcome emails average open rates above 50 percent, often 3 to 4 times higher than a standard newsletter. Sending the wrong thing at that moment is not a neutral outcome. It is a missed handshake with a reader who was ready to engage.

The plugins most commonly recommended for this, such as Better Notifications for WP, solve the plain-text problem but stop there. They give you a customisable template with shortcodes, but no conditional logic, no delays, no sequences, and no analytics on whether the email actually ran. Krom Automation treats the welcome email as the first step in a workflow, not a standalone notification, which means you can extend it later without rebuilding from scratch.

A welcome email sent at registration has a 50-plus percent open rate. What you put in that email matters more than almost any campaign you will ever run.

Step-by-Step: Send a Welcome Email When a User Registers on WordPress

Everything below uses the free version of Krom Automation. Download the free plugin from the WordPress.org plugin directory, install it, and activate it before starting. Full installation instructions are in the Krom Automation installation guide.

Step 1: Create a New Workflow

Go to Krom Automation > Workflows in your WordPress admin and click Add New. Give the workflow a name you will recognise, such as “Welcome Email on Registration”. The canvas opens with a blank start node.

You can also load one of the 20 free workflow templates. There is a welcome email template in the User category that pre-populates the trigger and a basic Send Email action, which saves a few clicks if you want a starting point.

Step 2: Set the User Registered Trigger

Click the trigger node and select User Registered from the User trigger group. This fires once each time a new account is created through any standard WordPress registration path: the default login page, WooCommerce checkout, or any plugin that calls the native user_register hook.

The trigger exposes a set of merge tags automatically, including {{user.display_name}}, {{user.user_email}}, {{user.user_login}} and {{user.ID}}. You will use these in the email body. The full list is documented in the merge tags reference.

Step 3: Add a Short Delay (Optional but Recommended)

Sending a welcome email the instant someone hits the registration button can feel robotic, and it also means the email races the password confirmation email that WordPress sends natively. A 5-minute delay lets WordPress finish its own notifications first and makes your welcome feel slightly more considered.

Click the plus icon below the trigger, select Delay, and set it to 5 minutes. Delays in Krom Automation run via Action Scheduler, so they do not block page loads. The delay documentation covers all available units, including minutes, hours, days, weeks and a custom seconds value, in the delays and scheduling guide.

Step 4: Add the Send Email Action

Add a Send Email action after the delay node. Fill in the following fields:

• To: {{user.user_email}} (sends to the newly registered user)
• From name: Your site or brand name
• Subject: Something like “Welcome to [Site Name], {{user.display_name}}”
• Body: Your welcome message, with merge tags for personalisation

A simple body might read: “Hi {{user.display_name}}, thanks for joining. Your login is {{user.user_login}}.

Here is where to start: [link to your getting started page].” That is already meaningfully better than the default WordPress email. The full actions reference lists every available field and its accepted values.

Step 5: Test with the Workflow Simulator

Before activating the workflow, run it through the Workflow Simulator. Click the simulator button in the top toolbar, supply a test user ID, and the simulator executes every step in dry-run mode: no email is sent, no database rows are written, but you see exactly what would happen at each node, including the resolved values of every merge tag.

This is the correct way to verify the workflow. Registering a real test account works too, but the simulator is faster and leaves no test users in your database. Full instructions are in the workflow simulator documentation.

Step 6: Activate and Monitor

Toggle the workflow to Active. From this point, every new registration triggers the sequence automatically.

The analytics dashboard shows total executions, success rate and failed execution count. The execution log gives you a per-step audit trail so you can see exactly when an email fired and what merge tag values it resolved to.

If an execution fails, for example because a user registered with no email address, Krom Automation sends you a failure notification and retries automatically with configurable backoff.

The simulator is the single biggest time saver in the plugin. Running a dry test takes 30 seconds. Finding out the merge tags resolved incorrectly after 200 registrations does not.

How to Personalise the Welcome Email with AI

The free plugin includes three AI actions: AI Generate Text, AI Content Moderation and AI Auto-Tag. You can use AI Generate Text to write the welcome email body dynamically rather than using a static template.

To set this up, insert an AI Generate Text node before the Send Email action. In the prompt field, write something like: “Write a warm, brief welcome email for a new user named {{user.display_name}} who just registered on [site name].

Keep it under 100 words. Do not include a subject line.”

The AI action outputs generated text. Store that output in a variable and reference it in the Send Email body field. The result is a unique email for every registration, which reads noticeably differently from a template.

You connect your own API key, and you pay your provider directly at standard rates. Supported providers and models in the free version include OpenAI GPT-4o Mini and GPT-4o, Google Gemini 2.0 Flash and 2.5 Flash Preview, and Groq Llama 3.3 70B. For a broader look at what AI can do across a WordPress site, see our guide on using AI to automate WordPress.

How to Send Different Welcome Emails Based on User Role

Not every registrant should get the same email. A customer who registers during WooCommerce checkout has different needs from a member who signed up for a course or a contributor who requested an account. Krom Automation handles this with conditional branching, available free.

After the User Registered trigger, add a Condition node and set the condition to check {{user.role}}. Each branch gets its own Send Email action with a subject line and body written for that audience:

• Customer role: “Your order account is ready. Here is how to track orders.”
• Subscriber role: “You are now subscribed. Here is what to read first.”
• Editor role: “Welcome to the team. Here is the editorial calendar.”

You can chain as many condition nodes as you need. Each Yes/No path is independent, so a customer never sees the contributor email and vice versa. The full logic reference is in the conditions and branching documentation.

How to Build a Multi-Step Welcome Sequence

Every competing tutorial treats the welcome email as a single message. It does not have to be. Because Krom Automation runs on a canvas with delays, you can build a full onboarding sequence from one workflow:

1. Immediately (0 min): Internal Slack or email notification to your team that a new user registered
2. 5 minutes later: Welcome email with login instructions and a link to your getting started guide
3. Day 2: A follow-up email pointing to your most popular content or feature
4. Day 7: A check-in email asking if they need help, with a link to support

Each step is a node on the canvas. Add a delay between each Send Email action and the sequence runs automatically for every new registrant.

The Run Once per entity setting ensures no user receives the sequence more than once, even if they somehow trigger the workflow twice. For Slack notifications, the messaging integrations guide covers Slack, Discord, Twilio and Telegram setup.

Connecting Registration to Your Email Marketing Tool

Sending the welcome email through Krom Automation is fine for transactional messages. For ongoing marketing, you probably want new registrants added to your email list automatically at the same moment. Add a second action branch from the User Registered trigger to subscribe the user to your list.

Krom Automation Pro connects to Mailchimp, ConvertKit, MailerLite, MailPoet, ActiveCampaign and FluentCRM, all on the same canvas as your welcome email workflow. Documentation for each integration is available separately:

• Mailchimp integration: subscribe, tag and sync users automatically
• FluentCRM integration: contacts, tags and lists
• MailerLite integration: subscribe, unsubscribe and manage groups
• ConvertKit integration: subscribers, tags, sequences and forms

That means a single registration event can fire the welcome email AND subscribe the user to your list AND tag them in your CRM, all in the same workflow without writing a line of code.

What About Deliverability? The Part Nobody Else Covers

Every tutorial for this topic assumes wp_mail() just works. It often does not. WordPress sends email via PHP mail by default, which most hosting providers either block outright or let through in a way that makes the email look suspicious to spam filters.

Before relying on any welcome email workflow, configure an SMTP plugin and verify your domain has valid SPF and DKIM records pointing to your sending provider. Tools like WP Mail SMTP or FluentSMTP handle this. Without proper authentication, a welcome email that triggers correctly in Krom Automation can still land in the user’s spam folder or disappear entirely, and the execution log will show a successful send because WordPress accepted the handoff to PHP mail.

Krom Automation’s failure notifications and execution logs will not catch a deliverability problem at the SMTP level. They tell you whether WordPress accepted the email for sending.

Whether it arrived is a question for your SMTP provider’s delivery logs. This is the honest limitation every automation plugin shares, not just Krom Automation.

The WP-Cron Timing Issue on Low-Traffic Sites

Delayed actions in Krom Automation run through Action Scheduler, which relies on WP-Cron. WP-Cron fires when someone visits your site. On a site that receives very little traffic, a delay set to 5 minutes might not execute until the next visitor arrives, which could be an hour later.

The fix is a real server cron job that calls wp-cron.php on a schedule, typically every 5 minutes. Your hosting control panel usually supports this. Once a real cron is in place, delays run on time regardless of traffic.

For a welcome email, a few minutes of imprecision is harmless. For time-sensitive automations, the server cron is not optional.

Action Scheduler is solid infrastructure. WP-Cron is the weak link, and on a quiet site it is the only reason a delay does not run on time. Fix the cron and the rest takes care of itself.

What This Does Not Cover (Honest Constraints)

A few scenarios that fall outside this setup:

• Registration via third-party forms: If users register through Gravity Forms, WPForms, Fluent Forms, or Elementor Forms, the User Registered trigger may fire depending on whether the form creates a WordPress user. Pro-tier integrations give you form-specific triggers with access to every field. See the Gravity Forms integration docs or the WPForms integration docs for the exact setup.
• Email confirmation gating: If you want to send the welcome email only after the user confirms their address, you need a plugin that adds email confirmation to the registration flow. The User Registered trigger fires on account creation, not on confirmation.
• Suppressing the default WordPress notification: WordPress sends its own registration email separately. Krom Automation does not suppress that. If you want to remove the default email, you need a small code snippet using the wp_new_user_notification_email filter, or a plugin that manages registration emails.
• Membership-gated registration: Sites using MemberPress, BuddyBoss or similar have their own registration flows with additional triggers. The MemberPress integration and BuddyBoss integration cover those scenarios.

Free vs Pro: What You Actually Need for Welcome Emails

Use case	Free	Pro
Single welcome email with merge tags	Yes	Not needed
Delayed delivery (minutes, hours, days)	Yes	Not needed
AI-generated email body	Yes (bring your own key)	Not needed
Role-based conditional branching	Yes	Not needed
Multi-step onboarding sequence	Yes	Not needed
Execution logs and analytics	Yes	Not needed
Branded HTML email with visual builder	No	Yes
Subscribe user to Mailchimp or FluentCRM at the same time	No	Yes
Trigger from Gravity Forms or WPForms registration	No	Yes
80+ additional triggers for advanced conditions	No	Yes

Pro starts at $69 a year or $199 as a lifetime purchase for a single site. See the full plan comparison to decide whether the email marketing integrations or the visual email builder justify the upgrade for your site.

Also from wpRigel

Pollify is our Gutenberg-native poll, survey and quiz plugin. Polls are built directly as blocks inside the editor, so there are no shortcodes to paste and no separate interface to configure. It is worth knowing about if you want to collect structured feedback from the users you are now onboarding.

Commandify is a command palette for the WordPress admin. Press Cmd or Ctrl plus K to jump anywhere in your dashboard, search content, and run admin actions without clicking through menus. It is the only command palette with genuine WooCommerce order, product and customer commands built in.

Our Verdict

If your goal is a personalised, conditional, logged welcome email that you can extend into a full onboarding sequence later, the free version of Krom Automation is the right tool and the setup takes less than 15 minutes. The visual canvas makes the logic readable at a glance, the simulator means you never test on real users, and the execution logs tell you exactly what ran and when.

If you only need a static plain-text welcome email and have no plans to add logic or sequences, a lightweight notification plugin is a simpler choice. Krom Automation is deliberately more capable than a notification plugin, which makes it slightly more to configure even for the simplest case.

For anyone building a membership site, a course platform, a SaaS on WordPress, or any site where the registration moment matters, start with the free plugin, get the welcome email working, then decide whether the Pro email marketing integrations or the visual email builder are worth the upgrade.

Download Krom Automation free from the WordPress.org plugin directory and follow the first workflow walkthrough in our documentation to have it running in minutes.

See Krom Automation pricing and plan details if you are ready to add email marketing integrations or the branded email builder.

Frequently Asked Questions

Does Krom Automation replace the default WordPress registration email?

No. Krom Automation sends its own welcome email as an additional automation.

The default WordPress registration notification still fires unless you suppress it separately using the wp_new_user_notification_email filter or a plugin that manages that notification. Most sites choose to disable the default and let Krom Automation handle the messaging entirely.

Can I send the welcome email only after the user confirms their email address?

Not with the User Registered trigger alone. That trigger fires when the account is created, not when the address is verified.

If your registration flow requires email confirmation via a plugin, check whether that plugin fires a custom hook on confirmation. If it does, you can use the HTTP webhook receiver in Krom Automation Pro to catch it, or request a native trigger on the Krom Automation roadmap.

Why is my welcome email going to spam?

Almost certainly a deliverability issue, not an automation issue. WordPress uses PHP mail by default, which lacks SMTP authentication and is treated as suspicious by most inbox providers.

Install an SMTP plugin, configure it with your sending provider, and verify your domain has SPF and DKIM records in place. Once those are correct, emails sent through Krom Automation arrive like any properly authenticated message.

Can I send different welcome emails based on which registration form the user used?

Yes, in two ways. For role-based differences, use a Condition node on {{user.role}} in the free plugin. For form-specific differences based on which Gravity Forms, WPForms or Fluent Forms form the user completed, you need the Pro-tier form integrations, which give you form-specific triggers with access to individual field values.

How do I resend a welcome email to a user who did not receive it?

Open the execution log for the workflow and find the original execution for that user. If it failed, the log shows the reason and the retry count.

If you want to trigger a resend manually, you can do so from the execution log or by using the HTTP Request action to call your own workflow endpoint. For a one-off resend, the simplest approach is temporarily duplicating the workflow, setting it to run once, and manually triggering it with the user ID.

Does registering through WooCommerce checkout trigger the User Registered event?

Yes. When a customer creates an account during WooCommerce checkout, WordPress creates a standard user record and fires the same user_register hook.

Krom Automation’s User Registered trigger catches this automatically. If you want to send a different welcome email to customers versus other registrant types, add a Condition node checking whether the user has the Customer role.

You can automatically tag WordPress posts with AI using Krom Automation, a free WordPress plugin. The AI Auto-Tag action is included in the free version, no Pro licence required.

You connect a “Post Published” trigger to the AI Auto-Tag action, supply your own API key from OpenAI, Google Gemini or Groq, and every new post gets tagged the moment it goes live. The whole setup takes under 10 minutes.

The free plugin handles tagging for new posts on publish. If you need to retroactively tag hundreds or thousands of existing posts, the most practical approach combines a scheduled workflow with a Post Updated trigger, which lets you process your back catalogue in controlled batches. We cover both flows below, along with the tag governance decisions that every other guide skips entirely.

This guide also addresses the question nobody answers directly: how many tags should AI assign, what happens to your existing tags, and how do you stop a well-meaning automation from turning your tag archive into 400 near-duplicate terms that confuse both readers and search engines.

Browse the full feature list to see every free trigger and action before you commit to a setup.

What the AI Auto-Tag Action Actually Does

The AI Auto-Tag action reads the post content and uses your chosen AI model to generate relevant tags. It then applies those tags to the post inside WordPress, the same way you would add them manually from the editor. No markup is altered, no post content is modified, and the action leaves existing tags in place by default.

The critical behaviour to understand before you build a workflow: by default, the action adds tags rather than replaces them. If a post already has three manually set tags, the AI adds its suggestions alongside them.

This is the right default for most sites. If you want the AI to own tagging entirely and ignore any manual tags, that is a deliberate choice you make in the action settings, not an accident.

Tag creation behaviour also matters. The action can be configured to:

• Use existing tags only, so the AI matches content to tags already in your database and never creates a new term
• Create new tags freely, so the AI generates whatever terms fit the content, even if those terms do not yet exist in WordPress
• Cap the maximum tag count per post, which we recommend setting to between 3 and 7 to prevent tag sprawl

For most editorial sites, “existing tags only” is the safer starting point. You define the vocabulary once, the AI applies it consistently, and your tag archive stays clean. Switching to “create new tags” makes sense when you are building a new site and want the AI to help you discover what your tag taxonomy should be, not when you are managing an established archive.

Letting AI create tags freely on an established site is like hiring a filing clerk who invents their own categories. The filing gets done. Finding anything afterward takes twice as long.

Which AI Providers Work and What Do They Cost You

Krom Automation never charges per AI call and never marks up tokens. You bring your own API key, pay your provider at their standard rate, and the cost goes directly to them. wpRigel takes nothing from that transaction.

The free plugin supports seven models across three providers:

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

For auto-tagging specifically, GPT-4o Mini and Gemini 2.0 Flash are the cost-effective choices. A typical 1,000-word post generates a tagging request of roughly 1,000 to 1,500 tokens in and 20 to 50 tokens out.

At GPT-4o Mini rates, tagging 500 posts costs well under $1. If you are processing a large back catalogue, Groq’s Llama models are free on the free tier up to their rate limits, which makes retroactive bulk tagging on a budget genuinely achievable.

Setting Up Auto-Tagging for New Posts: Step by Step

Before you build the workflow, read how Krom Automation works if this is your first workflow. The core model is simple: a trigger fires when something happens, actions run in response, and the canvas connects them visually.

To tag every new post on publish:

1. Install and activate the free Krom Automation plugin from the WordPress.org plugin directory
2. Go to Krom Automation in your WordPress admin and click “Add New Workflow”
3. On the canvas, add the Post Published trigger and set the post type to “Post” (or whichever post type you want to tag)
4. Add the AI Auto-Tag action and connect it to the trigger node
5. In the action settings, choose your AI provider, paste your API key, and set your maximum tag count and tag creation mode
6. Save and activate the workflow

The next post you publish will be tagged automatically within seconds of the trigger firing. Use the workflow simulator to run a dry test against an existing post before you go live. It shows exactly what tags would be applied, with zero side effects on real content.

If you want to add a human review step, you can insert a conditional branch after the AI Auto-Tag action. See the conditions and branching documentation for how to build Yes and No paths, which lets you route borderline posts to a draft status for manual review while publishing clean ones immediately.

How to Bulk Auto-Tag Existing Posts

Every other auto-tagging guide ignores your existing content. Most sites have hundreds or thousands of posts that predate any AI tool, and those posts are the ones with the most search traffic at stake. Here is a practical approach for processing them without breaking your site or your tag taxonomy.

The core problem with bulk retroactive tagging is volume control. Sending 2,000 posts to an AI provider at once is not a workflow, it is an invoice. The safer approach is batching: process 20 to 50 posts per run, on a schedule, until the back catalogue is done.

In Krom Automation Pro, the Schedule Trigger lets you fire a workflow hourly, daily or on a custom interval. Combined with a query that fetches untagged posts and passes them through the AI Auto-Tag action, you get controlled batch processing with full execution logs and failure notifications if anything goes wrong.

For the free plugin, the practical equivalent is to export a CSV of untagged post IDs, bulk-edit them in batches inside WordPress to trigger a “Post Updated” event, and let the workflow catch each update. It is more manual, but it works and costs nothing beyond the API calls.

Retroactive tagging is not a one-afternoon job. It is an editorial project. The sites that do it well set a tag limit, audit the results after the first 100 posts, and adjust the prompt before running the rest.

Tag Governance: The Part Every Other Guide Skips

Tag sprawl is when your tag archive slowly fills with near-duplicate terms: “marketing strategy”, “marketing strategies”, “content marketing strategy”, “digital marketing tips”. Each term has one or two posts attached.

None of them rank for anything. All of them generate thin archive pages that dilute your site authority.

AI auto-tagging accelerates whatever tagging discipline you already have. Good discipline scales well. No discipline scales into a mess faster than you can clean it up.

Before you run any auto-tagging workflow, answer these three questions:

• What is the maximum number of tags per post? We recommend 3 to 7. More than 7 and the tags stop being meaningful signals. Fewer than 3 and you are not getting the taxonomy coverage the feature exists to provide.
• Who owns the tag vocabulary? If the AI creates new tags freely, nominate someone to audit new terms weekly. A monthly audit is too infrequent once you have a high-volume site.
• What is your merge strategy for near-duplicates? WordPress does not merge tags automatically. You will need a taxonomy management plugin or manual cleanup when you spot drift. Building the cleanup step into your governance workflow from day one is far cheaper than a one-off cleanup of 600 tags six months from now.

The “existing tags only” mode in the AI Auto-Tag action is the best technical safeguard. If the AI can only choose from the 80 tags you have already defined, the worst it can do is pick a slightly imprecise match.

That is recoverable. A freely-generating AI choosing new tag names daily is not.

Will AI Auto-Tagging Help or Hurt Your SEO?

The honest answer is: it depends entirely on how you configure it, and the risk comes from the output rather than the mechanism.

Tags in WordPress generate archive pages. Each archive page is a URL that Google crawls and indexes.

A tag with 30 posts behind it is a meaningful topical signal. A tag with one post behind it is a thin page with near-zero ranking potential, and if you have 200 of those, you are giving Google 200 reasons to view your site as shallow.

The configuration choices that protect your SEO:

• Set the tag creation mode to “existing tags only” until your taxonomy is mature
• Cap tags per post at 5 or fewer during the initial rollout
• Use the execution logs in Krom Automation to review the first 50 tagged posts before running the full back catalogue
• Add noindex to tag archives with fewer than 5 posts, using Yoast SEO or RankMath’s taxonomy settings, until the archive builds enough content to justify indexing

Done this way, AI auto-tagging is a genuine SEO lever. Consistent tagging across hundreds of posts creates topical clusters that manual tagging rarely achieves because it is too easy to forget a tag or use a slightly different term on each post.

Does This Work With WooCommerce Products and Custom Post Types?

Yes. In the Post Published trigger, you set the post type. WordPress registers WooCommerce products as the “product” post type.

Set the trigger to “product” and the AI Auto-Tag action will tag products exactly as it tags posts. The same applies to any custom post type registered on your site.

If you run WooCommerce, you may also find the WooCommerce Subscriptions integration useful for broader order and subscription automation beyond tagging. And if your site uses forms to gather data that informs content creation, the Gravity Forms integration and WPForms integration let you trigger other workflows from form submissions in the same canvas.

The Timing Limitation You Should Know About

Krom Automation runs background tasks via Action Scheduler, the same queue system WooCommerce uses. This means the AI Auto-Tag action does not run during the page load that saves your post. It fires in the background, typically within a few seconds on a site with normal traffic.

On very low-traffic sites, WP-Cron only fires when someone visits the site. If your site goes several hours without a visitor, a scheduled or queued action waits until the next visit before it runs.

The fix is to disable WP-Cron in wp-config.php and configure a real server cron job to call the WordPress cron endpoint every minute. This is a one-time server configuration that costs nothing and makes every time-dependent automation on your site more reliable, not just Krom Automation.

For a broader view of how AI can power WordPress automation beyond tagging, see our guide on using AI to automate your WordPress site.

Free vs. Pro: What Do You Actually Need for Auto-Tagging?

Use case	Free plugin	Pro required
Tag new posts on publish	Yes	No
Tag WooCommerce products on publish	Yes	No
Tag custom post types on publish	Yes	No
Conditional branch after tagging (review step)	Yes	No
Dry-run testing with the simulator	Yes	No
Scheduled batch processing of existing posts	No	Yes (Schedule Trigger)
AI workflow generation from plain English	No	Yes
Incoming webhook to trigger tagging from external events	No	Yes

The free plugin handles the primary use case fully. Pro becomes relevant when you want to run scheduled batch jobs against existing content or trigger tagging from external systems via webhook.

What It Costs Across One, Five and Twenty Sites

Scenario	Free plugin only	Krom Pro Basic (1 site)	Krom Pro Standard (5 sites)	Krom Pro Enterprise (unlimited)
1 site, new posts only	$0/year	From $69/year	From $149/year	From $299/year
5 sites, new posts only	$0/year	5x Basic licences	From $149/year	From $299/year
1 site, includes batch back-catalogue	Not available	From $69/year	From $149/year	From $299/year
20+ client sites, agency use	$0/year, manual setup each	Not practical	Not practical	From $299/year
Any tier, lifetime option	Free forever	From $199 once	From $399 once	From $699 once

Launch pricing is currently applied. See the current pricing for up to date figures. All Pro plans include a 14-day money-back guarantee and every Pro feature, with the only difference between plans being the number of site activations.

For context, at the time of writing, Uncanny Automator’s automation plans start at $199 per year for one site, with AI features starting at $300 per year. Krom Automation’s free tier includes AI actions at no additional cost from wpRigel, which is a material difference for teams watching per-feature costs.

For agencies running 10 or more client sites, the Enterprise lifetime plan at $699 one time competes directly with a single year of per-site SaaS tooling. That is the calculation worth running before you renew anything.

How This Compares to Standalone Auto-Tagging Plugins

There are WordPress plugins built specifically for AI tagging. TagPilot AI uses the Dandelion NLP API and focuses on the install-and-forget flow.

Qwebmaster AI Auto Tagger takes a privacy-first approach where all processing happens on-server with no external API. PublishPress Taxonomies Pro integrates with OpenAI and IBM Watson for taxonomy management at a broader level.

The practical difference with Krom Automation is scope. A dedicated tagging plugin does one thing. Krom Automation does tagging as one of 21 free actions inside a workflow that can also send emails, update post meta, create users, make HTTP requests, and moderate comments.

If tagging is the only thing you need, a dedicated plugin is a legitimate option. If you are already building automations or plan to, adding a tagging step to an existing workflow costs nothing extra.

The other difference is the audit trail. Krom Automation logs every execution with a per-step breakdown, so you can see exactly which tags were applied to which post and when. Debugging a misfiring tag rule in a dedicated plugin typically means searching through a settings page.

In Krom Automation, you open the execution history and read the result directly. Our guide on AI comment moderation shows the same pattern applied to a different content management problem.

Also from wpRigel

Pollify is wpRigel’s Gutenberg-native poll, survey and quiz plugin. Polls are built directly inside the block editor as real blocks, so there are no shortcodes to paste and no separate interface to learn. It is the fastest way to add audience engagement to any post or page without leaving the editor.

Commandify is a command palette for the WordPress admin. Press Cmd or Ctrl plus K from anywhere in the admin to jump to any page, search any content type, and run admin actions without clicking through menus. It is the only command palette plugin with genuine WooCommerce depth, covering orders, products and customers as first-class commands.

Our Verdict: Who Should Use This and Who Should Not

Use the AI Auto-Tag workflow if you publish more than 4 posts per month and find tagging inconsistent across your archive. Inconsistency is the real cost: posts on the same topic tagged differently create fragmented archives that neither readers nor search engines can navigate. The free plugin handles this with zero recurring cost from wpRigel, and the only ongoing expense is your AI provider’s token fees, which are negligible at typical publishing volumes.

Do not use it if your site has fewer than 20 posts total. The overhead of setting up a workflow and governing a tag taxonomy is not worth it at that scale.

Manual tagging takes minutes and gives you full control when the site is small enough for one person to manage in their head. Come back when you are publishing regularly and the manual process starts creating gaps.

For agencies managing multiple client sites, the workflow is worth setting up once, exporting as JSON, and importing to each new site. Krom Automation supports workflow import and export, so you build the tagging workflow once and deploy it everywhere. That is the use case where the Enterprise lifetime plan earns its cost back in the first quarter.

Download the free plugin from the WordPress.org plugin directory and set up your first auto-tagging workflow today. If you decide you need scheduled batch processing for existing posts, compare all three Pro plans to find the right fit.

Frequently Asked Questions

Will the AI Auto-Tag action overwrite my existing tags?

No. By default it adds tags alongside any existing ones.

If you want the AI to replace all existing tags, that is a deliberate setting you change in the action configuration. The default protects manually set tags.

How many tags should AI assign per post?

We recommend capping at 3 to 7 per post. Below 3, the taxonomy coverage is too thin to build meaningful topical clusters. Above 7, the tags start to overlap and lose their value as navigational signals for both readers and search engines.

Does auto-tagging work with custom post types, not just standard posts?

Yes. In the Post Published trigger, you select which post type fires the trigger. Any custom post type registered on your site, including WooCommerce products, is available in that dropdown.

Is there a free AI auto-tagger for WordPress, or do I always need to pay for an API?

Krom Automation is free to download and the AI Auto-Tag action is included at no cost from wpRigel. You do need an API key from OpenAI, Google Gemini or Groq. Groq’s Llama models have a free tier that is sufficient for moderate tagging volumes, making it possible to start with no API cost at all.

Can I auto-tag existing posts, or only new ones going forward?

The free plugin tags posts when they are published or updated, so you can trigger retroactive tagging by batch-updating existing posts. Krom Automation Pro adds a Schedule Trigger that lets you run automated batch jobs against existing content on a set interval without manual edits.

Will AI-generated tags help my SEO or create thin archive pages?

Both outcomes are possible and the configuration determines which one you get. Setting the action to “existing tags only” and capping at 5 tags per post creates consistent topical clusters that support SEO. Allowing the AI to create new tags freely without governance creates thin archive pages quickly.

The technical tool is neutral. The editorial discipline around it is what makes the difference.

You can moderate WordPress comments automatically with AI using Krom Automation, a free WordPress plugin. Connect the Comment Submitted trigger to the AI Content Moderation action, set your sensitivity threshold, and every incoming comment gets scored for spam and toxicity before it touches your moderation queue.

The free plugin covers this entirely. No Pro plan required.

WordPress has no built-in AI moderation. Its native comment controls let you hold all comments for manual review, require prior approval, or rely on Akismet’s pattern-matching filter.

None of those use a language model. They catch known spam signatures but miss nuanced toxicity, off-topic attacks and low-quality noise that looks grammatically clean.

Krom Automation takes a different approach. You bring your own API key from OpenAI, Google Gemini or Groq, connect it once, and the plugin calls the model on every comment that arrives. The result determines whether the comment is approved, held for review or moved to trash, automatically, with a full execution log so you can audit every decision.

Browse the full feature list to see everything the free plugin includes before you install it.

Is Akismet Still Good Enough in 2026?

Akismet is a signature-based filter. It compares incoming comments against a database of known spam patterns and blocks matches.

That works well against bot-submitted garbage, and for many small blogs it is sufficient. The gap appears when spam is new, when it looks legitimate on the surface, or when the problem is toxicity rather than spam.

A comment that reads “Great post, but the author clearly has no idea what they’re talking about” is not spam. Akismet passes it.

A language model can flag it as hostile and hold it for human review before it goes live. That is a genuinely different capability, not a better version of the same thing.

The practical answer is that Akismet and AI moderation solve different problems. Running both together is the configuration that covers the most ground. Akismet handles volume bot attacks cheaply.

AI moderation handles nuance. Sites with active comment sections, community forums or product reviews benefit most from adding the AI layer.

Akismet stops bots. AI moderation stops humans behaving badly. You likely need both, and the free tier of each covers most sites.

How the Free AI Content Moderation Action Works

Inside Krom Automation’s visual workflow builder, you connect nodes on a drag-and-drop canvas. The moderation workflow uses three nodes: a trigger, an AI action and a branch.

• Trigger: Comment Submitted. Fires the moment a comment lands, before it is approved or displayed.
• Action: AI Content Moderation. Sends the comment text to your chosen AI provider and returns a verdict: safe, flagged or blocked, along with a confidence score.
• Branch: Yes/No conditional. Routes flagged comments to a hold action, blocked comments to trash, and safe comments to an approve action. You set the thresholds.

The conditions and branching documentation covers how to configure the Yes/No logic for different sensitivity levels. You can run a strict threshold on a children’s site and a looser one on a debate-oriented publication, using the same workflow structure with different values.

Sensitivity is configurable. A score of 0.7 or above holds the comment. A score of 0.9 or above trashes it.

Those numbers are yours to set. The AI does not make binary decisions on its own. It returns a score, and your threshold determines the outcome.

Which AI Providers Can You Use?

Krom Automation supports seven models across three providers in the free version. You connect your own API key in the plugin settings.

wpRigel never charges per AI call and never marks up tokens. You pay your provider directly at their standard rate.

Provider	Models available (free plugin)	Approximate cost per 1,000 comments
OpenAI	GPT-4o Mini, GPT-4o	$0.01 to $0.15 depending on model and comment length
Google Gemini	Gemini 2.0 Flash, Gemini 2.5 Flash Preview, Gemini 2.5 Pro Preview	$0.01 to $0.10 for most comment volumes
Groq	Llama 3.3 70B, Llama 3.1 8B	Very low; Groq’s inference pricing is among the lowest available

For a blog receiving 500 comments a month, the AI cost using GPT-4o Mini runs well under $1 per month. A high-traffic publisher at 50,000 comments a month should model costs carefully before committing to a premium model. For that volume, Gemini 2.0 Flash or Groq’s Llama 3.1 8B keeps costs in the $5 to $15 range monthly, while GPT-4o at the same volume could reach $75 or more.

The cost modeling matters because no other moderation plugin documentation does it honestly. Choosing the right model for your volume is the most important configuration decision you make.

What Does the Workflow Actually Catch?

Traditional spam filters operate on pattern matching. They look for repeated URLs, known spam domains, or comment text that appeared in their training database.

AI Content Moderation operates on meaning. The model reads the comment as a sentence and scores it against categories you care about.

• Spam detection: Catches low-quality promotional comments, affiliate spam and keyword stuffing that looks grammatically correct and fools signature-based filters.
• Toxicity scoring: Flags hostile, abusive or threatening language even when it uses no known slur and matches no spam pattern.
• Sensitivity detection: Identifies potentially sensitive content appropriate to hold on certain site types, such as health or legal sites where user-generated advice carries risk.
• Off-topic and low-quality signals: Some configurations flag comments that contribute nothing to the discussion, reducing the moderation queue even when a comment is not strictly spam or toxic.

What it does not catch is context it was not given. If a comment uses site-specific jargon that looks hostile out of context, the model may score it incorrectly. The hold outcome exists for exactly that reason.

A held comment goes to your moderation queue rather than being trashed, so a human still reviews edge cases. Only comments scoring above your highest threshold go straight to trash.

Automatic trash should be reserved for the highest-confidence verdicts. Hold everything else and let the queue shrink by 80 percent, not 100 percent.

Setting Up the Workflow: What You Actually Configure

Start with the step-by-step workflow builder guide if this is your first Krom Automation workflow. The moderation setup specifically involves these decisions:

1. Choose your AI provider and model. For most sites, GPT-4o Mini or Gemini 2.0 Flash balances accuracy and cost. Connect the API key in Krom Automation settings.
2. Set the Comment Submitted trigger. This fires before any comment is displayed. The trigger captures comment content, author name, author email and post ID as merge tags available to every downstream action.
3. Configure the AI Content Moderation action. Pass the comment body using the comment content merge tag. Set your sensitivity level: low, medium or high. The action returns a verdict and a numeric score.
4. Add a Yes/No branch on the score. Route scores below your hold threshold to an approve action. Route scores between your hold and trash thresholds to an update comment status action set to “pending”. Route scores above your trash threshold to a delete post action targeting the comment.
5. Enable run-once per entity enforcement. This prevents a single comment from triggering the workflow twice on sites with caching or retry logic.
6. Use the workflow simulator for a dry run. The simulator runs your workflow with zero side effects, so you can confirm the routing logic before it touches live comments.

The merge tags documentation lists every variable the Comment Submitted trigger exposes. Author email is particularly useful if you want to add a second branch that skips moderation for verified registered users with more than five approved comments.

Cost of AI Comment Moderation Versus the Manual Alternative

This is the table nobody publishes. Most plugin pages tell you AI saves time. They rarely show the numbers behind that claim.

Scenario	Manual moderation cost	AI moderation cost (Krom free + API)	Net saving
Small blog, 200 comments/month	45 min/month at $50/hr = $37.50	Plugin free + ~$0.05 API cost	~$37 per month
Active community site, 5,000 comments/month	18 hrs/month at $50/hr = $900	Plugin free + ~$1 to $5 API cost	~$895 to $899 per month
High-traffic publisher, 50,000 comments/month	Dedicated moderator or outsourced, $800 to $2,000/month	Plugin free + $5 to $75 API cost depending on model	$725 to $1,995 per month

The manual cost estimate uses 15 seconds per comment for a trained moderator making a simple approve or trash decision. That is a conservative figure.

Complex community sites where moderators read context and respond to disputes run considerably higher. The AI cost range reflects model choice: Groq Llama 3.1 8B is at the low end, GPT-4o is at the high end.

Even for a small blog, the return is not really about money. It is about whether comment moderation happens at all.

Most site owners on tight schedules let their queue back up for days, which means spam sits visible for hours. Automation eliminates the delay entirely.

Honest Limits: What AI Comment Moderation Gets Wrong

No moderation system is perfect. AI Content Moderation in Krom Automation has specific constraints you should understand before relying on it fully.

• False positives on sarcasm and irony. A comment that uses hostile phrasing in a clearly joking context may score high for toxicity. Set your trash threshold conservatively. Hold is safer than trash for borderline scores.
• Language coverage varies by model. Most models perform best on English. Sites with significant non-English comment traffic should test accuracy on their actual language mix before setting aggressive thresholds.
• WP-Cron timing on low-traffic sites. Krom Automation runs actions via Action Scheduler, which depends on WordPress Cron. On sites that receive fewer than a few visits per hour, WP-Cron can fire late, meaning the moderation action runs minutes after the comment arrives rather than immediately. A real server cron job fixes this. Without it, a flagged comment may sit unapproved rather than visibly published, which is acceptable, but not instant.
• API key dependency. If your API key is invalid, rate-limited or the provider has an outage, the AI action fails. Configure Krom Automation’s failure notification by email and the automatic retry with backoff so you know when this happens.
• Cost at scale without model tuning. If you run GPT-4o on every comment without checking volume first, the monthly API bill can surprise you. Set a budget alert with your provider before enabling on a high-traffic site.

For a broader look at what AI can and cannot do reliably inside WordPress, our post on using AI to automate your WordPress site covers the full picture.

What the Execution Log Gives You

Every comment that passes through the workflow creates a per-step execution record. You can see the comment text that was evaluated, the score returned by the AI, which branch was taken, and the outcome action that ran. This matters for three reasons.

First, it gives you an audit trail if a reader disputes that their comment was removed. You have a timestamped record of the score and the threshold that triggered the outcome. Second, it lets you tune your thresholds over time based on real data rather than guessing.

If you see that 40 percent of your held comments are being manually approved, your hold threshold is probably too aggressive. Third, the analytics dashboard shows a failed execution count and trend chart, so you see immediately if your API key stops working.

The free actions reference documents what each action returns to the execution log, including the AI Content Moderation action’s output fields.

Extending the Workflow Beyond Basic Moderation

Once the core moderation workflow is running, the same trigger and AI action can feed additional steps without creating separate workflows. These extensions all run free.

• Notify the post author when a comment is held. Add a Send Email action on the hold branch so the author knows a comment is waiting for their review, not just sitting in the queue silently.
• Auto-tag approved comments. Use the AI Auto-Tag action after the approve branch to label approved comments by topic, useful for community sites where readers browse by subject.
• Add comment meta on every scored comment. Store the toxicity score as comment meta. This lets you sort or filter comments by score inside WordPress without re-running the AI.
• Send a Slack alert on high-confidence toxic comments. Connect the trash branch to an HTTP Request action pointing to a Slack webhook, or use the Slack and Discord messaging integration if you are on Pro. Your moderation team sees the flagged content in real time without checking the WordPress dashboard.

If your site uses BuddyBoss for community features, the BuddyBoss integration documentation covers how to extend similar moderation logic to activity stream posts and private messages, not just standard WordPress comments.

The real advantage of a workflow tool over a dedicated moderation plugin is that comment moderation becomes one node in a larger response, not the whole system.

Also from wpRigel

Pollify is wpRigel’s poll, survey and quiz plugin, built as native Gutenberg blocks. Creating a poll feels like writing a paragraph in the block editor.

There are no shortcodes and no separate interface to learn. It is the right tool if you want to add structured reader input alongside your comment section.

Commandify is a command palette for the WordPress admin. Press Cmd or Ctrl plus K to jump anywhere, search content, and run admin actions without clicking through menus.

If you moderate comments manually for borderline cases, Commandify cuts the time spent navigating to the comments queue significantly. It is the only command palette with real WooCommerce order, product and customer commands built in.

Verdict: Who Should Set This Up and Who Should Not

Set up AI comment moderation with Krom Automation if your site receives more than 50 comments a month and you currently spend any time on manual moderation. The free plugin plus a Groq or Gemini API key costs almost nothing to run, the workflow takes under an hour to build, and the time saving compounds every month. Community sites, membership sites and WooCommerce stores with active product reviews see the sharpest return.

Do not set this up if your site averages fewer than 10 comments a month. Akismet handles that volume fine, and adding AI infrastructure for a queue you review in two minutes a week adds complexity with no meaningful return.

Also avoid aggressive trash thresholds on sites where community trust matters. Start with hold-only moderation for the first month, review the execution logs, and only move to automatic trash once you have calibrated your thresholds against real comment data.

For most active WordPress sites, this is the automation that pays for itself fastest. Download the free plugin from the WordPress.org plugin directory and build the workflow this week. If you want to review the full plan comparison before going Pro, the free versus Pro feature comparison covers every difference in one place.

See Krom Automation pricing and plan options to find the right plan if you need Pro features across multiple sites.

Frequently Asked Questions

Does WordPress have built-in AI comment moderation?

No. WordPress core includes manual moderation controls and optional Akismet integration, but no AI-powered scoring. A plugin such as Krom Automation is required to add AI moderation via an external language model.

Do I need to bring my own API key for AI comment moderation in Krom Automation?

Yes. You supply an API key from OpenAI, Google Gemini or Groq. Krom Automation calls the model on your behalf and logs the result.

wpRigel does not charge per call and does not mark up token costs. You pay your provider directly at their standard rate.

Will AI moderation block legitimate comments from real readers?

It can produce false positives, particularly on sarcasm, irony or comments using aggressive phrasing in a clearly joking context. The safest configuration uses the hold outcome rather than automatic trash for borderline scores.

Held comments go to your moderation queue rather than disappearing, so a human reviews edge cases. Reserve automatic trash for scores above 0.9 or your equivalent high-confidence threshold.

How much does AI comment moderation cost per month?

Krom Automation is free for this workflow. API costs depend on volume and model choice. A blog receiving 500 comments a month spends under $1 on GPT-4o Mini.

A site at 50,000 comments a month should use Groq Llama or Gemini 2.0 Flash to keep costs in the $5 to $15 range. GPT-4o at that volume can reach $75 or more per month.

Does AI comment moderation work with WooCommerce product reviews?

WooCommerce product reviews use the WordPress comment system internally, so the Comment Submitted trigger fires on them as it does on standard post comments. The AI Content Moderation action evaluates the review text the same way. No additional configuration is required to cover both comment types from one workflow.

What happens if my AI provider has an outage during high comment volume?

The AI action fails and Krom Automation logs it as a failed execution. The plugin sends a failure notification by email and retries automatically with configurable backoff.

The comment is typically left in a pending state during the retry window rather than being auto-approved or auto-trashed. Configure your WordPress default comment setting to hold all comments pending review as a fallback, so nothing publishes unreviewed if retries exhaust.

Yes, ChatGPT can write and publish content on your WordPress site automatically. The safest approach is to use Krom Automation, connect your own OpenAI API key, and let the AI Generate Text action draft the content while a Create Post action saves it with a draft status.

That workflow is available in the free plugin. Fully hands-off publishing without a human review step is possible, but we would not recommend it at scale for reasons this article covers in detail.

Every method for connecting ChatGPT to WordPress follows the same basic shape: a trigger fires, a prompt goes to the OpenAI API, text comes back, and a post action saves it. What separates a useful pipeline from a liability is what happens between the AI response and the publish button. Most guides skip that part entirely.

This article covers how to build that pipeline inside WordPress itself, what it actually costs to run, where the quality risks sit, and who should and should not let AI publish without review.

Browse the full Krom Automation feature list to see every trigger and action available before you build.

How the Basic Pipeline Works

The core workflow has three nodes on the canvas. A trigger fires on a schedule or an incoming event, an AI Generate Text action sends your prompt to the OpenAI API and returns the completed text, and a Create Post action saves that text as a WordPress post. You connect them on the visual drag-and-drop builder, set the post status to draft, and the workflow runs in the background via Action Scheduler so nothing touches page load times.

Krom Automation supports three AI providers in the free version. You bring your own API key and pay your provider directly. wpRigel never charges per AI call and never marks up tokens.

• 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

GPT-4o Mini costs roughly $0.15 per million input tokens and $0.60 per million output tokens at standard OpenAI pricing. A 1,000-word blog post uses approximately 1,300 to 1,500 tokens total.

That puts the per-post API cost well under one cent for most use cases. Running 100 posts a month through GPT-4o Mini costs less than $1 in API fees at that rate.

The Schedule trigger in Krom Automation Pro lets you fire the workflow on a recurring timetable, daily, weekly, or at a custom interval. The free plugin handles event-based triggers instead.

If you need the pipeline to run on its own clock rather than in response to a site event, that is a Pro feature. See the schedule trigger documentation for setup details.

Free vs Pro: What Do You Actually Need?

What you want to do	Free or Pro?	Notes
Generate text with AI and save as a draft post	Free	AI Generate Text + Create Post actions, both included free
Trigger the workflow when a form is submitted	Free	Works with WPForms, Gravity Forms, Fluent Forms via free triggers
Run the workflow on a daily or weekly schedule	Pro	Schedule trigger is Pro-only
Trigger from an external webhook, e.g. a Google Sheet or RSS	Pro	Incoming webhook receiver is Pro-only
Run AI content moderation before saving	Free	AI Content Moderation action is included free
Auto-tag the generated post	Free	AI Auto-Tag action is included free
Generate the entire workflow from a plain-English description	Pro	AI workflow generation is Pro-only

If your goal is a fully scheduled, recurring AI content pipeline, you need Pro. If you want to test the AI actions and get familiar with how the pipeline behaves, the free version gives you everything except the Schedule trigger and the webhook receiver.

Pro plans start at $69 a year for one site, or $199 as a one-time lifetime payment. Every plan includes all 25 integrations and every Pro feature.

The only difference between plans is the number of sites. See the full pricing breakdown before you decide.

The question is not whether AI can publish your posts. It is whether you want it to, without reading them first.

The Draft-First Workflow: Why It Matters

Every guide that covers ChatGPT and WordPress automation treats “generate and publish” as the goal. We think that is the wrong frame for any site where accuracy, brand voice or SEO quality matters. The right default is generate and draft, with a human in the loop before anything goes live.

Here is why that matters in practice:

• Factual errors: AI models hallucinate. A post about a plugin, a product or a news event can contain plausible-sounding figures that are simply wrong. A reader who acts on bad information is a trust problem you cannot undo with a correction.
• Brand voice drift: A prompt that works well 80 percent of the time produces outputs that are subtly off 20 percent of the time. At 10 posts a month, that is 2 posts a month that need a rewrite before anyone sees them. At 100 posts a month, it is 20.
• Duplicate content risk: If your prompt is too generic, the model will produce text that closely resembles other content it has generated for similar prompts. Google’s guidance on AI content focuses on helpfulness and originality, not on whether a human typed the words. Thin, generic output is the actual risk, not AI authorship itself.
• Prompt injection from external inputs: If your trigger receives content from a form or a webhook, a malicious user can craft input that changes your prompt’s behaviour. Review what goes into your AI action fields before automating at scale.

Setting the Create Post action to draft status costs you nothing in the automation itself. You still get the time saving on generation.

You add a 2 to 5 minute editorial pass before publishing. That is a reasonable trade at almost any volume.

For a step-by-step look at how Krom Automation’s conditions and branching work, including how to route a workflow based on the AI moderation result, see the conditions and branching documentation.

Building a Quality Control Layer Into the Workflow

Krom Automation includes three AI actions in the free version. Used together, they give you a lightweight editorial layer without any external tools.

• AI Generate Text: sends your prompt and any merge tag variables to the model and returns the completed text.
• AI Content Moderation: checks the output against categories like harmful content, off-brand language or policy violations. Returns a pass or fail signal you can branch on.
• AI Auto-Tag: reads the generated post and assigns relevant tags automatically, which matters for internal site search and taxonomy consistency.

A well-structured workflow uses all three in sequence. Generate the text, run it through moderation, and branch on the result. If it passes, save as a draft and notify the editor.

If it fails, log the failure and skip saving. You can read more about how triggers, actions and workflows connect before building this out.

Merge tags let you inject live data into your prompt. If the trigger is a form submission with a topic field, that topic value flows into the AI prompt automatically. See the merge tags documentation for the full variable reference.

A moderation step that catches 1 in 5 outputs is not overhead. It is the difference between a content pipeline and a liability.

Triggering the Workflow: Your Options

A workflow needs something to start it. Your choice of trigger shapes the whole pipeline.

Event-based triggers (free)

Any WordPress event can start a content generation workflow. A form submission is the most common: someone submits a topic request, the trigger fires, and the AI generates a draft on that topic.

Krom Automation integrates with Gravity Forms, WPForms, and Fluent Forms out of the box. A Post Published trigger can also fire a workflow that enriches or repurposes the post immediately after it goes live.

Schedule trigger (Pro)

The Schedule trigger runs a workflow at a fixed interval: hourly, daily, weekly, monthly, or a custom cadence. This is the right choice for a recurring content pipeline where you want posts generated on a timetable without manual input. The schedule trigger documentation covers all available options.

Incoming webhook (Pro)

The incoming webhook receiver gives each workflow a unique secret URL with HMAC-SHA256 signature support. Any external service that can send an HTTP request, a Google Sheet, an RSS aggregator, a content brief tool, can trigger the workflow. This is the integration point for more complex pipelines where topic input comes from outside WordPress.

The WP-Cron Timing Problem

Krom Automation runs background tasks through Action Scheduler, which itself depends on WordPress Cron. On a site with consistent traffic, WP-Cron fires reliably within a few minutes of the scheduled time. On a low-traffic site where hours can pass between visits, WP-Cron fires late, sometimes by hours.

If your content pipeline needs to run at a precise time, configure a real server cron job to trigger WP-Cron on a fixed schedule. Your hosting control panel or a simple server cron entry pointing at wp-cron.php solves this. It is a five-minute setup that makes every scheduled workflow on the site more reliable, not just content automation.

This limitation applies to all WordPress automation plugins, not just Krom Automation. Anyone who tells you scheduled WordPress automations fire at exact times on shared hosting without a real cron is glossing over how WP-Cron actually works.

Cost Comparison: Self-Hosted vs External Services

Approach	Year 1 cost (est.)	Year 2 cost (est.)	Per-task billing?	Data stays on your server?
Krom Automation free + OpenAI API	API cost only (~$1-$5/mo at 100 posts)	Same	No	Yes
Krom Automation Pro + OpenAI API	$69/yr + API cost	$69/yr + API cost	No	Yes
Zapier + ChatGPT (Professional plan)	~$240/yr for 750 tasks/mo, then overage	~$240/yr or more	Yes	No
Uncanny Automator + OpenAI	From $199/yr (1 site); AI plans from $300/yr	Same renewal	No	Yes

Zapier and Uncanny Automator figures are as of September 2026. Zapier uses task-based billing, meaning each step in a multi-action workflow counts as a separate task. A three-step content workflow uses 3 tasks per run, not 1.

The self-hosted approach keeps your prompts, your generated content and your execution logs inside your own database. Nothing passes through a third-party server except the OpenAI API call itself. For clients in regulated industries or with strict data handling policies, that matters.

For a broader look at when external automation services make sense and when they do not, see our article on automating WordPress without Zapier.

Zapier’s task-based billing means a three-step AI content workflow costs three times what the dashboard implies per run.

Testing Before You Let It Run

Krom Automation includes a workflow simulator for dry-run testing. It executes the workflow logic without firing real actions, so you can check that your prompt, branching conditions and post settings behave as expected before anything touches the live site. Use it every time you change a prompt or add a new branch.

The workflow simulator documentation explains how to interpret the output and catch configuration errors before they propagate into your content queue.

The execution log gives you a full per-step audit trail for every workflow run. If a post does not appear in drafts, the log tells you exactly which step failed and why, whether that was an API timeout, a moderation flag or a missing merge tag value. You can read about the full actions reference to understand what each action returns and how to use those return values in downstream steps.

Is Auto-Published AI Content Bad for SEO?

Google’s stated position is that automatically generated content is acceptable when it is helpful, original and produced primarily for people rather than for search engines. Thin content that exists only to fill a keyword gap is the problem. AI authorship is not the disqualifying factor.

In practice, the sites that get penalised for AI content are the ones running bulk generation with no editorial oversight. Posts that all share the same structure, the same phrasing patterns and the same generic conclusions are the signal, not the API call that created them.

A draft-first pipeline with a human review step, a specific prompt that matches your site’s voice, and an AI Auto-Tag action for taxonomy consistency produces content that is harder to distinguish from well-written human output. That is the baseline worth targeting. For more on how AI fits into a broader WordPress automation strategy, see our post on using AI to automate your WordPress site.

Also from wpRigel

Pollify is wpRigel’s poll, survey and quiz plugin. It is built natively for the Gutenberg block editor, so you create polls the same way you write a paragraph, no shortcodes, no separate configuration screen. It is worth knowing about if you run any kind of community or audience-facing site.

Commandify is a command palette for the WordPress admin. Press Cmd or Ctrl plus K to search everything, navigate instantly and run admin actions without clicking through menus. It is the only command palette plugin with real WooCommerce order, product and customer commands built in, which makes it genuinely useful on any store-backed site.

Our Verdict: Who Should Build This and Who Should Not

Build a ChatGPT-to-WordPress pipeline if you have a clear, repeatable content type, topic roundups, product descriptions, event summaries, and a prompt that reliably produces acceptable output. Set the Create Post action to draft status, build a moderation branch, and review before publishing. At 20 to 50 posts a month, that workflow saves 10 to 20 hours of generation time while keeping a human editor accountable for what goes live.

Do not build a fully hands-off publishing pipeline for any site where accuracy or brand voice is the product. News sites, professional service firms, SaaS documentation: all of these carry trust costs that a retraction or a hallucinated figure can set back significantly.

The automation saves you time. It does not read the post.

The free version of Krom Automation is enough to get started. Download it from the WordPress.org plugin directory, connect your OpenAI API key, and build the three-node draft workflow before you decide whether the Pro schedule trigger is worth adding. Most people find that the free version answers the core question, and upgrade when they want the pipeline to run on its own clock.

Compare all three Pro plans if you are ready to move to a scheduled, recurring pipeline.

Frequently Asked Questions

Does Krom Automation store my OpenAI API key securely?

Yes. API keys are stored in your own WordPress database, encrypted at rest.

They are never sent to wpRigel’s servers. The only external call is the one from your server directly to the OpenAI API.

Can I use a different AI model, not just OpenAI?

Yes. The free version supports OpenAI, Google Gemini and Groq.

You can configure a separate API key for each provider and switch between them per workflow. Groq’s Llama models are free-tier eligible and useful for testing prompts before running them against a paid model.

What happens if the AI API call fails mid-workflow?

Krom Automation logs the failure with a full per-step trace and sends a failure notification by email. It also retries automatically with configurable backoff. The post is not saved in a half-complete state because the Create Post action only runs after a successful AI Generate Text response.

Will this work on a shared hosting plan?

The plugin runs on any host that meets the requirements: WordPress 6.2 or higher, PHP 7.4 or higher, and MySQL 5.7 or MariaDB 10.2. Shared hosting works, but the WP-Cron timing issue described above applies. Configure a real server cron job if the workflow needs to fire at a predictable time rather than whenever the next site visit arrives.

Can I run this across multiple client sites without paying per site?

The free plugin is free on every site. If you need Pro features like the Schedule trigger or the incoming webhook receiver across multiple client sites, the Standard plan covers 5 site activations at $149 a year, and the Enterprise plan covers unlimited sites at $299 a year.

Both are lifetime-eligible as well. See the pricing page for the current rates.

Is there a way to preview the AI output before it saves as a draft?

Yes. The workflow simulator runs the full workflow in dry-run mode, showing you the AI output and every step result without saving anything to the database. Use it to tune your prompt until the output is consistently usable, then switch the workflow to live mode.

You can use AI to automate your WordPress site right now, for free, using Krom Automation. The free plugin includes three AI actions, supports OpenAI, Google Gemini, and Groq, and costs nothing beyond the API key you supply.

Pro adds AI workflow generation, where you describe an automation in plain English and get a working workflow in seconds. Most common use cases, including generating post summaries, moderating comments, and auto-tagging content, need only the free version.

Most WordPress automation articles give you a plugin list and stop there. This one works differently. We will show you which AI automations are worth building first, what each one actually saves you, and where the real limits are, including the WP-Cron timing issue that affects low-traffic sites.

The angle most coverage misses is that AI is a step inside a workflow, not a separate tool bolted on. When AI generation sits inside the same canvas as your triggers, conditions, delays, and email actions, you can build genuinely useful end-to-end automations rather than just calling an API and hoping something happens.

Browse the full feature list to see what triggers and actions are available before you build your first workflow.

What Does “AI Automation” Actually Mean in WordPress?

Most people asking this question want one of three things: content written automatically, responses sent without manual input, or data organized without anyone touching it. All three are possible inside WordPress without connecting to an external automation platform.

The practical approach is to treat AI as one action inside a larger workflow. A post publishes, that triggers the workflow, an AI action generates a summary, and a follow-up action posts it somewhere or updates a custom field. The AI call is one node on a canvas, not the whole system.

This matters because it keeps the logic in one place. You see the full chain, including what fires the AI call, what conditions gate it, and what happens after it returns. That is very different from stringing together separate plugins that do not know about each other.

Treating AI as a plugin to install misses the point. The value comes from placing AI inside a workflow that has a trigger, conditions, and a consequence.

Which AI Actions Come Free and What Do They Do?

Krom Automation includes three AI actions in the free plugin, with no paywall and no usage limits imposed by wpRigel. You pay your AI provider directly at their standard rates. The three actions are:

• AI Generate Text: Sends a prompt to your chosen model and injects the result into any downstream action field using merge tags. Use it to write post summaries, generate email body copy, create follow-up messages, or produce structured output from form submissions.
• AI Content Moderation: Passes text to the model and returns a judgment. Route comments, form entries, or user-generated content down a Yes path if clean and a No path if flagged, without any manual review unless you want it.
• AI Auto-Tag: Reads post content and suggests or applies tags automatically. A post that takes 30 seconds to tag manually, across 20 posts a week, is 10 minutes gone. Across a year that is over 8 hours of tagging.

All three actions work with the full actions reference, which lists every parameter and what each field accepts.

Which AI Model Should You Use?

Krom Automation supports three providers in the free version. You connect your own API key in the plugin settings and choose a model per action node. The supported models are:

• OpenAI: GPT-4o Mini (fast, cheap, good for tagging and moderation) and GPT-4o (stronger reasoning, better for longer generation tasks)
• Google Gemini: Gemini 2.0 Flash, Gemini 2.5 Flash Preview, and Gemini 2.5 Pro Preview
• Groq: Llama 3.3 70B and Llama 3.1 8B (fast inference, useful when response speed matters more than output length)

For most content generation tasks, GPT-4o Mini or Gemini 2.0 Flash keeps costs very low per call. For moderation where accuracy matters more than cost, GPT-4o or Gemini 2.5 Pro Preview is the better choice. You can use different models for different workflows, so a high-volume tagging workflow can run on a cheaper model while a customer-facing email workflow uses a stronger one.

Four AI Automations Worth Building First

Not all automations deliver equal value. Work through these in order.

The first two require only the free plugin and give you a working result within 20 minutes of setup. The third and fourth are slightly more involved but save more time per week at any meaningful publishing volume.

1. Auto-Tag New Posts on Publish

Trigger: Post Published. Action: AI Auto-Tag. That is the entire workflow for a basic version.

The AI reads the post content and applies tags, so editors never open the tags panel unless they want to override something. At 3 posts per day, that is roughly 90 tagging operations a month that take zero human time.

2. Moderate Comments Before They Go Live

Trigger: Comment Submitted. Action: AI Content Moderation. Add a conditional branch on the result.

The Yes path approves the comment automatically. The No path holds it for manual review or deletes it. This runs before WordPress’s own spam filter, so clean comments get published instantly and borderline ones never reach the queue unless a human should see them.

3. Generate a Post Summary and Update a Custom Field

Trigger: Post Published. Action: AI Generate Text, with a prompt asking for a two-sentence summary. Action: Update Post Field, writing the AI output into a custom field your theme or SEO plugin reads.

The summary appears in search previews, social cards, or wherever your site uses it, without anyone writing it. A developer billing at $75 an hour who spends 5 minutes per post on summaries costs you $6.25 per post. At 20 posts a month that is $125, every month.

4. Respond to a Contact Form Submission with an AI-Generated Reply

Connect a form trigger from Gravity Forms, Contact Form 7, or WPForms to an AI Generate Text action. Pass the form submission content as a merge tag inside the prompt. Use the AI output as the body of a Send Email action back to the submitter.

This is not a chatbot. It is a first-response email that arrives in under a minute, acknowledges the specific query, and sets expectations for a human reply.

A first-response email arriving in 45 seconds converts better than a thoughtful reply arriving in 4 hours. Speed is the variable most teams underestimate.

What Does Each AI Automation Actually Cost?

The table below shows realistic API cost ranges for common AI actions. These are estimates based on typical input and output lengths at standard provider rates, not guarantees. Actual cost depends on prompt length, model choice, and output volume.

Automation	Model	Approx. cost per call	Cost at 500 runs/month
Auto-tag a post	GPT-4o Mini	Under $0.01	Under $5
Moderate a comment	GPT-4o Mini	Under $0.01	Under $5
Generate a 2-sentence summary	GPT-4o	$0.01 to $0.03	$5 to $15
Generate a full email reply	GPT-4o	$0.02 to $0.05	$10 to $25
Any action above	Gemini 2.0 Flash	Lower than GPT-4o Mini	Often under $2

wpRigel charges nothing per execution and nothing per AI call. The only cost above the plugin price is what you pay your provider directly.

How Does Pro Differ for AI Workflows?

Pro adds one feature that changes how you build workflows: AI workflow generation. You describe an automation in plain English, for example “when a new user registers, wait 24 hours, then send them an email with a personalized getting-started guide based on their registration details”, and Krom Automation builds the workflow on the canvas. You review it, adjust anything, and activate it.

Pro also adds 60 or more additional actions and 80 or more additional triggers, which gives AI generation more to work with. A prompt that would produce a two-node workflow on the free version can produce a six-node workflow with branching and a delay on Pro because more building blocks exist. See the free versus Pro comparison for the complete breakdown.

Pro plans start at $69 a year for one site, or $199 as a one-time lifetime payment. Every plan includes every Pro feature, including AI workflow generation, the visual email builder, the schedule trigger, and all 25 integrations. See current pricing and plan limits.

Free vs. Pro: Which Do You Need for AI Automation?

Use case	Free	Pro
Auto-tag posts on publish	Yes	Yes
Moderate comments with AI	Yes	Yes
Generate post summaries into a custom field	Yes	Yes
AI-generated first-response email from a form	Yes (with form trigger)	Yes (with more form options)
AI workflow generation from a text prompt	No	Yes
Schedule trigger for recurring AI tasks	No	Yes
Incoming webhook to trigger AI from external tools	No	Yes
Visual email builder for AI-generated content	No	Yes

How to Set Up Your First AI Workflow

Install Krom Automation from the WordPress.org plugin directory, then activate it. The setup takes under 5 minutes for a basic workflow. The steps are:

1. Go to Krom Automation in your WordPress admin and open the workflow builder.
2. Add a trigger node. For auto-tagging, choose Post Published.
3. Add an AI action node. Choose AI Auto-Tag.
4. Open the action settings, select your AI provider, and enter your API key.
5. Choose a model. GPT-4o Mini or Gemini 2.0 Flash is fine for tagging.
6. Save and activate the workflow.
7. Publish a test post and check the tags it generates.

The workflow simulator lets you run a dry test before activating, with zero side effects. No posts are published, no emails are sent, no AI calls are made to your provider. Use it to confirm the workflow structure is correct before you go live.

The merge tags documentation explains how to pass dynamic data from the trigger into your AI prompt, for example injecting the post title and category into the tagging prompt so the model has context.

What Are the Real Limits You Should Know About?

Every page selling automation software glosses over the constraints. Here are the ones that actually matter for AI workflows in WordPress.

• WP-Cron timing on low-traffic sites: Krom Automation uses Action Scheduler for background execution, so nothing runs during page loads. But Action Scheduler depends on WP-Cron to fire its queue. On a site that receives fewer than a few visits per hour, delayed actions may run late. If timing precision matters, configure a real server cron to trigger WP-Cron on a schedule rather than relying on visitor traffic.
• AI calls require your own API key: wpRigel never holds or proxies your AI provider credentials. You create the key directly with OpenAI, Google, or Groq and enter it in the plugin. If a key expires or hits a rate limit, AI actions in that workflow will fail until you update it.
• AI output is not guaranteed to be correct: Moderation works well for obviously problematic content and obviously clean content. The gray area in the middle still needs a human review path. Build your moderation workflow with a No path that holds borderline content for manual review, not one that deletes it automatically.
• Token limits on long posts: Very long posts sent in full to an AI model for summarization can exceed the model’s context window. For posts over 5,000 words, either truncate the input in your prompt or use a model with a larger context window such as Gemini 2.5 Pro Preview.

No automation review tells you about WP-Cron timing on quiet sites because it is not a sales point. It is the thing you discover at 2am when a workflow runs four hours late.

How Does This Compare to Using Zapier or an External Tool?

Zapier can connect WordPress to an AI provider, but you are building the bridge yourself using a third-party platform. Your workflow data, execution logs, and API credentials live on Zapier’s servers rather than in your own database. At Zapier’s Professional plan, that costs around $240 per year billed annually for 750 tasks a month, as of September 2026, with additional charges if you exceed the task limit.

Krom Automation keeps everything inside WordPress. Execution logs, credentials, and workflow definitions are stored in your site’s database in 9 custom tables.

There are no per-task or per-execution fees at any tier. For AI-specific tasks, Zapier does not include native AI providers at the same depth, and the cost-per-run model makes high-volume automations expensive quickly.

If you are evaluating alternatives, our post on automating WordPress without Zapier covers the trade-offs in detail, and the Zapier alternative comparison includes pricing scenarios.

Extending AI Workflows With Integrations

AI actions become more useful when they connect to the tools your site already uses. A few combinations worth knowing about:

• AI moderation to FluentCRM: Flag a user after a moderation failure and update their contact record automatically, using the FluentCRM integration.
• AI summary to Slack: Generate a post summary with AI and post it to a Slack channel when the post publishes, using the messaging integrations.
• AI tagging with Google Sheets logging: Write the tags applied to a post into a Google Sheet for audit purposes, using the Google Sheets integration.
• Form submission to AI to Mailchimp: Take a form entry, pass it to AI for classification, and subscribe the contact to the right Mailchimp list based on the result, using the Mailchimp integration.

These combinations all use Pro integrations. The free plugin handles the AI actions. Pro handles the downstream connections to external services.

Also from wpRigel

Pollify is wpRigel’s poll, survey, and quiz plugin for WordPress. Polls are built as native Gutenberg blocks inside the editor, so there are no shortcodes to paste and no separate interface to configure. The free version is available on WordPress.org, and Pro adds NPS voting, CSV and PDF export, scheduling, and enriched analytics.

Commandify is a command palette for the WordPress admin. Press Cmd or Ctrl plus K from anywhere in the admin, type what you want, and go there, whether that is a post, a user, a setting, or a WooCommerce order. It is the only WordPress command palette with genuine WooCommerce depth, covering orders, products, variations, and customers as first-class commands rather than an afterthought.

Verdict: Who Should Build AI Workflows in WordPress Now?

If you publish content regularly and you are not auto-tagging or moderating with AI, you are doing manual work that a free plugin can handle. The free version of Krom Automation covers the three highest-value AI actions for content sites, and the setup time is under 30 minutes for all three workflows combined.

Pro is worth it if you want AI to generate the workflows themselves, if you need the schedule trigger for recurring AI tasks, or if your site connects to services like FluentCRM, Mailchimp, or Slack where the full integration list matters. At $69 a year or $199 as a lifetime payment for one site, the breakeven against 3 to 4 hours of saved manual work is reached in the first month for most active sites.

If your site publishes fewer than 4 posts a month and receives minimal form submissions, the time saved may not justify even the setup time. Start with the free plugin, build one workflow, and measure. If the analytics dashboard shows 50 or more executions in the first month, the automations are doing real work and Pro becomes an obvious call.

Download the free plugin from the WordPress.org plugin directory and build your first AI workflow today. When you are ready to compare plans, see full pricing and plan details.

Frequently Asked Questions

Do I need a paid Krom Automation plan to use AI actions?

No. All three AI actions, AI Generate Text, AI Content Moderation, and AI Auto-Tag, are included in the free plugin with no usage caps from wpRigel.

You pay only for the API calls your AI provider charges. Pro adds AI workflow generation, where you describe an automation in plain English and get a built workflow on the canvas.

Which AI provider is cheapest for WordPress automation?

For high-volume tasks like tagging and moderation, Gemini 2.0 Flash and GPT-4o Mini are both very cheap per call, often under $0.01 for a short task. Groq’s Llama models are also fast and low-cost. The right choice depends on whether you already have an API key with a provider and how much output quality matters for your specific task.

Will AI workflows slow down my WordPress site?

No. Krom Automation runs all workflow executions in the background using Action Scheduler, which is the same queue system WooCommerce uses.

No AI call runs during a page load. The only timing caveat is WP-Cron on very low-traffic sites, where delays may fire late if the cron queue is not triggered by real traffic.

Can I use AI to automatically publish full blog posts?

You can use AI Generate Text to create content and the Create Post action to publish it, either immediately or after a delay. However, publishing AI-written content without human review is a quality and editorial risk. A more practical setup is to create the post as a draft with AI-generated content, then publish it manually after review.

How is this different from using an AI writing plugin?

An AI writing plugin lives in the editor and helps you write. Krom Automation’s AI actions run automatically in response to events, without anyone opening the editor.

The distinction is between a tool that assists a human and a workflow that runs without one. Both have a place, and they are not competing for the same job.

Does Krom Automation store my AI API keys securely?

Your API keys are stored in your own WordPress database, in the same environment as every other credential on your site. wpRigel never sees or proxies your keys. Security depends on your hosting environment and your site’s overall access controls, which is the same answer as for any sensitive credential stored in a self-hosted WordPress installation.

Yes, there is a cheaper alternative to Uncanny Automator: Krom Automation. The free version includes 16 triggers, 21 actions, and a visual drag-and-drop workflow builder with no run limits and no trial period.

Pro plans start at $69 a year for one site, or $199 as a one-time lifetime payment, compared to Uncanny Automator’s automation plans starting at $199 per year for one site as of September 2026. No lifetime option exists on Uncanny Automator’s side.

This article compares both tools on pricing model, builder experience, AI features, testing, and the integrations that matter most to WordPress sites running WooCommerce, LearnDash, MemberPress or similar plugins. Every figure is sourced and dated. Where we have gaps, we say so rather than guess.

We make Krom Automation, so this is not a neutral review. What it is: an honest breakdown of where Krom Automation is the right call, where it is not, and what the real cost difference looks like over time.

Browse the full Krom Automation feature list or keep reading for the comparison.

How Do the Prices Actually Compare?

Uncanny Automator charges per year with no lifetime option. Krom Automation offers both annual and lifetime pricing, and the gap between the two is significant once you factor in year two and beyond.

Scenario	Krom Automation	Uncanny Automator (as of Sept 2026)
Year 1, 1 site	$69/year (current launch price)	$199/year
Year 2, 1 site	$69/year (renews same rate)	$199/year
Lifetime, 1 site	$199 one-time payment	Not available
5 sites, year 1	$149/year	Higher-tier plan required
Unlimited sites, lifetime	$699 one-time payment	Not available
Free tier	Yes, no run caps, no trial	Limited free version

At the current launch price, Krom Automation Pro costs less in year one than Uncanny Automator’s entry plan. Over three years on a single site, Uncanny Automator costs $597 at $199 per year.

The Krom Automation lifetime plan costs $199 once. That is a $398 difference by year three, with no further payments.

Uncanny Automator also offers plans that include AI features starting at $300 per year as of September 2026. Krom Automation includes AI actions in the free version.

You supply your own API key and pay your provider directly at standard rates. We do not mark up tokens or put AI behind a paywall at any tier.

A lifetime plan that costs less than one year of a competitor’s entry plan is not a discount. It is a different pricing philosophy entirely.

What Does the Free Version Actually Give You?

The Krom Automation free version is a real automation plugin, not a feature-locked preview. You can download it free from the WordPress.org plugin directory and run production workflows with no expiry date and no execution caps.

The free version includes:

• 16 triggers covering user events (registration, login, role changes), post lifecycle, comments, media uploads, and WooCommerce orders
• 21 actions including sending email, creating or updating posts and users, making HTTP requests (GET, POST, PUT, PATCH, DELETE), and three AI actions
• 20 ready-made workflow templates across six categories, plus a blank canvas option
• Visual drag-and-drop builder built on ReactFlow with auto layout, conditional Yes/No branching, and delay scheduling in minutes, hours, days or weeks
• Workflow simulator for dry-run testing with zero side effects
• Execution logs with a full per-step audit trail, analytics dashboard, and CSV export
• AI actions including text generation, content moderation, and auto-tagging, using your own OpenAI, Google Gemini, or Groq API key

The free vs Pro comparison spells out exactly what each tier unlocks, but for most single-site WordPress setups the free version handles the common automation patterns without any payment.

How Does the Visual Builder Compare?

Krom Automation uses a canvas-based workflow builder where triggers and actions are nodes connected by lines. You can see the full shape of a workflow at a glance, including where branches split into Yes and No paths and where delays sit in the sequence.

List-based rule editors are the more common pattern in WordPress automation plugins. They work for simple chains, but when a workflow branches into multiple paths or includes several delays and conditions, a list becomes hard to read and harder to debug. The visual workflow builder documentation covers navigation, canvas controls, and how to arrange nodes for complex flows.

The workflow simulator lets you run any workflow in dry-run mode before activating it. It processes the full logic and shows you exactly what would have happened at each step, without sending a single email or creating any real data. This matters because testing automation on a live site without a dry-run mode means using real users as test subjects.

A workflow that looks correct as a list can still branch the wrong way. Seeing the shape of the logic on a canvas is what catches that before it runs on real data.

Which Integrations Are Covered?

Krom Automation Pro includes 25 integrations spanning forms, e-commerce, CRM, email marketing, LMS, membership, messaging, social media, data storage, productivity, and affiliate tools. Every integration is included in every Pro plan. There is no per-integration add-on pricing.

For the integrations most commonly paired with Uncanny Automator, here is what Krom Automation covers in Pro:

• LMS: LearnDash (enrollment, completion, quiz, and group triggers) and TutorLMS
• Membership: MemberPress (signup, subscription, expiry, and payment triggers)
• E-commerce: WooCommerce built into the free tier, plus WooCommerce Subscriptions and Easy Digital Downloads in Pro
• Forms: Gravity Forms, WPForms, Fluent Forms, Contact Form 7, Elementor Forms, and Ninja Forms
• Email marketing: Mailchimp, FluentCRM, ActiveCampaign, ConvertKit, MailerLite, and MailPoet
• Messaging: Slack, Discord, Twilio, and Telegram
• Data and productivity: Google Sheets and Google Calendar
• Social: Facebook, Twitter/X, and LinkedIn

If your stack is built around tools not on that list, check the Krom Automation roadmap before committing to a plan. Uncanny Automator has been in market longer and has a wider integration list at this point. That is a real difference worth weighing.

What About AI Automation?

Both tools include AI features, but the access model differs. Krom Automation includes three AI actions in the free version: AI Generate Text, AI Content Moderation, and AI Auto-Tag. You connect your own API key from OpenAI, Google Gemini, or Groq.

You pay your provider at their standard rates. We charge nothing on top.

Uncanny Automator’s newer plans that include AI features start at $300 per year as of September 2026. Whether the AI features included in that pricing match what you need depends on your specific workflows, but the access model means paying more per year to use AI rather than supplying your own key.

Pro adds AI workflow generation: describe an automation in plain English and get a working workflow on the canvas in seconds. That is useful when you know what you want but are not yet familiar with the builder.

What Does Krom Automation Not Do Well?

Honest limitations matter here because this is the section that earns trust and the one most articles skip.

• Integration count: Uncanny Automator has been in market longer and covers more third-party integrations. If your stack relies on a plugin not yet in Krom Automation’s 25 Pro integrations, that is a blocker until the integration ships.
• WP-Cron timing: Delays in Krom Automation depend on WordPress Cron. On very low-traffic sites where no visitor arrives for several hours, WP-Cron fires late. This is a WordPress-wide limitation, not unique to Krom Automation, but it means a one-hour delay on a quiet staging site may actually run after 90 minutes. Configuring a real server cron fixes it entirely.
• External-to-external automation: Krom Automation is WordPress-native. If you need to move data between two external services with no WordPress involvement, a dedicated iPaaS tool is the right fit. Our guide on automating WordPress without Zapier covers where that boundary sits.
• Migration effort: If you have dozens of existing Uncanny Automator workflows, rebuilding them on a new canvas takes time. Krom Automation supports workflow import and export as JSON, which helps for portability, but there is no automated import from Uncanny Automator’s format.

A plugin that cannot tell you what it does not do is not being transparent. It is selling. Know the gaps before you migrate 40 workflows.

Who Should Switch and Who Should Not?

Use this table to decide which situation applies to your site before spending time on a migration.

Your situation	Better fit	Why
Managing 5 or more client sites with recurring annual costs	Krom Automation Pro	$149/year for 5 sites vs $199+/year for one site on Uncanny Automator
Want to eliminate the renewal entirely	Krom Automation lifetime	$199 once for 1 site, $399 for 5 sites, no further payments
Need AI actions without a higher-tier plan	Krom Automation free	AI actions included free, bring your own API key
Rely on a plugin not in Krom’s 25 integrations	Uncanny Automator or wait for roadmap	Integration gap is a real blocker; check the roadmap first
Have 50+ existing Uncanny Automator workflows	Evaluate carefully	Rebuild time is a real cost; weigh it against the annual saving
Need to automate between two external services with no WordPress involvement	Neither; use a dedicated iPaaS tool	Both plugins are WordPress-native
Running a new site or starting fresh	Krom Automation free	No cost, no run caps, 16 triggers and 21 actions from day one

How Many Workflows Can You Build for Free?

Krom Automation’s free version has no workflow count limit, no monthly execution cap, and no feature that disappears after a trial period. You can build as many workflows as your site needs using any combination of the 16 free triggers and 21 free actions.

The step-by-step workflow builder guide walks through the full process from selecting a trigger to testing and activating. For a practical starting point, the welcome email automation walkthrough is the fastest way to see the builder in action on a real use case.

Twenty ready-made templates cover the most common automation patterns. You can also import and export workflows as JSON, which is useful when replicating a setup across client sites or sharing a workflow with a team. See the workflow settings documentation for how run-once enforcement, pausing, and import/export work in practice.

How Does This Compare to Zapier for WordPress?

Zapier is sometimes mentioned in the same breath as Uncanny Automator, but the tools solve different problems. Zapier connects external services. Krom Automation connects WordPress events to actions, either inside WordPress or out via HTTP requests and its 25 Pro integrations.

Zapier’s Professional plan costs around $240 per year billed annually for 750 tasks per month as of September 2026, with task-based billing that adds overage charges when you exceed the cap. Krom Automation has no per-task or per-execution billing at any tier. Our comparison of Zapier alternatives for WordPress covers this in more detail if you are evaluating both.

Also from wpRigel

Pollify is our Gutenberg-native polls, surveys, and quizzes plugin. Polls are built directly inside the block editor as native blocks, so there are no shortcodes to paste and no separate interface to switch between. If you run a membership site or course platform and want to gather structured feedback from members, it fits the same WordPress-first philosophy as Krom Automation.

Commandify is a command palette for the WordPress admin. Press Cmd or Ctrl plus K to jump anywhere, search everything, and run admin actions without clicking through menus. It is the only WordPress command palette with real WooCommerce order, product, and customer commands built in, which makes it genuinely useful for store operators rather than just a navigation shortcut.

Our Verdict

If you are currently paying $199 or more per year for Uncanny Automator and your integrations are covered by Krom Automation’s 25 Pro integrations, the switch saves money from year one and eliminates renewal cost entirely on the lifetime plan. The visual builder and the workflow simulator are better tools for building and testing complex flows than the list-based interfaces most competing plugins use.

If you have a large library of existing Uncanny Automator workflows, factor in rebuild time before deciding. The annual saving is real, but so is the cost of rebuilding 30 workflows on a new canvas. For new sites or sites with fewer than 10 automation workflows, starting with the free Krom Automation plugin costs nothing and gives you a complete picture of the builder before any payment decision.

Check the Krom Automation pricing page for current plan details, including the active launch pricing on annual and lifetime options.

Frequently Asked Questions

Is Krom Automation actually free, or is the free version limited to a trial?

The free version is free forever. There is no trial period, no execution cap, and no feature that expires.

You get 16 triggers, 21 actions, and the full visual builder at no cost. Pro unlocks 80+ additional triggers, 60+ additional actions, and 25 integrations.

Does Krom Automation work with LearnDash and MemberPress?

Yes, both are Pro integrations. The LearnDash integration covers enrollment, course completion, quiz results, and group triggers. The MemberPress integration covers signup, subscription renewal, expiry, and payment events.

What happens if a workflow fails? Will I know about it?

Yes. Krom Automation sends failure notifications by email and retries automatically with configurable backoff.

Every execution is logged with a full per-step audit trail, so you can see exactly which step failed and why. Our post on silent automation failures in WordPress explains why per-step logging matters more than a simple pass/fail status.

Can I connect Krom Automation to external services, not just WordPress plugins?

Yes, via the HTTP Request action in the free version, which supports GET, POST, PUT, PATCH, and DELETE with JSON response parsing. Pro also adds an incoming webhook receiver with HMAC-SHA256 signature support, so external services can trigger WordPress workflows as well as receive data from them.

Does the lifetime plan include future updates and new integrations?

Yes. Lifetime plans include updates for life, which means new integrations and features added to Pro are included as they ship, with no additional payment.

Is there a money-back guarantee?

All Pro plans include a 14-day money-back guarantee. If Krom Automation does not fit your site after you have had a chance to test it properly, you can request a full refund within that window.

Yes, you can automate WordPress without Zapier. Krom Automation is a self-hosted WordPress plugin that connects site events to automated responses on a visual drag-and-drop canvas.

The free version includes 16 triggers, 21 actions, and 20 ready-made templates. Most common Zaps, form submissions to email lists, new users to a CRM, orders triggering custom emails, can be rebuilt inside WordPress with zero monthly fees and no per-task charges.

The case for replacing Zapier with a native plugin comes down to three things: cost, data control, and fit. Zapier’s Professional plan runs around $240 a year for just 750 tasks a month, and every automation that touches an external service eats from that task budget. A self-hosted plugin runs inside your own server, logs everything in your own database, and has no concept of a task limit.

That said, Zapier does something a WordPress plugin cannot: connect two external services that have nothing to do with WordPress. If you need Typeform to talk to Airtable, you need Zapier or a cloud equivalent. This article covers what you can fully replace, what you cannot, and how to migrate the workflows that matter most.

Browse the full feature list for Krom Automation to see every trigger, action, and integration before reading further.

What Does Zapier Actually Do for WordPress Sites?

Most WordPress sites use Zapier for a surprisingly short list of tasks. Understanding that list makes the replacement decision straightforward.

• Form submission to email list: Gravity Forms or WPForms fires a Zap that adds the contact to Mailchimp, ConvertKit, or ActiveCampaign.
• New WooCommerce order to a spreadsheet or CRM: an order triggers a row in Google Sheets or a contact record in HubSpot.
• User registration to a welcome email sequence: a new WordPress user triggers an email in an external platform.
• Slack notification on a specific event: a post published, an order placed, or a membership activated sends a message to a channel.
• Webhook from an external service into WordPress: a payment processor or SaaS tool sends a webhook that creates or updates something inside WordPress.

Every item on that list is a WordPress event connecting to something else. That is exactly what a native automation plugin handles, without routing data through a cloud intermediary.

Three Common Zaps Rebuilt Inside WordPress

The following examples use Krom Automation’s trigger-and-action model. Each maps directly to a real Zapier workflow pattern.

Zap 1: Gravity Forms Submission Adds a Subscriber to Mailchimp

In Zapier this costs at least 2 tasks per submission: one to receive the form data, one to send it to Mailchimp. At 500 submissions a month, that is 1,000 tasks before your other automations run.

Inside Krom Automation, the Gravity Forms integration fires a trigger the moment a form is submitted. A Mailchimp action then subscribes the contact, maps the fields using merge tags, and optionally adds a tag based on which form was submitted. No task count, no overage charge, no data leaving your server to reach a middleman before reaching Mailchimp.

The same pattern works with WPForms via the WPForms integration, Contact Form 7 via the Contact Form 7 integration, and Fluent Forms via the FluentForms integration.

Zap 2: WooCommerce Order Completed Adds a Row to Google Sheets

This is one of the most common WooCommerce Zaps. An order completes, Zapier fires, a row appears in a tracking spreadsheet.

The Zapier Professional plan costs roughly $240 a year for 750 tasks monthly. A store processing 300 orders a month uses 300 tasks on this single Zap alone, leaving 450 for everything else.

Krom Automation’s Google Sheets integration maps WooCommerce order data directly to spreadsheet columns the moment the order status changes. This is a Pro feature, and Pro starts at $69 a year for one site (at the time of writing, launch pricing applies). At a store doing 300 orders a month, the plugin pays for itself by month one compared to a Zapier plan that would need upgrading to handle the volume.

Zap 3: New WordPress User Triggers a Slack Notification

A team wants to know when someone registers, especially on a membership or course site. In Zapier, this is a two-step Zap: WordPress trigger, Slack action. Two tasks per event, every time.

Krom Automation’s User Registered trigger is free. The Slack messaging integration is a Pro action, and it supports dynamic merge tags so the message includes the user’s name, email, and role. You can add a conditional branch so notifications only fire for specific user roles, keeping noise low without building a second workflow.

A task limit is not a pricing tier. It is a ceiling that punishes you for growing.

What Still Needs an External Tool

Being honest about limits is more useful than overselling. Krom Automation is WordPress-native, which is its strength and its boundary.

You still need Zapier, Make, or n8n for:

• Service-to-service automation with no WordPress touch point: Typeform to Airtable, Calendly to HubSpot, Stripe to a Google Sheet, where WordPress is not involved at any step.
• Integrations not yet in the Pro library: Krom Automation has 25 integrations. Zapier has thousands. If you need a niche SaaS tool that is not on the Pro list, you need an external tool or a custom HTTP Request action.
• Real-time data transformations across multiple external APIs: complex multi-step data manipulation that never touches a WordPress object is better handled in a cloud automation tool built for that purpose.

The HTTP Request action in the free version covers a surprising amount of this gap. It supports GET, POST, PUT, PATCH, and DELETE with JSON response parsing, so any service with a documented API can receive data from a WordPress event even without a dedicated integration. That covers many “I just need to hit an endpoint” situations without upgrading to Pro.

How to Migrate from Zapier: A Practical Starting Point

No existing guide walks through the actual migration, so here is the practical version. The principle is: audit before you cancel.

Step 1: List every active Zap and its monthly task volume

Zapier’s dashboard shows task usage per Zap. Export or note the list.

Categorise each one as WordPress-to-external, external-to-WordPress, or external-to-external. The third category stays with Zapier for now.

Step 2: Map the first two categories to Krom Automation triggers and actions

Use the free triggers reference and free actions reference to confirm coverage. If a Zap uses a trigger and action both covered in the free version, it migrates at no cost.

Step 3: Build and test one workflow at a time

Use the workflow simulator to run a dry test with no side effects before activating. Confirm the data maps correctly using merge tags. Run the live version in parallel with the Zapier Zap for 48 to 72 hours, then deactivate the Zap.

Step 4: Track what remains

After migrating the WordPress-touch workflows, reassess your Zapier plan. Many sites find they can drop to a free or Starter Zapier tier, or cancel entirely, keeping only the external-to-external automations that genuinely require a cloud platform.

Most sites use Zapier for five workflows. Two of them touch WordPress. Those two are the ones worth migrating first.

Free vs. Pro: Which Do You Need to Replace Zapier?

The free plugin handles a meaningful share of common Zaps. The table below shows which tier covers which workflow type.

Workflow type	Free covers it	Pro required
New user registration to welcome email	Yes	No
Post published to custom notification email	Yes	No
WooCommerce order to HTTP endpoint	Yes (HTTP Request action)	No
Form submission to Mailchimp	No (Mailchimp is a Pro integration)	Yes
WooCommerce order to Google Sheets	No	Yes
New user to Slack notification	No (Slack is a Pro action)	Yes
Schedule-triggered recurring email	No (Schedule trigger is Pro)	Yes
Incoming webhook from external service	No (webhook receiver is Pro)	Yes
AI-generated content on post publish	Yes (AI actions are free)	No

The free plugin is a genuine starting point, not a crippled trial. For teams replacing Zapier on integrations with named platforms like Mailchimp, FluentCRM, ActiveCampaign, ConvertKit, or Google Sheets, Pro is the honest answer.

For a complete side-by-side breakdown, see the free vs. Pro feature comparison.

What Does Krom Automation Cost Compared to Zapier?

Cost is usually the reason someone searches for a Zapier alternative in the first place. The comparison below uses Zapier’s Professional plan pricing as of September 2026.

Scenario	Zapier Professional	Krom Automation Pro
1 site, year 1	~$240/year (750 tasks/month)	$69/year (launch pricing)
1 site, year 2 and beyond	~$240/year, same limit	$69/year, no task limits
5 client sites, year 1	~$240/year (one shared task pool)	$149/year, 5 site activations
Unlimited sites, lifetime	No lifetime plan available	$699 one-time (launch pricing)
Task or execution limits	750 tasks/month, overage charged	None at any tier

Krom Automation Pro pricing is launch pricing at the time of writing. Check the current pricing page for the exact figure before purchasing. All Pro plans include a 14-day money-back guarantee, and lifetime plans include updates for life.

For a broader comparison of how Krom Automation stacks up against other WordPress-native tools and Zapier, see our Zapier alternative for WordPress roundup and the full Zapier pricing breakdown.

What Does “Self-Hosted” Actually Mean for Your Workflows?

Self-hosted automation means execution logs, API credentials, and workflow data sit inside your WordPress database, not on a vendor’s servers. That matters for three reasons.

• Privacy and compliance: user data processed by a Zap passes through Zapier’s infrastructure. A GDPR or HIPAA-adjacent site may have obligations that make cloud automation complicated. Self-hosted means the data never leaves the server.
• No vendor lock-in: Zapier changes pricing, changes plan limits, or goes down, and your automations stop. Krom Automation runs on your server. The only dependency is your WordPress install.
• Full execution history: every workflow run is logged step by step in your own database. The analytics dashboard shows success rate, failure count, and an execution trend chart. For a deeper look at a failing workflow, the per-step audit trail shows exactly where it broke and what data was present at that moment.

If your automation vendor has an outage, your site’s workflows should not care.

Honest Limitations Worth Knowing

Krom Automation uses WordPress Cron and Action Scheduler for background execution. On very low-traffic sites, WP-Cron fires only when a page is visited. A delay-scheduled action set to run at 3am will fire the next time someone visits the site after that, not at exactly 3am.

The fix is a real server cron job calling wp-cron.php on a schedule. Most managed WordPress hosts either do this by default or make it a one-setting toggle.

On a high-traffic site it is not a practical issue. On a site getting ten visits a day it is worth addressing before building time-sensitive workflows.

AI actions in the free version require your own API key from OpenAI, Google Gemini, or Groq. wpRigel never charges per AI call and never marks up tokens. You pay your provider directly at their standard rates, which is cheaper than a bundled “AI credits” model, but it does mean one additional account to manage.

Also from wpRigel

Pollify is a Gutenberg-native poll, survey, and quiz plugin. Polls are built as real blocks inside the editor, so there are no shortcodes to paste and no separate admin interface to learn. It is the fastest way to add interactive voting to a WordPress post or page.

Commandify is a command palette for the WordPress admin. Press Cmd or Ctrl plus K to search everything and run admin actions without clicking through menus. It is the only command palette plugin with real WooCommerce order, product, and customer commands built in.

Our Verdict

If the majority of your Zapier usage involves WordPress events on either end, Krom Automation replaces it cleanly, costs less in year one, and costs nothing extra as volume grows. The free version is the right starting point for anyone not yet ready to commit. Install it, build the two or three workflows you rely on most, and see how far it gets you before deciding whether Pro is worth the upgrade.

If your Zapier usage is mostly external-to-external, connecting two SaaS tools with no WordPress involvement, you need Zapier or a cloud equivalent. A WordPress-native plugin cannot replace that by design.

For agencies managing automations across multiple client sites, the Standard plan at $149 a year for 5 activations and the Enterprise lifetime plan at $699 for unlimited sites are the two tiers worth evaluating. The WordPress automation across multiple client sites post covers that decision in more detail.

Download the free plugin from the WordPress.org plugin directory and build your first workflow in under ten minutes. No account required, no trial expiry, no feature locked away.

See Krom Automation Pro pricing and compare all three plans.

Frequently Asked Questions

Does Krom Automation work without any paid plan?

Yes. The free version includes 16 triggers, 21 actions, 20 workflow templates, AI actions, conditional branching, delay scheduling, a workflow simulator, execution logging, and a full analytics dashboard.

There is no trial period and no run cap. Pro adds 80+ more triggers, 60+ more actions, and 25 named integrations including Mailchimp, Google Sheets, Slack, and FluentCRM.

Can I receive webhooks from external services in WordPress without Zapier?

Yes, with Krom Automation Pro. The incoming webhook receiver gives each workflow a unique secret URL with HMAC-SHA256 signature verification and 9 security layers. Any external service that can POST JSON can trigger a workflow directly inside WordPress, no cloud middleman needed.

What happens to my Zapier workflows during the migration?

They keep running. The recommended approach is to build and test the Krom Automation equivalent using the workflow simulator, then run both in parallel for 48 to 72 hours before deactivating the Zap. There is no forced cutover, and you can migrate one workflow at a time rather than switching everything at once.

Does Krom Automation integrate with my email marketing tool?

Pro includes integrations for Mailchimp, ConvertKit, MailerLite, MailPoet, and ActiveCampaign. For a self-hosted CRM option, the FluentCRM integration handles contacts, tags, and lists entirely inside WordPress. The Mailchimp integration docs cover the subscribe, tag, and sync options in detail.

How do I run workflows on a schedule without Zapier?

The Pro schedule trigger supports hourly, daily, weekly, monthly, custom interval, and one-time execution. Workflows run via Action Scheduler in the background, so they do not affect page load time. On low-traffic sites, pairing Action Scheduler with a real server cron ensures timing accuracy.

Is there a Zapier alternative comparison I can read before deciding?

Yes. Our best WordPress automation plugin guide covers the main options with pricing as of 2026, including how Uncanny Automator and AutomatorWP compare on features and cost. If you are evaluating specifically on price, the Uncanny Automator pricing breakdown is a useful reference point alongside Krom Automation’s own pricing page.

The best Zapier alternative for WordPress is Krom Automation, a visual workflow plugin that runs entirely inside your WordPress install. The free version includes 16 triggers, 21 actions, and AI automation at no cost. Pro starts at $69 a year with no per-task fees and no execution caps.

If your automation touches WordPress on at least one end, Krom Automation replaces Zapier outright. If you need to connect two external services that have nothing to do with WordPress, you still need a cloud tool.

Zapier is a capable product. The problem is its cost model.

At the time of writing, Zapier’s Professional plan runs around $240 a year for 750 tasks a month, and every automation counts against that cap whether it fires once or a thousand times. A busy WooCommerce store, a membership site with daily enrollments, or an agency running flows across client sites can burn through that ceiling fast.

Krom Automation takes the opposite approach. Workflows run on your server, log every execution in your own database, and charge a flat annual or lifetime fee regardless of how many times they fire. There is no task meter, no overage bill, and no credentials sent to a third-party cloud.

Browse the full Krom Automation feature list or keep reading for the full comparison.

What Makes a WordPress-Native Automation Different from Zapier?

Zapier sits outside WordPress. It polls for events, waits for a webhook, then calls your site’s API. That round-trip adds latency, introduces a dependency on Zapier’s uptime, and means your workflow data lives on someone else’s servers.

For many sites that trade-off is acceptable. For sites handling customer data, course enrollments, or payment events, it is not.

A WordPress-native plugin like Krom Automation runs inside the site. The trigger fires when WordPress fires it, the action executes on the same server, and the execution log writes to your own database. No round-trip, no third-party dependency, no data leaving your hosting environment unless you explicitly tell it to.

Workflow data, execution logs, and API credentials staying inside your own database is not a minor convenience. It is the difference between controlling your automation stack and renting access to it.

The practical consequence is that WordPress-native automation is faster for anything that stays within WordPress, and better suited for regulated industries or clients with data residency requirements. The limit is the inverse: if both endpoints are external services with no WordPress involvement, a cloud tool is the right choice.

Is There a Free Zapier Alternative That Works Inside WordPress?

Yes. The free version of Krom Automation is free forever with no trial period, no run caps, and no features locked behind a paywall after a certain number of executions. The 16 free triggers cover the events that drive most WordPress automations:

• User events (7): User Registered, User Profile Updated, User Login, User Logout, User Role Changed, User Deleted, Password Reset
• Post events (4): Post Published, Post Updated, Post Deleted, Post Status Changed
• Comment events (2): Comment Submitted, Comment Approved
• Media events (1): Media Uploaded
• WooCommerce events (2): Order Created, Order Completed

The 21 free actions include sending email, creating or updating posts and users, making HTTP requests to any external API, and three AI actions covering text generation, content moderation, and auto-tagging. Those AI actions use your own API key and charge at your provider’s standard rates. wpRigel never marks up tokens or adds a per-call fee on top.

You also get 20 ready-made workflow templates, a visual drag-and-drop canvas, conditional branching, delay scheduling, a workflow simulator for dry-run testing, and a full execution log. That is not a stripped-down trial. It is a complete automation tool.

Krom Automation vs. Zapier: Cost in Year One and Beyond

Cost comparisons between subscription tools look different depending on how many sites you run and how many automations fire. The table below uses verified figures. Zapier’s pricing is as of September 2026.

Scenario	Zapier Professional (~$240/yr)	Krom Automation Pro ($69/yr, 1 site)	Krom Automation Pro (lifetime, $199)
Year 1, 1 site	$240	$69	$199
Year 2, 1 site	$480	$138	$199 (no renewal)
Year 3, 1 site	$720	$207	$199 (no renewal)
5 sites, year 1	$1,200 (5 accounts)	$149 (Standard plan, 5 sites)	$399 (Standard lifetime)
Task overages	Yes, above 750/month	None	None

Zapier’s task-based billing means a busy Black Friday weekend can push a $240/year account into overage territory. If you want to understand exactly how that math works in practice, our Zapier pricing breakdown runs through every plan and what WordPress sites actually pay.

Krom Automation’s flat fee covers unlimited executions at every tier. An agency running 5 sites pays $149 a year on the Standard plan. Running the same 5 sites on Zapier at $240 per account would cost $1,200 a year, and that assumes none of them hit the task ceiling.

Krom Automation vs. Uncanny Automator: Which Wins for WordPress?

Uncanny Automator is the most established WordPress-native automation plugin, and it is worth covering honestly. Automation plans start from $199 a year for one site, and newer plans that include AI features start at $300 a year, as of September 2026. There is no lifetime plan.

Krom Automation costs $69 a year for one site with AI actions included free in both the free plugin and every Pro plan. The lifetime plan starts at $199. For a single-site buyer, the price difference is significant in year one and grows every year after.

• Visual builder: Krom Automation uses a drag-and-drop canvas built on ReactFlow with auto layout. Uncanny Automator uses a list-based rule editor. Both work. The canvas is genuinely faster for multi-step branching workflows.
• AI actions: Included free in Krom Automation, no paywall. Uncanny Automator’s AI features sit behind the higher-tier plan at $300/year as of September 2026.
• Execution logging: Both products log executions. Krom Automation’s per-step audit trail is available on the free version.
• Integration count: Uncanny Automator has a larger integration library built over more years. Krom Automation Pro includes 25 integrations, with more on the roadmap.

For a deeper breakdown of where these two tools diverge on pricing and features, the Uncanny Automator pricing analysis is worth reading before you decide.

A list-based rule editor and a visual canvas can both build the same workflow. The canvas wins when you need to debug a failing branch at 11pm before a client’s launch.

What Integrations Does Krom Automation Cover?

The free version handles WordPress core events plus WooCommerce triggers and actions natively. Pro adds 25 integrations across forms, e-commerce, CRM, email marketing, LMS, membership, messaging, social, data storage, and productivity. The ones most relevant to WordPress agency work:

• Forms: Gravity Forms, WPForms, Contact Form 7, Fluent Forms, Elementor Forms, Ninja Forms
• Email marketing: Mailchimp, ActiveCampaign, ConvertKit, MailerLite, MailPoet, FluentCRM
• LMS and membership: LearnDash, TutorLMS, MemberPress
• Messaging: Slack, Discord, Twilio, Telegram
• Data and productivity: Google Sheets and Google Calendar
• E-commerce: WooCommerce Subscriptions, Easy Digital Downloads, AffiliateWP

Pro also adds an incoming webhook receiver with a unique secret URL per workflow and HMAC-SHA256 signature verification. That is how you connect any external service that can send a POST request, including tools Krom Automation does not yet have a native integration for.

When Krom Automation Replaces Zapier Completely

For WordPress-centric workflows, Krom Automation handles everything Zapier handles and does it with less overhead. The clearest replacement scenarios:

• A user registers, gets a welcome email, and is added to a Mailchimp list automatically
• A WooCommerce order completes, a FluentCRM contact is tagged, and an internal Slack notification fires
• A Gravity Forms submission creates a post draft, assigns it to an author, and sends an email to the editor
• A LearnDash course completes, a coupon generates, and a congratulations email goes out
• A MemberPress subscription expires, the user’s role reverts, and a re-engagement sequence starts in ActiveCampaign

Every one of those workflows runs on Krom Automation’s free version or Pro depending on which integrations are needed. None of them require Zapier or a cloud middleware layer. Our guide on when to connect Zapier to WordPress versus replacing it entirely walks through the decision in more detail.

When You Still Need Zapier or a Cloud Tool

Krom Automation is WordPress-native. That is its strength and its scope. If neither the trigger nor the action touches your WordPress site, a cloud tool is the right answer.

Practical examples where you still need Zapier or Make:

• A new row in a Google Sheet triggers a message in Slack, with no WordPress involvement at either end
• A Salesforce deal closes and updates a HubSpot contact, both external to WordPress
• A Typeform response (hosted externally) needs to reach an external CRM with no WordPress step in between

The honest constraint is WP-Cron. Delays in Krom Automation run through Action Scheduler, which relies on WordPress Cron. On very low-traffic sites where no one visits for hours, WP-Cron fires late.

Configuring a real server cron job fixes this, but it requires server access and is an extra setup step. Sites on managed WordPress hosting with reliable cron handling are not affected. The delays and scheduling documentation explains the setup.

If your automation involves WordPress on at least one end, Krom Automation is the better tool. If it involves WordPress on neither end, keep Zapier for that flow and let Krom handle everything else.

Multi-Site and Agency Use: What No One Else Covers

Most comparisons frame this decision around a single site owner. Agencies running 10 to 100 WordPress sites have a different calculation entirely.

On Zapier, each site either uses a separate account or shares task limits, which creates either billing complexity or a ceiling that every site competes against. On Krom Automation, the Standard plan covers 5 sites for $149 a year and the Enterprise plan covers unlimited sites for $299 a year. Lifetime plans are available at $399 and $699 respectively, meaning the automation cost across a client portfolio becomes a one-time line item rather than a recurring one per site.

Sites	Zapier Professional (per site account)	Krom Automation Pro (annual)	Krom Automation Pro (lifetime)
1 site	~$240/yr	$69/yr	$199 once
5 sites	~$1,200/yr	$149/yr (Standard)	$399 once
Unlimited sites	Not available on a single account	$299/yr (Enterprise)	$699 once

Agencies also benefit from the self-hosted model on a practical level. Workflow configurations, execution logs, and API credentials stay inside each client’s WordPress database.

There is no shared cloud account to manage access to. When a client relationship ends, there is nothing to disconnect in a third-party dashboard.

For a structured approach to managing automation across client sites, this guide on WordPress automation across multiple client sites covers the patterns that work at scale.

What the Migration from Zapier Actually Looks Like

Nobody covers this, so here is the honest version. There is no automated migration tool.

Zapier Zaps do not import as Krom Automation workflows. You rebuild them, which is faster than it sounds for most WordPress workflows.

A practical migration approach:

1. Export a list of your active Zaps and group them by whether the trigger or action touches WordPress
2. Zaps that touch WordPress on at least one end are candidates to move first, because Krom Automation handles the WordPress side natively
3. Install the free plugin and rebuild one workflow using the step-by-step workflow builder guide. Run it in parallel with the Zap for a week using the workflow simulator to verify outputs match
4. Disable the Zap once the Krom workflow has a clean execution record. Move to the next one
5. Zaps with no WordPress involvement stay on Zapier or move to Make depending on cost

A typical WordPress site with 5 to 10 active Zaps takes 2 to 4 hours to migrate. The workflows that take longest are ones where you relied on Zapier’s filter steps to handle conditional logic. Krom Automation handles that natively through conditional branching with Yes and No paths, but you need to map your filter logic into branch conditions, which takes a few minutes per workflow.

What the Analytics Tell You That Zapier Does Not

Krom Automation stores all execution data locally, which means you can query it without paying for a higher plan. The analytics dashboard shows total executions, active workflows, failed execution count, and a trend chart. The reports page adds date range filtering, per-workflow success rate, and CSV export.

That matters for agency work specifically. When a client asks why their welcome email did not send last Tuesday, you open the execution log, find the workflow, and read the per-step audit trail.

You do not file a support ticket with a cloud service or try to reconstruct events from an email thread. Silent automation failures are one of the harder problems to diagnose on WordPress, and the guide on silent automation failures is worth bookmarking before you need it.

Also from wpRigel

Pollify is wpRigel’s Gutenberg-native poll, survey and quiz plugin. Polls are built directly inside the block editor as real blocks, with no shortcodes to paste and no separate admin interface to learn. If your site captures audience feedback or runs polls alongside automated content workflows, Pollify and Krom Automation work well together.

Commandify is a command palette for the WordPress admin. Press Cmd or Ctrl and K from anywhere in the admin to search, navigate, or run actions without clicking through menus.

It is the only command palette plugin with genuine WooCommerce depth: full order, product, and customer commands built in. If you manage WordPress sites for clients, Commandify cuts the time spent on routine admin tasks.

Our Verdict: Who Should Switch and Who Should Not

Switch to Krom Automation if: your automations touch WordPress on at least one end, you are paying Zapier $240 or more a year, you want execution logs and workflow data in your own database, or you are an agency paying per-site Zapier costs that multiply across your client list.

Keep Zapier if: you need to connect two external services with no WordPress involvement, or you have hundreds of Zaps across non-WordPress tools that would cost more to migrate than the annual savings justify. You can run both in parallel, with Krom Automation handling every WordPress workflow and Zapier handling the external-to-external ones.

What we would do: install the free plugin today, rebuild the three or four highest-frequency WordPress Zaps, and run them in parallel for two weeks. If the execution logs are clean and the cost difference holds up across your site count, complete the migration and cancel the Zapier plan. The free plugin costs nothing to test and the broader WordPress automation comparison is there if you want a wider view before deciding.

Pro starts at $69 a year with a 14-day money-back guarantee. Download the free version from the WordPress.org plugin directory to start without a credit card.

See all Krom Automation plans and pricing, including lifetime options starting at $199.

Frequently Asked Questions

Does Krom Automation work without any coding?

Yes. Workflows are built on a visual drag-and-drop canvas with no code required.

Conditional branching, delay scheduling, and merge tags for dynamic data are all configured through the visual interface. Developers who want to extend it have a full REST API, but you never need to touch it.

Can Krom Automation connect WordPress to external services like Mailchimp or Slack?

Yes. Pro includes 25 integrations covering email marketing tools like Mailchimp, ActiveCampaign, ConvertKit and MailerLite, plus messaging via Slack, Discord, Twilio and Telegram, and data tools like Google Sheets. The free version can reach any external service via the HTTP Request action, which supports GET, POST, PUT, PATCH and DELETE with JSON response parsing.

Is there a limit on how many workflows or executions I can run?

No. The free version and every Pro plan have no execution caps and no workflow count limits. You pay a flat annual or lifetime fee and run as many workflows as your hosting can handle.

Does switching away from Zapier mean rebuilding all my automations from scratch?

For WordPress-touching workflows, yes, you rebuild them, but they are typically faster to configure in Krom Automation’s visual builder than they were in Zapier’s step editor. There is no automated import tool. The realistic time for a site with 5 to 10 active Zaps is 2 to 4 hours, and running both tools in parallel during the transition removes any risk of a gap in coverage.

What happens if my hosting has unreliable WP-Cron?

Delayed actions in Krom Automation run through Action Scheduler, which depends on WordPress Cron. On very low-traffic sites, WP-Cron can fire late. Configuring a real server cron job on a one-minute interval fixes this completely.

Most managed WordPress hosts either handle this automatically or document how to set it up. Immediate triggers, meaning actions with no delay, are not affected.

Is Krom Automation a good fit for agencies managing multiple client sites?

Yes, and it is one of the stronger arguments for choosing it over Zapier. The Standard plan covers 5 sites for $149 a year and the Enterprise plan covers unlimited sites for $299 a year.

Lifetime plans eliminate the recurring cost entirely. Workflow data stays inside each client’s own database, so there is no shared cloud account to manage.

The best WordPress automation plugin in 2026 depends on what you are automating and how much you want to spend. Krom Automation is the strongest free-tier option, with 16 triggers, 21 actions, a visual drag-and-drop canvas, and AI actions included at no cost.

The free plugin handles most common site automations without any upgrade. Pro starts at $69 a year and adds 80+ additional triggers, 60+ additional actions, and 25 integrations covering forms, email marketing, CRM, LMS, and messaging platforms.

If your automations stay inside WordPress, a self-hosted plugin is almost always the better choice. No per-task fees, no data leaving your server, no third-party dependency sitting between your trigger and your action. If you need to connect two external services with no WordPress involvement, a cloud tool like Zapier is more appropriate, but that is a genuinely different use case.

This article compares the main options across six criteria: workflow builder quality, integrations depth, testing tools, execution logging, AI features, and pricing model. The goal is an honest match between tool and situation, including cases where Krom Automation is not the right fit.

Browse the full Krom Automation feature list or keep reading for the full comparison.

How We Evaluated Each Plugin

Every roundup has criteria. These are the six that actually matter when you are choosing an automation plugin for a live site or a client project.

• Workflow builder: Can you see the full logic of an automation at a glance, or are you reading a list of rules and guessing how they connect?
• Integrations: Does the plugin connect to the third-party tools your site already uses, or will you be writing HTTP requests for everything beyond email?
• Testing: Can you verify a workflow fires correctly before it touches real users or orders?
• Execution logs: When something fails, can you see exactly which step failed, what data it received, and why?
• AI features: Is AI built into the core product or sold as a premium add-on?
• Pricing model: Flat licence versus per-task metering. The difference is significant at volume.

These criteria weight toward agency owners and developers choosing tools for client sites or team use. A solo blogger automating a welcome email has simpler needs, and the free tier of almost any plugin covers that.

The Main Options Worth Comparing

Krom Automation is a visual workflow automation plugin built natively for WordPress. It uses a drag-and-drop canvas built on ReactFlow, where triggers, actions, conditions, and delays are visible nodes connected by lines. The core logic of how triggers, actions, and workflows connect is documented for anyone evaluating it before installing.

Uncanny Automator is the established market leader for WordPress-native automation. It has a large integration library and a mature list-based editor.

Automation plans start at $199 per year for one site as of September 2026, with newer plans that include AI features starting at $300 per year. It has no lifetime plan.

Zapier is a cloud-based automation platform, not a WordPress plugin. It connects external services through a browser interface and uses a per-task billing model. The Professional plan runs around $240 per year billed annually for 750 tasks a month, with overage charges beyond that limit.

It has no lifetime plan. Zapier suits teams whose workflows connect two SaaS tools with WordPress playing a minor role.

AutomatorWP is a lightweight WordPress-native alternative with a free version and paid add-ons. It uses a rule-based editor rather than a visual canvas and is a reasonable choice for simple if-this-then-that logic without a budget.

A flat licence and a per-task billing model are not two versions of the same thing. At 10,000 executions a month, the difference in cost is not a rounding error.

Workflow Builder: Visual Canvas vs Rule List

Most WordPress automation plugins use a list-based editor. You pick a trigger, add actions below it, and the logic runs top to bottom.

That works for simple sequences. It fails when you add branching, delays between steps, and different paths for different conditions.

Krom Automation uses a visual workflow builder built on a canvas, where every node is visible and connected by lines. You can see at a glance that a Yes branch sends a welcome email while the No branch flags the user for review. In a list editor, that same logic requires careful reading to reconstruct.

Conditional branching with Yes and No paths is included in the free version. So are delay nodes that postpone actions by minutes, hours, days, or weeks. Both appear as visible nodes on the canvas rather than nested settings buried inside an action.

Uncanny Automator uses a list-based editor that is well-designed and easy to read for linear workflows. It becomes harder to follow when a workflow has multiple branches. Zapier uses a similar list format optimised for connecting two services step by step.

Integrations: What Each Plugin Actually Connects

The free version of Krom Automation covers the most common WordPress events natively. The 16 free triggers cover user registration, login, logout, profile updates, role changes, post publishing and status changes, comments, media uploads, and WooCommerce order events.

The Pro version adds 25 integrations across forms, email marketing, CRM, LMS, membership, messaging, social media, data storage, productivity, and affiliate platforms. That covers the integrations most WordPress sites actually need without requiring a separate connector for each one.

Specific integrations worth noting for common use cases:

• Forms: Gravity Forms, WPForms, Contact Form 7, Fluent Forms, and Ninja Forms
• Email marketing: Mailchimp, MailerLite, ActiveCampaign, ConvertKit
• CRM: FluentCRM
• LMS: LearnDash, TutorLMS
• Membership: MemberPress
• Messaging: Slack, Discord, Twilio, and Telegram
• Data and productivity: Google Sheets and Google Calendar

Uncanny Automator has a larger integration count overall and has been building its library for longer. If a specific third-party plugin matters to you and it is not listed above, check Uncanny Automator’s integration page before deciding. Zapier connects to more external SaaS tools than either WordPress plugin, but it is not self-hosted and its data passes through Zapier’s servers.

Testing and Execution Logging: Where Most Plugins Fall Short

This is the gap that costs the most time in production. A workflow that looks correct in setup can fail silently when a condition does not match, a merge tag resolves to empty, or an external API returns a 4xx error. Without step-level logging, finding the fault means guessing.

Krom Automation includes a workflow simulator for dry-run testing with zero side effects. You can fire a workflow against real or synthetic data before it touches any user, order, or external service. That is not a common free-tier feature.

Execution logging records every run with a full per-step audit trail, so when a workflow fails on step 3 of 5, you see exactly what data reached that step and what the failure was. The analytics dashboard shows total executions, active workflow count, success rate, and a trend chart. The reports page adds date range filtering and CSV export.

A workflow failing 20 percent of the time looks identical to a working one until you check the logs. Logging is not a nice-to-have. It is the only way to know your automations are actually running.

Failure notifications arrive by email, and failed executions retry automatically with configurable backoff. The article on what happens when an automation fails silently on WordPress covers the real-world consequences in more detail.

Uncanny Automator includes execution logs in its paid plans. AutomatorWP’s logging depth varies by plan. Zapier logs task history but the data lives on Zapier’s servers, not yours.

AI Features: Built In vs Bolted On

Krom Automation includes three AI actions in the free version: AI Generate Text, AI Content Moderation, and AI Auto-Tag. You bring your own API key from OpenAI, Google Gemini, or Groq, and you pay your provider directly at their standard rates. wpRigel charges nothing per AI call and marks up no tokens.

Supported models in the free version include GPT-4o Mini, GPT-4o, Gemini 2.0 Flash, Gemini 2.5 Flash Preview, Gemini 2.5 Pro Preview, Llama 3.3 70B, and Llama 3.1 8B. That covers a range of cost and capability trade-offs without any plan restriction.

Pro adds AI workflow generation: describe an automation in plain English and get a working workflow on the canvas in seconds. That is useful for getting a first draft of a complex workflow, which you then review and adjust before enabling.

Uncanny Automator introduced AI features in its newer plans starting at $300 per year as of September 2026. Zapier has AI steps in its higher-tier plans. Neither includes AI at the free tier.

Pricing Model: Flat Licence vs Per-Task Billing

This is the decision that matters most at scale. Flat-licence plugins charge once per year or once forever regardless of how many automations run. Per-task tools charge based on execution count, which means a busy WooCommerce store or a membership site with a large user base pays more every month as it grows.

Plugin	Model	Entry price	Run limits	Lifetime plan
Krom Automation (free)	Flat, self-hosted	Free forever	None	N/A
Krom Automation (Pro)	Flat, self-hosted	$69/year or $199 lifetime (1 site)	None	Yes, from $199
Uncanny Automator	Flat, self-hosted	From $199/year (1 site, as of Sep 2026)	None	No
Zapier Professional	Per-task, cloud	~$240/year (750 tasks/month, as of Sep 2026)	750 tasks/month, overages charged	No

For a site running 5,000 automation executions a month, the Krom Automation Pro annual fee stays fixed. On Zapier’s Professional plan, 5,000 tasks a month would require a higher tier with a significantly larger bill. The article on Zapier’s 2026 pricing and what WordPress sites actually pay works through the real numbers.

Krom Automation Pro plans cover 1 site (Basic, $69/year), 5 site activations (Standard, $149/year), and unlimited sites (Enterprise, $299/year) at current launch pricing. Lifetime plans start at $199 for 1 site.

Every plan includes all Pro features and all 25 integrations. The difference between plans is only the site count.

Which Tool Suits Which Situation

Situation	Best fit	Reason
WordPress-native automations, tight budget	Krom Automation free	16 triggers, 21 actions, AI included, no cost, no run caps
Agency managing 5+ client sites with WooCommerce, LMS, or CRM	Krom Automation Pro Standard or Enterprise	Flat per-site licence, 25 integrations, no task metering
Large integration library for legacy plugin ecosystem	Uncanny Automator	Broader integration count, mature platform
Connecting two external SaaS tools, WordPress plays a minor role	Zapier	Cloud native, built for external service connections
Simple linear automations, minimal budget	AutomatorWP free	Lightweight, no canvas overhead for basic needs
High execution volume on a WordPress-native stack	Krom Automation Pro	No per-task charges, background execution via Action Scheduler

What the Marketing Pages Do Not Tell You

Every automation plugin works on a clean site with low traffic and simple workflows. The differences show up at the edges. Here is what to check before committing.

• WP-Cron dependency: Krom Automation schedules delayed actions through Action Scheduler, which relies on WP-Cron by default. On very low-traffic sites where no page visit fires for several hours, a delayed action fires late. A real server cron job solves this, but it requires server access. This is not a Krom Automation limitation specifically; it affects every WordPress plugin that uses WP-Cron for scheduling.
• AI API costs: Krom Automation charges nothing for AI actions, but you pay your API provider directly. At low volume this is negligible. At scale with a verbose generation prompt and GPT-4o, it adds up. Gemini 2.0 Flash and Llama 3.1 8B are the low-cost options when the output quality is sufficient.
• Zapier task overages: On Zapier’s task-based model, a busy Black Friday week can push you past your monthly task limit in days. The real cost of Zapier during peak traffic periods is worth reviewing before any high-volume campaign.
• Uncanny Automator plan complexity: The pricing structure changed in 2026, and the AI-inclusive plans cost significantly more. The full breakdown is covered in the Uncanny Automator pricing analysis for 2026.
• Self-hosted data control: Both Krom Automation and Uncanny Automator keep execution logs, API credentials, and workflow data in your own database. Zapier processes workflow data on its own infrastructure. For sites handling personal data under GDPR, that distinction matters.

The plugin that looks cheapest at sign-up is often the most expensive one to operate at scale. Run the per-execution numbers before you build anything.

Getting Started with Krom Automation

The free plugin installs from the WordPress.org plugin directory and is ready to use in under five minutes. The installation guide covers the full setup process, and the first workflow tutorial walks through sending a welcome email when a user registers, which is the most common starting point.

Merge tags inject live event data into any action field, so a welcome email can address the user by name and reference the post they just commented on without any custom code. That is available in the free version alongside conditional branching, delay scheduling, and the workflow simulator.

If you want to evaluate what Pro adds before buying, the complete free vs Pro comparison lists every feature by tier.

Also from wpRigel

Pollify is wpRigel’s Gutenberg-native poll, survey, and quiz plugin. Polls are built directly inside the block editor as real blocks, so there are no shortcodes to paste and no separate interface to learn. If you need to collect feedback or run a quiz alongside your automation workflows, it works without any additional integration.

Commandify is a command palette for the WordPress admin. Press Cmd or Ctrl plus K to jump anywhere in the admin, search content, and run actions without navigating through menus. It is the only WordPress command palette with full WooCommerce order, product, and customer commands built in.

Our Verdict

For most WordPress sites, Krom Automation’s free version is the right starting point. It covers the triggers and actions that handle 80 percent of common automations, includes AI, and has no run caps. If you outgrow it, Pro starts at $69 a year with a 14-day money-back guarantee, and the lifetime plan at $199 removes the annual renewal question entirely.

Choose Uncanny Automator if you need a specific integration that Krom Automation does not yet cover and the $199 annual entry price fits your budget. Choose Zapier if your automations primarily connect two external services and WordPress is a minor participant. Do not choose a per-task tool for a high-execution WordPress workflow if a flat-licence plugin covers the same triggers and actions.

The free version is the lowest-friction way to form an opinion. Download Krom Automation from the WordPress.org plugin directory and run the simulator before you commit to anything.

Compare all Krom Automation plans and pricing or start with the documentation if you want to understand the full scope before installing.

Frequently Asked Questions

Is there a free WordPress automation plugin that actually works for real sites?

Yes. Krom Automation’s free version includes 16 triggers, 21 actions, a visual workflow builder, conditional branching, delay scheduling, execution logging, and AI actions.

There are no run caps and no trial period. It is free permanently, not a feature-limited trial.

What is the difference between Uncanny Automator and Krom Automation?

Both are self-hosted WordPress-native automation plugins with flat-licence pricing and no per-task fees. Uncanny Automator has a larger integration library built over more years.

Krom Automation has a visual canvas builder, AI actions included free, and a Pro plan that starts at $69 a year compared to Uncanny Automator’s $199 entry price as of September 2026. Krom Automation also offers lifetime plans; Uncanny Automator does not.

Should I use Zapier or a WordPress plugin for automation?

Use a WordPress plugin if your trigger and action both involve WordPress. Use Zapier if you are connecting two external SaaS tools and WordPress is not directly involved. Zapier’s per-task billing model becomes expensive at volume, while a flat-licence plugin costs the same regardless of how many automations run.

Can WordPress automation plugins connect to external apps like Slack or Mailchimp?

Yes, with a Pro plan. Krom Automation Pro connects to Slack, Discord, Telegram, Twilio, Mailchimp, ActiveCampaign, FluentCRM, ConvertKit, MailerLite, Google Sheets, and more across 25 integrations. The free version can reach any external service using the HTTP Request action, which supports GET, POST, PUT, PATCH, and DELETE with JSON response parsing.

What is the best automation plugin for WooCommerce stores?

Krom Automation handles WooCommerce order and product events natively in the free version, including Order Created and Order Completed triggers and Create Coupon and Update Order Status actions. Pro adds WooCommerce Subscriptions support for recurring membership and billing workflows. For stores with high order volumes, the flat-licence model prevents the escalating costs that come with per-task tools at scale.

Do I need to know how to code to use these plugins?

No. Krom Automation is built for no-code use. The visual canvas lets you connect triggers, actions, conditions, and delays by clicking and dragging.

Merge tags handle dynamic data like user names and order totals without any scripting. The Pro AI workflow generator lets you describe an automation in plain English and get a working canvas draft in seconds.