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.

The fastest way to keep your team updated on Black Friday sales in real time is to connect your WooCommerce store to Slack using Krom Automation. The free plugin covers order alerts via HTTP Request actions. The Pro plan adds native Slack, Telegram, and Google Sheets integrations that take about 20 minutes to configure.

Black Friday 2026 is November 27. Set this up by November 13 so you have two weeks to test.

Every competing guide treats Slack as a passive webhook destination. This one treats it as a live operations channel: one workflow per purpose, a running order log in Google Sheets, and Telegram for whoever is away from their desk. The goal is that your team knows the moment a high-value order lands, a product sells out, or revenue crosses a milestone, without anyone refreshing the dashboard.

This guide covers four workflows you can build once and run all weekend. It also covers the one timing limitation you need to understand before you rely on any of them.

Browse the full feature list to see every trigger and action available before you start building.

Quick Summary

Alert type	Trigger	Destination	Free or Pro?
New order notification	Order Created	Slack channel	Pro (Slack action)
High-value order alert	Order Created + condition	Slack DM or channel	Pro
Order completed log	Order Completed	Google Sheets row	Pro
Owner alert on the move	Order Created	Telegram message	Pro
HTTP Request fallback	Order Created	Any Slack webhook URL	Free

Why Slack Alone Is Not Enough

A Slack channel full of raw order notifications turns into noise within the first hour of a sale. By midday on Black Friday, your team stops reading them. The fix is not fewer alerts, it is smarter routing: order volume to a shared channel, high-value orders to a dedicated thread, the owner’s phone to Telegram, and a Google Sheets log that gives you the full picture at a glance without anyone having to scroll through chat history.

Each of the four workflows below has exactly one job. That separation is what keeps the channels readable. Conditional branching in Krom Automation lets you split paths inside a single workflow, so a $500 order and a $20 order can trigger different actions from the same starting point.

A Slack channel full of every order is a wall of noise. A Slack channel filtered to orders over $200 is an operations tool.

Workflow 1: New Order Notification to a Slack Channel

This is the baseline alert. Every new WooCommerce order posts a formatted message to a shared team channel. The message should include the order number, customer name, order total, and the items purchased, all pulled in automatically using merge tags.

The setup in Krom Automation Pro uses the Order Created trigger and the Slack action. Connect your Slack workspace once under the integrations settings, choose the target channel, and write your message template.

A typical message takes about 5 minutes to configure once the connection is live. Full setup steps are in the messaging integrations documentation.

If you are on the free plugin and want to start before upgrading, the HTTP Request action works with Slack’s incoming webhook URL. You send a POST request with a JSON body containing the merge tag values. It is more manual to set up but it costs nothing and the result is functionally identical.

What the Slack message should include

• Order number, so the team can pull it up in WooCommerce instantly
• Customer name and email, so support knows who ordered without leaving Slack
• Order total in currency, so revenue milestones are visible in real time
• Product names, so the fulfilment team knows what needs to move
• A direct link to the order edit screen, saving 30 seconds per order lookup

Workflow 2: High-Value Order Alert with Conditional Branching

Not every order deserves the same attention. A conditional branch after the Order Created trigger checks whether the order total exceeds a threshold you set, say $200 or $500.

Orders above that threshold post to a separate #big-orders channel or trigger a direct message to the store owner. Orders below it post to the general channel as normal.

This is the workflow most teams skip because it takes an extra 10 minutes to build. It is also the one that saves the most time on the day, because your senior people stop wading through $15 orders to find the ones that matter. The conditions and branching documentation shows exactly how to configure the Yes and No paths.

For a deeper look at structuring high-value order notifications across a busy sale period, the guide on WooCommerce high-value order notifications covers the threshold logic in more detail.

Ten minutes building a conditional branch on November 13 saves your team two hours of scrolling on November 27.

Workflow 3: Live Google Sheets Order Log

Slack is for alerts. Google Sheets is for the record.

This workflow fires on Order Completed and appends a new row to a spreadsheet with every field you need for end-of-day reconciliation: order ID, customer name, email, total, products, payment method, and timestamp. By midnight on Black Friday, you have a complete log without anyone having to export anything from WooCommerce.

The Google Sheets integration documentation covers the OAuth connection and column mapping. The key decision is whether to trigger on Order Created or Order Completed. Order Created catches everything including orders that later fail or get refunded.

Order Completed catches only paid, fulfilled orders. For a clean revenue log, Order Completed is the right choice.

Columns worth logging from day one

• Timestamp so you can see order velocity by hour
• Order total for a running revenue sum at the bottom of the sheet
• Payment method to flag any unusual patterns quickly
• Product names to track which items are selling fastest
• Customer email so post-sale tagging and follow-up is ready to go

If you plan to tag those customers in Mailchimp or FluentCRM after the sale, the guide on tagging Black Friday customers automatically explains how to chain that into the same workflow or run it as a separate one. The FluentCRM integration documentation covers the contact and tag actions in detail.

Workflow 4: Telegram Alert for the Owner on the Move

Not everyone is at a desk on Black Friday. If the store owner or a senior team member needs order alerts on their phone without needing the Slack app open, Telegram is the right channel.

Krom Automation Pro supports Telegram natively alongside Slack, Discord, and Twilio. One workflow, one trigger, two action branches: Slack for the team, Telegram for the individual.

The practical setup is a Telegram bot connected to a private chat or a small group. The message can be shorter than the Slack version because it is personal context, not a shared operations log.

Order total, product name, and a link is usually enough. The full configuration is covered in the messaging integrations documentation alongside the Slack setup.

The One Timing Limitation to Know Before Black Friday

Krom Automation runs background tasks via Action Scheduler, which relies on WordPress Cron. On sites with consistent traffic, this works well and delays are measured in seconds. On very low-traffic sites where no one visits for an extended period, WP-Cron fires late, and a delayed order alert on Black Friday is nearly as bad as no alert.

The fix is simple: configure a real server cron job to call the WordPress cron endpoint every minute. Your host’s control panel or a tool like WP-CLI handles this in under 5 minutes.

Do it before November 27. The article on whether Black Friday traffic will break your WordPress automations covers this and other load considerations in full.

If you are running any delayed actions, the delays and scheduling documentation explains how to configure backoff and what happens when a queued action misses its window.

Set It Up by This Date: A Countdown Timeline

Black Friday is November 27, 2026. Cyber Monday is November 30. These deadlines are not generous, they are the minimum lead time to build, test, and fix anything before the sale starts.

Date	What to complete
November 7	Install Krom Automation Pro, connect Slack, Telegram, and Google Sheets
November 10	Build Workflow 1 (order to Slack) and Workflow 3 (completed order to Sheets)
November 12	Build Workflow 2 (high-value branch) and Workflow 4 (Telegram)
November 13	Run the workflow simulator on all four workflows. Fix anything that fails.
November 17	Place two test orders in WooCommerce staging. Confirm all four destinations receive messages.
November 20	Configure real server cron. Confirm it fires every minute.
November 24	Final check: all workflows active, execution logs clean, Slack channels live

Test with the Simulator Before Any Real Orders Arrive

Krom Automation includes a workflow simulator that runs a full dry-run of any workflow with zero side effects. No Slack messages are sent, no rows are added to Google Sheets, no Telegram messages fire. You see exactly what would have happened, including merge tag values, branch decisions, and action outputs, without touching a real order.

Run the simulator on each of the four workflows before November 27. Check that merge tags resolve to real values, that the high-value branch fires on the correct path, and that the Google Sheets column mapping lands in the right columns. A 15-minute simulation session on November 13 is the difference between a smooth Friday and a morning of emergency fixes.

The simulator also catches silent failures, the kind where a workflow appears active but never fires because a connection credential expired. Silent failures on Black Friday are expensive. The article on what happens when an automation fails silently explains how to catch them before they cost you.

The simulator is the most underused feature in Krom Automation. Running it costs 15 minutes. Not running it can cost a sale.

What Krom Automation Pro Costs vs. the Alternatives

The free plugin is free forever with no run caps and no feature locks on the core engine. The HTTP Request action in the free version handles basic Slack webhooks at no cost. Pro adds native Slack, Telegram, Google Sheets, and 22 other integrations, plus the schedule trigger, incoming webhook receiver, and 101 additional workflow templates.

Option	Cost for 1 site, year 1	Cost from year 2	Run limits	Native Slack action
Krom Automation Free	$0	$0	None	No (HTTP Request workaround)
Krom Automation Pro Basic	Starts at $69/year	$119/year	None	Yes
Uncanny Automator (as of September 2026)	From $199/year	$199/year	None stated	Via integration add-on
Zapier Professional (as of September 2026)	Around $240/year	Around $240/year	750 tasks/month, overages charged	Yes

Zapier’s task-based billing is worth thinking about specifically for Black Friday. If your store processes 1,000 orders over the weekend and each order fires three Zaps, that is 3,000 tasks in 72 hours. At 750 tasks per month on the Professional plan, you hit overage charges before Saturday morning.

Krom Automation has no per-task or per-execution billing at any tier. The full breakdown of what Zapier costs during Black Friday runs through the numbers scenario by scenario.

Lifetime plans for Krom Automation Pro start at $199 for one site, which covers all 25 integrations and every Pro feature with no annual renewal. See full pricing details for the current launch rates across all plans.

What This Setup Does Not Cover

These four workflows handle alerting. They do not handle stock management, coupon creation, or post-sale follow-up.

If you also need low-stock alerts before you sell out, that is a separate workflow covered in the guide on avoiding running out of stock on Black Friday. If you need to automate coupon codes as part of the sale itself, the guide on sending Black Friday coupon codes automatically covers that workflow.

These workflows also do not apply to sites with no WooCommerce involvement. Krom Automation is WordPress native, so both the trigger and the action touch your site. If you need to monitor a third-party retailer’s price page and alert in Slack, that is a page-monitoring tool problem, not a WordPress automation problem.

Also from wpRigel

Pollify is wpRigel’s Gutenberg native poll, survey, and quiz plugin. Polls are built as real blocks inside the editor, with no shortcodes to paste and no separate interface to configure. Useful for gathering post-sale feedback or running a quick audience poll directly on a post or page.

Commandify is a command palette for the WordPress admin. Press Cmd or Ctrl plus K to jump anywhere, search orders, products, and customers, and run admin actions without clicking through menus. It is the only WordPress command palette with real WooCommerce order, product, and customer commands, which makes it useful exactly on a day when speed in the admin matters.

Our Verdict

If your team is currently refreshing the WooCommerce dashboard or checking a shared inbox for order notifications on Black Friday, these four workflows replace that with a live operations setup that runs without anyone managing it. The free plugin gets you most of the way with the HTTP Request action. Pro makes it faster to configure and adds Telegram and Google Sheets without custom code.

Build by November 13, simulate on November 13, test with real staging orders by November 17, and you will have two full weeks of buffer before the sale starts. Teams that build this on November 26 find something wrong on November 27.

Build it now. Download the free plugin from the WordPress.org plugin directory and install Pro when you are ready to connect Slack natively.

Compare all three Pro plans and pick the one that fits your site count. The 14-day money-back guarantee covers the full sale weekend if you start this week.

Frequently Asked Questions

Do I need Krom Automation Pro to send Black Friday alerts to Slack?

No. The free plugin includes the HTTP Request action, which works with Slack’s incoming webhook URL.

You write the JSON body manually and use merge tags to inject order data. Pro adds a native Slack action that removes that manual step and also adds Telegram and Google Sheets as destinations.

Will WP-Cron delay my order alerts during peak traffic?

On high-traffic sites, WP-Cron fires frequently and delays are minimal. On low-traffic sites, alerts can arrive late if no request hits the site for an extended period. The fix is a real server cron job calling the WordPress cron endpoint every minute, which your host’s control panel can configure in under 5 minutes.

Can I send different alerts to different Slack channels from one workflow?

Yes. Use conditional branching after the Order Created trigger. Orders above your threshold go to one channel action, orders below go to another.

Both branches can include different message formats and different Slack channel targets. The conditions and branching documentation covers the configuration.

How do I test these workflows without placing real orders?

Use the built-in workflow simulator. It runs a complete dry-run of every step, resolves merge tags, and shows you what each action would have sent, without actually sending anything to Slack, Telegram, or Google Sheets.

Run it before November 27. Full details are in the simulator documentation.

Does Krom Automation charge per order or per workflow execution?

No. There is no per-task, per-execution, or per-order billing at any tier, including the free version. You pay once for the Pro licence and run as many workflows as your site generates, across the full Black Friday weekend and beyond.

Can I use the Google Sheets log alongside the Slack alerts in the same workflow?

Yes. A single workflow can have multiple action branches.

The Order Created trigger fires once, and Krom Automation can post to Slack, send a Telegram message, and append a Google Sheets row all from the same execution. Alternatively, run them as separate workflows if you want to pause or test them independently.

Black Friday membership and course automation with Krom Automation covers the full cycle: a welcome email fires the moment someone buys, they enrol in the right course automatically, and a renewal follow-up sequence runs in the weeks after the sale. The free plugin handles enrolment triggers and email actions. Pro adds the Schedule trigger and visual email builder you need for timed sequences and deadline reminders, so plan on Pro if your sale has a countdown.

Black Friday 2026 falls on November 27, Cyber Monday on November 30. That gives you roughly eight weeks from the time you read this to build, test, and stress-test every workflow before traffic arrives. That is enough time if you start now, and not enough time if you wait until the week before.

Most guides for Black Friday course sales stop at the checkout. They cover email teasers, discount codes, and cart abandonment, then go quiet.

What they skip is the automation that keeps a deal buyer engaged for the next 12 months, which is the only part that actually determines whether the sale was worth running. This guide covers both halves.

Browse the full feature list to see which triggers and actions apply to your stack before you start building.

What Does a Complete Black Friday Automation Actually Cover?

A complete Black Friday automation for a membership or course site has three phases. Miss any one of them and you are leaving revenue on the table or setting up for a churn spike in January.

• Phase 1, sale window: trigger on purchase, enrol the buyer in the correct course or membership tier, fire a branded welcome email, tag them in your CRM or email list, and send an internal Slack or email alert so your team knows the sale is converting.
• Phase 2, onboarding (days 1 to 14): a welcome sequence dripped over the first two weeks, a check-in at day 7 asking whether they have logged in, and a milestone trigger when they complete their first lesson or hit a content gate.
• Phase 3, retention (days 30 to 90): a renewal reminder at 30 days for annual subscribers, a re-engagement email at day 45 for anyone who has not logged in since purchase, and a churn-prevention offer at day 60 for members who look inactive.

The third phase is what none of the competitor content covers. Selling a Black Friday deal is easy. Keeping those buyers past January is the actual challenge, and it requires workflows that run long after you have moved on to the next promotion.

Which Triggers and Actions Do You Actually Need?

The table below maps each phase of a Black Friday membership workflow to the specific Krom Automation trigger, the action that fires, and whether that trigger is in the free plugin or requires Pro.

Workflow step	Trigger	Action	Free or Pro
Buyer completes purchase	MemberPress signup / Order Completed	Send Email, Change User Role	Free
Enrol buyer in course	MemberPress signup	LearnDash / TutorLMS enrolment action	Pro (integration)
Tag buyer in email list	MemberPress signup	Mailchimp tag, FluentCRM tag, ConvertKit tag	Pro (integration)
Day 3 check-in email	Schedule trigger (after signup delay)	Send Email with merge tags	Pro
Day 7 login nudge	Schedule trigger	Send Email, conditional branch if logged in	Pro
Course completion celebration	LearnDash Course Completed	Send Email, Create Coupon (next course)	Free (trigger) / Free (coupon)
Day 30 renewal reminder	MemberPress Subscription Expiry	Send Email with renewal link merge tag	Pro (integration)
Day 45 re-engagement	Schedule trigger	Send Email, conditional branch on last login	Pro
Internal team alert on every sale	Order Completed	Slack / Discord message	Pro (integration)

The free plugin covers the purchase trigger, the welcome email, and basic user role updates. Everything involving timed delays, integrations with MemberPress or LearnDash, or email list syncing requires Pro. The free vs Pro comparison spells out exactly which features sit at which tier.

Setting Up the Purchase Trigger for MemberPress, LearnDash, and TutorLMS

The trigger is the most important decision you make. Choose the wrong one and the workflow fires for the wrong people, or does not fire at all.

For MemberPress, use the MemberPress Signup trigger. It fires when a member completes a transaction and gains access, which is the correct moment to start the onboarding sequence. The MemberPress integration documentation covers the available triggers, including signup, subscription renewal, subscription expiry, and failed payment, along with the merge tags each one exposes.

For LearnDash, the purchase trigger depends on how you sell. If LearnDash courses are sold through WooCommerce, use the WooCommerce Order Completed trigger and then fire a LearnDash enrolment action.

If you sell through LearnDash’s own payment system, use the LearnDash Course Enrolled trigger directly. The LearnDash integration documentation lists every available trigger including enrolment, lesson completion, quiz passed, quiz failed, and group membership.

For TutorLMS, the Course Enrolled trigger fires as soon as a student gains access, whether that is through a free enrolment or a completed payment. See the TutorLMS integration documentation for the full trigger list and available merge tags like student name, course name, and enrolment date.

The trigger you pick on day one determines what data you have access to for the entire workflow. Choosing the wrong trigger means rewriting the whole thing after the sale starts.

Building the Welcome Sequence That Actually Onboards Deal Buyers

A single welcome email is not a welcome sequence. A welcome sequence is three to five emails sent over the first 14 days, each with a single job. Here is the structure we recommend for Black Friday buyers specifically.

• Email 1, immediate: purchase confirmation, login link, and one specific action to take in the next 10 minutes. Not a wall of features. One action.
• Email 2, day 3: a reminder of what they bought and a link to the first piece of content or the first lesson. Frame it as “most members who get the most out of this start here.”
• Email 3, day 7: a check-in. Ask whether they have started. If your platform tracks last login, use a conditional branch to send a different version to people who have not logged in yet.
• Email 4, day 14: social proof. A short story from another member who joined during a sale period and stuck around. This is the email that separates the buyers who stay from the ones who forget they subscribed.

Each email is a separate action node on the canvas, connected by delay nodes. The delays and scheduling documentation shows how to set a delay of 3 days, 7 days, or any custom interval in seconds if you need finer control. Use merge tags to pull the buyer’s first name, course name, and membership level into every email so the sequence reads like it was written for them.

The visual email builder (Pro) lets you design each email in a block-based editor without writing HTML. That matters on Black Friday because you want branded emails, not plain text, and you want to change the header image or CTA button in 90 seconds without touching code.

Tagging Buyers in Your Email List and CRM

Every Black Friday buyer needs a tag in your email platform the moment they purchase. Without that tag, you cannot segment them from full-price members, you cannot suppress them from future promotional emails about deals they already bought, and you cannot run a targeted re-engagement campaign in January.

Krom Automation Pro supports Mailchimp, FluentCRM, ConvertKit, ActiveCampaign, and MailerLite as direct integration actions. The workflow pattern is consistent across all of them: trigger on purchase, add the subscriber, apply a tag like “bf2026-member”, move them off the promotional list, and add them to the onboarding sequence list.

For more detail on tagging Black Friday buyers specifically across Mailchimp and FluentCRM, see our guide on tagging Black Friday customers automatically.

A buyer who stays on your general promotions list after purchasing is a complaint waiting to happen. Tag them on purchase and suppress them from the next broadcast, not the one after.

Renewal Follow-Up: Keeping Deal Buyers Past January

This is the section nobody writes. Black Friday buyers are the most price-sensitive cohort you will ever acquire.

They bought because of the discount. If you do not have a retention workflow running before their renewal date, you will lose a disproportionate number of them.

The MemberPress integration exposes a Subscription Expiry trigger that fires a configurable number of days before the renewal date. Use it to run a sequence like this:

• 30 days before renewal: an email summarising what they have accessed or completed, with a link to their progress report. The goal is to remind them of the value they have already received.
• 14 days before renewal: a plain-text email from a real name on your team. No graphics, no buttons. Just “we noticed your membership renews on [date]. Is there anything you want to cover before then?” This email gets replied to.
• 3 days before renewal: a clear renewal reminder with the price, the renewal link, and a one-line answer to the most common objection. For annual memberships, that objection is almost always “I did not use it enough to justify another year.”
• 1 day after failed renewal: a recovery email using the MemberPress Failed Payment trigger. Do not assume the failure was intentional. Most failed payments are expired cards.

For WooCommerce Subscriptions users, the WooCommerce Subscriptions integration provides the same pattern, with triggers for subscription renewal, subscription cancellation, and payment failure.

Stress Testing Before the Sale: Using the Workflow Simulator

Every workflow you build for Black Friday must be tested with zero real users before the sale starts. Krom Automation includes a workflow simulator that runs a dry pass through the entire workflow, showing you which branches fire, which actions would execute, and what the merge tag output would look like, without sending a single email or creating a single database record.

Run the simulator for every workflow you plan to have active on November 27. Check these three things specifically:

• Does the correct branch fire when a buyer has the “bf2026” tag versus one who does not?
• Do merge tags resolve to real values, or do any come back as empty strings?
• Does the delay timing produce the correct dates when you run it against a November 27 start date?

A workflow that sends a “day 7 check-in” on day 4 because of a misconfigured delay unit is embarrassing on a Tuesday and a disaster on Black Friday. Test it first.

Also worth reading before launch: whether Black Friday traffic will break your WordPress automations, which covers Action Scheduler queue depth, WP-Cron reliability, and what to monitor during peak hours.

The WP-Cron Problem on Low-Traffic Sites

Krom Automation uses Action Scheduler for background execution, which means no workflow runs during a page load. That is good for performance. But Action Scheduler depends on WordPress Cron, and WP-Cron only fires when someone visits the site.

If your site gets fewer than one visit every 15 minutes, delayed workflow steps can fire late. A “send email at 9am” instruction might not execute until 11am if no one visits between those times.

On Black Friday this is unlikely to be a problem because traffic will be high. But in the weeks before and after the sale, when you are running the onboarding and renewal sequences on a smaller number of buyers, the risk is real.

The fix is straightforward: replace WP-Cron with a real server cron job that hits wp-cron.php every minute. Most managed WordPress hosts offer this in their control panel. If yours does not, a cron job via cPanel or a server-level scheduler takes about 5 minutes to configure and eliminates the problem entirely.

Your Setup Timeline: Work Backwards from November 27

Date	Task	Why it matters
October 1	Install Krom Automation Pro, connect integrations	Gives you 4 weeks to find any compatibility issues before you need the workflows live
October 8	Build the purchase trigger and welcome email workflow	The most critical workflow. Test it first, test it longest.
October 15	Build the onboarding sequence (emails 2 through 4)	Delay nodes need to be verified against real calendar dates, not just unit labels
October 22	Build email list tagging and CRM sync workflows	Segment errors compound. A buyer on the wrong list for 3 weeks is hard to clean up.
November 1	Build renewal follow-up sequence	Renewal triggers fire 30 days after purchase, which means they start firing in late December. Build them now.
November 10	Run simulator on every workflow	Two weeks to fix anything the simulator surfaces
November 17	Test with a real purchase on a staging or test account	Simulator catches logic errors. A real test catches integration misconfigurations.
November 24	Final check, pause any non-BF workflows that might conflict	Buyers should not receive a standard “new member” sequence AND a Black Friday sequence simultaneously
November 27	Sale opens, workflows live	Monitor the execution log for failures in the first hour

The renewal sequence starting on November 1 might feel early. It is not.

A 30-day renewal reminder for someone who buys on November 27 fires on October 28 of next year, but a 30-day pre-expiry trigger for someone on a monthly plan fires in late December, which is right after the holidays. Build it now so you are not doing it in a panic.

What Transfers Automatically and What You Have to Rebuild

If you are migrating from a manual email sequence, a spreadsheet reminder system, or another automation tool, here is an honest account of what moves easily and what does not.

• Transfers automatically: any workflow you export from Krom Automation as JSON imports perfectly to another WordPress install. Workflow logic, branching, delay settings, and action configuration all travel with the export file.
• Transfers automatically: merge tag placeholders in email bodies. The tag syntax is consistent across installs, so a welcome email written for one site works on another with no edits.
• Does not transfer: existing subscribers or members. Krom Automation handles events as they happen. It cannot retroactively trigger on purchases that occurred before the workflow was active.
• Does not transfer: API credentials for integrations. Mailchimp API keys, FluentCRM connection settings, and LearnDash integration configuration are all site-specific and must be re-entered on each install.
• Does not transfer: execution history or analytics data. Each site maintains its own log, and logs do not travel with the workflow JSON.

For teams managing multiple client sites, the import/export approach scales well. Build the canonical Black Friday workflow once, export it, and import it to each client site with the integration credentials updated. See our piece on WordPress automation across multiple client sites for how to manage this efficiently.

The workflows travel. The execution history and API keys do not. Plan for 20 minutes of integration configuration per site when you deploy to a new install.

What Krom Automation Does Not Do Here

Being clear about limitations is more useful than pretending they do not exist.

Krom Automation does not manage the discount or coupon creation side of your Black Friday sale. You still need to create the WooCommerce coupon or MemberPress discount rule manually, or use a plugin that handles that. What Krom handles is everything that happens after the purchase fires.

It also does not include a built-in affiliate tracking system. If you are running a Black Friday affiliate campaign, you need AffiliateWP or a similar plugin. Krom Automation does integrate with AffiliateWP via the AffiliateWP integration, so you can trigger workflows on affiliate referral events, but Krom itself does not replace the affiliate plugin.

Finally, if your Black Friday sale requires sending a personalised coupon code to every buyer immediately on purchase, that is covered by the Create Coupon action in the free plugin. But if you want the coupon code to be unique per user and pre-generated in bulk before the sale starts, that is a WooCommerce coupon management task, not an automation task. The guide on sending Black Friday coupon codes automatically covers this pattern in detail.

Pricing: What Running This Actually Costs

The free plugin covers the purchase trigger, the Send Email action, and the Create Coupon action. If your Black Friday workflow is a single welcome email on purchase with no delays, no CRM tagging, and no timed sequences, the free version is sufficient.

For any real Black Friday automation, including timed sequences, MemberPress or LearnDash integration, and email list tagging, Pro is required. Krom Automation Pro starts at $69 a year for a single site, or $199 for a lifetime licence. For agencies deploying across multiple client sites, the Standard plan covers 5 sites at $149 a year, or $399 lifetime.

See full pricing details. Every Pro plan carries a 14-day money back guarantee.

For comparison, Uncanny Automator’s automation plans start at $199 per year for one site, with AI features starting at $300 per year, as of September 2026. Zapier’s Professional plan runs around $240 per year for 750 tasks per month, with task-based billing that means a high-volume Black Friday sale can push you into overage fees. Krom Automation has no per-task or per-execution fees at any tier.

You can also download the free plugin from the WordPress.org plugin directory and test the builder before committing to Pro.

Also from wpRigel

Pollify is wpRigel’s Gutenberg-native poll, survey, and quiz plugin. Polls are built as real blocks inside the editor, which means no shortcodes to paste and no separate interface to configure. If you want to survey your Black Friday buyers on why they joined or what they want next, Pollify handles it without leaving the block editor.

Commandify is a command palette for the WordPress admin. Press Cmd or Ctrl plus K to jump anywhere in the admin, search posts, pages, users, and WooCommerce orders, and run admin actions without clicking through menus. It is the only WordPress command palette with real WooCommerce order, product, and customer management built in, which makes it useful on days when your Black Friday order volume is high and you need to move fast.

FAQ

Does the free version of Krom Automation support MemberPress or LearnDash triggers?

No. MemberPress and LearnDash integrations, including their triggers, are Pro features.

The free plugin includes 16 triggers covering WordPress users, posts, comments, media, and WooCommerce orders. Pro adds 80 or more additional triggers covering membership platforms, LMS platforms, form plugins, and more.

Can I run the Black Friday welcome sequence and my standard new-member sequence at the same time?

You can, but you should not. Use conditional branching to check whether the buyer has the Black Friday tag before the standard welcome workflow fires, and pause or disable the standard sequence for the sale window. The conditions and branching documentation shows how to set up Yes and No paths based on user meta or tags.

What happens if a workflow fails during the sale?

Krom Automation logs every execution with a full per-step audit trail. Failed executions trigger an email notification to the address you configure, and the plugin retries automatically with configurable backoff.

You will know about a failure within minutes, not days. For more on silent failures and how to catch them, see when an automation fails silently on WordPress.

Can I use Krom Automation to automatically enrol a buyer in multiple courses?

Yes. A single trigger can connect to multiple action nodes on the canvas. If a buyer purchases a bundle, one workflow can enrol them in three courses, tag them in your CRM, send a welcome email, and post a team notification to Slack, all from a single Order Completed trigger.

How do I handle buyers who miss the deadline and ask for the deal anyway?

This is a manual decision, not an automation one. What automation can do is capture those requests cleanly.

An incoming webhook or a contact form connected to a Krom workflow can log the request, tag the user in your CRM, and notify your team. The incoming webhook receiver documentation covers how to set up a unique endpoint for this kind of intake.

Is there a workflow template for Black Friday membership onboarding?

Krom Automation ships with 20 free workflow templates and 101 Pro templates across categories including e-commerce, membership, and LMS. The template library is the fastest starting point. You can import a template, customise the delay timings and email copy for your Black Friday context, and have a working workflow in under 30 minutes.

The free plugin is available now at the WordPress.org plugin directory. Pro plans start at $69 a year. Compare all three plans and choose the right one for your site count.

You can automate a Black Friday sale for digital products and licenses using Krom Automation connected to Easy Digital Downloads. The free plugin handles post-purchase emails, customer tagging, and basic follow-up. You will need the Pro plan to unlock the EDD integration triggers, the visual email builder, and scheduled renewal offer sequences.

Black Friday 2026 falls on November 27. If you want everything tested and running before then, setup should start no later than November 10.

Most automation content for Black Friday focuses on marketing flows: cart abandonment emails, countdown timers, ad retargeting. That is useful, but it skips the part that actually breaks under volume: the delivery side.

When 200 people buy your plugin in four hours, every license email, welcome sequence, and customer tag needs to fire correctly without you watching a dashboard. This article covers that gap, specifically for plugin and software sellers running Easy Digital Downloads.

The workflows below are built for solo founders and small teams who need their sale to run itself. If you have never set up automation on your WordPress site before, the Krom Automation concepts guide is the fastest way to get oriented before you start building.

Browse the full Krom Automation feature list to see what is available at each tier before committing to a plan.

What Does a Fully Automated Digital Product Sale Actually Include?

Marketing automation handles the campaign. Delivery automation handles the result. For a digital product seller, the delivery side means every customer gets their license, receipt, onboarding email, and any follow-up offer without a human triggering any of it.

A complete Black Friday automation stack for digital products covers six areas:

• Purchase confirmation and license delivery triggered the moment EDD marks an order complete
• Customer tagging in your CRM or email tool so Black Friday buyers are segmented from regular buyers
• Onboarding sequence starting 24 to 48 hours after purchase, covering setup and first-use steps
• License renewal offer scheduled 11 months out, timed before the renewal invoice arrives
• Upsell or cross-sell sent 3 to 7 days post-purchase, when the customer has had time to use the product
• Cyber Monday follow-up for customers who bought on Black Friday and qualify for an extended deal

Every one of these is a workflow in Krom Automation. Each runs once per customer, fires in the background via Action Scheduler, and logs every step so you can see exactly what happened if anything goes wrong.

The delivery side is where Black Friday breaks. Not the campaign.

The campaign runs fine. It is the 200 license emails that need to send in four hours without a queue backup that causes problems.

Which Workflows Need the Free Plugin and Which Need Pro?

Understanding the tier boundary before you build saves you from getting halfway through a workflow and hitting a paywall. Here is the honest split:

Workflow	Tier required	Why
Send welcome email on EDD purchase	Pro	EDD triggers are a Pro integration
Tag customer in FluentCRM on purchase	Pro	FluentCRM action is a Pro integration
Subscribe buyer to Mailchimp list	Pro	Mailchimp action is a Pro integration
Schedule renewal offer email 11 months out	Pro	Requires schedule trigger and delay beyond free units
Send email via HTTP Request to any external API	Free	HTTP Request action is included free
Create a WordPress user on first purchase	Free	Create User action is included free
Post a Slack alert when a high-value order completes	Pro	Slack integration is Pro
Log purchase data to Google Sheets	Pro	Google Sheets integration is Pro

The short version: if your trigger is an EDD event, you need Pro. The free vs Pro comparison has the complete breakdown across all 96+ triggers and 81+ actions.

Pro plans start at $69 a year for a single 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.

How to Set Up the Core EDD Purchase Workflow

The anchor workflow is the one that fires the moment EDD marks a payment complete. Everything else builds on top of it. The Easy Digital Downloads integration documentation lists every available EDD trigger and action with the exact field names.

The workflow shape is straightforward:

1. Trigger: EDD Payment Completed (fires once per completed order, not per item)
2. Action 1: Send Email using the visual email builder, inserting the customer name, product name, and license key via merge tags
3. Action 2: Tag the customer in FluentCRM or Mailchimp as a Black Friday buyer
4. Action 3: Add a delay of 24 hours, then send the onboarding email covering first setup steps
5. Action 4: Add a delay of 5 days, then send the cross-sell or upgrade offer

Merge tags are what make the license email personal at scale. The customer name, purchase date, product name, and any custom EDD fields can all be injected dynamically, so every email reads as if it was written for that person specifically. Using static text in a license delivery email that fires 200 times in four hours is how you end up with “Hi {first_name}” in 200 inboxes.

Enable run once per entity on this workflow. Without it, a customer who accidentally submits twice, or whose payment processor sends a duplicate webhook, will receive two license emails. That creates a support ticket every time it happens.

Run once per entity is not an optional setting on a sale workflow. It is the difference between a smooth Black Friday and a morning full of confused duplicate-email replies.

How Do I Tag Black Friday Buyers Separately From Regular Customers?

Tagging matters because your Black Friday buyers are a distinct segment. They paid a discounted rate, they have different renewal expectations, and they respond differently to upgrade offers. Lumping them with full-price buyers produces worse results in every follow-up campaign.

The tagging step sits inside the same EDD purchase workflow, immediately after the license email fires. You have two options depending on your email tool:

• FluentCRM: use the Add Tag to Contact action and apply a tag like “bf2026-buyer”. The FluentCRM integration documentation covers the exact field mapping.
• Mailchimp: use the Add Tag to Subscriber action. The Mailchimp integration documentation explains how to map EDD customer data to Mailchimp fields.
• ActiveCampaign: tag the contact and optionally trigger an ActiveCampaign automation from the same action. See the ActiveCampaign integration docs for setup.
• ConvertKit: tag the subscriber and add them to a Black Friday sequence directly from the workflow. The ConvertKit integration documentation has the subscriber field mapping.

If you want a deeper walkthrough of the tagging step specifically, this post on tagging Black Friday customers in Mailchimp and FluentCRM covers it in more detail.

How Do I Automate License Renewal Offers for Annual Subscriptions?

This is the workflow most sellers skip, and skipping it costs real money. A customer who bought a discounted annual license on Black Friday 2026 has a renewal coming in November 2027. If your first contact is the invoice, your renewal rate will be lower than if you send a warm offer 2 to 3 weeks before the invoice arrives.

The renewal offer workflow uses Krom Automation’s schedule trigger, which is a Pro feature. The setup has three steps:

1. Trigger: EDD Payment Completed (same as the main workflow, but this is a separate workflow)
2. Delay: 335 days, which puts the email roughly 30 days before the annual renewal date
3. Action: Send Email offering an early renewal at a loyalty rate, or a coupon generated by EDD’s built-in coupon system

The delays and scheduling documentation explains how to configure delays in days and how Krom Automation handles long-running delayed workflows without them expiring. The delay is stored in the database, not in memory, so a 335-day delay survives server restarts and plugin updates.

One honest limit to flag: long delays depend on WP-Cron firing reliably. On sites with consistent traffic this is not an issue. On a low-traffic staging site or a site with no visitors overnight, WP-Cron can fire late.

If your site gets fewer than a few hundred visits a day, configure a real server cron to call wp-cron.php on a schedule. Your host’s control panel or a service like Cronitor handles this in under five minutes.

What Is the Setup Timeline Before Black Friday?

Black Friday is November 27, 2026. Cyber Monday is November 30. Here is a realistic countdown for a seller starting from scratch:

Date	Task	Time required
November 3	Install Krom Automation Pro, connect EDD integration	30 minutes
November 5	Build the core purchase workflow with license email and tagging	1 to 2 hours
November 7	Build the renewal offer workflow with 335-day delay	45 minutes
November 10	Write and design emails using the visual email builder	2 to 3 hours
November 14	Run all workflows through the simulator, fix any issues	1 hour
November 17	Place a real test purchase to confirm live execution	30 minutes
November 21	Review execution logs, confirm email deliverability	30 minutes
November 27	Sale opens. Workflows run without your involvement.	0 minutes

The simulator is the step most people skip and most regret skipping. Testing with the workflow simulator lets you run a full dry-run against real data with zero side effects. No emails send, no tags apply, no records change.

You see exactly what each step would do, which fields it would populate, and whether any branch condition is misconfigured. Running the simulator is the difference between discovering a broken merge tag on November 14 and discovering it on November 27.

Will Automation Break Under Black Friday Traffic?

Krom Automation runs on Action Scheduler, which is the same background job system used by WooCommerce. Workflows do not execute during page loads.

A purchase triggers the workflow, Action Scheduler queues the jobs, and they process in the background regardless of how many people are on the site at once. A spike to 500 concurrent visitors does not cause workflows to back up or fail.

What can cause failures is an overwhelmed SMTP server. If you are sending license emails through your web host’s default mail function and 200 purchases happen in two hours, expect delivery problems.

Use a transactional email service such as Postmark, Mailgun, or Amazon SES for anything that matters. This post on whether Black Friday traffic breaks WordPress automations covers the infrastructure side in more detail.

Failure notifications are built into Krom Automation. If a workflow step fails, you receive an email alert, and the workflow retries automatically with configurable backoff. You will know within minutes if something is wrong, rather than discovering it in the support inbox two days later.

Krom Automation failing silently is not a risk. Every failed step generates an alert and an automatic retry. The risk is your SMTP provider rate-limiting you at 300 sends per hour when you have 500 orders to confirm.

How Does Zapier Compare for This Use Case?

Zapier can connect EDD to email tools and CRMs, but the cost model is a significant problem for a Black Friday sale. Zapier’s Professional plan costs around $240 a year for 750 tasks a month at the time of writing, with task-based billing and overage charges.

A sale that generates 400 orders, each triggering a 3-step workflow, consumes 1,200 tasks in a single day. That is a billing event, not just a usage spike.

Krom Automation charges no per-task or per-execution fees at any tier. A $69-a-year plan handles 50,000 workflow executions the same as it handles 50.

For a digital product seller running a once-a-year peak sale, that model is straightforwardly better. This breakdown of what Zapier actually costs during Black Friday has the numbers worked out in detail.

The other difference is where your data lives. Zapier processes your customer data, purchase events, and license information on Zapier’s servers. Krom Automation stores everything in your own WordPress database, which matters if your customers are in a jurisdiction with strict data handling requirements.

What Does Not Transfer Automatically, and What You Must Set Up by Hand

This is the section the marketing pages leave out. Know these limits before your sale starts:

• License key content: Krom Automation can trigger and send the license email, but it does not generate license keys. EDD’s licensing extension generates the key. Krom reads it as a merge tag and inserts it into the email. If EDD’s licensing extension is not active and configured, the merge tag will be empty.
• Coupon creation: Krom Automation Pro includes a Create Coupon action for WooCommerce, but EDD uses its own discount system. Discount codes for EDD need to be created in EDD before the workflow runs, then referenced statically in the email. Krom cannot create EDD discounts dynamically.
• Existing customers: Workflows trigger on new events. If you want to send a renewal offer to customers who bought last Black Friday and are not yet in any workflow, you need to import or manually trigger that segment. The schedule trigger does not backfill historical purchases.
• Email deliverability: Krom handles the trigger and the send instruction. Whether the email arrives in the inbox depends on your SMTP setup and your sender reputation. A transactional email provider is strongly recommended.
• Refund handling: there is no automatic workflow reversal if a customer refunds. If you tagged a customer in your CRM on purchase, you need a separate workflow triggered by EDD’s refund or payment reversal event to remove the tag or revoke access.

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 builder to open. If you want to run a post-sale satisfaction survey or a pre-launch product poll, it works exactly like writing a paragraph.

Commandify is a command palette for the WordPress admin. Press Cmd or Ctrl and K to open it, then type to jump anywhere, search any content, or run admin actions without clicking through menus. The only command palette plugin with real WooCommerce order, product, and customer commands built in, which makes it useful during a busy sale when you need to check an order status in seconds.

Frequently Asked Questions

Do I need the Pro version of Krom Automation to automate Easy Digital Downloads?

Yes. EDD triggers are part of the Pro integration set.

The free plugin does not include EDD triggers or the email marketing integrations you need for tagging buyers. Pro starts at $69 a year for one site, or $199 as a lifetime payment.

How do I make sure each customer only receives one license email, even if EDD fires the event twice?

Enable run once per entity in the workflow settings. This is a free feature available on all workflows. It prevents the workflow from executing a second time for the same customer, even if the trigger fires again due to a duplicate webhook or a payment processor retry.

Can I use Krom Automation to send license emails if I am not using EDD’s licensing extension?

Yes, but the license key merge tag will be empty if EDD has not generated a key. You can still use Krom to send the purchase confirmation and onboarding emails. The license key delivery requires EDD Licensing or a compatible licensing plugin to generate the key first.

What happens to the 335-day renewal delay if I update or deactivate Krom Automation?

Delays are stored in the database as Action Scheduler jobs, not in memory. Deactivating and reactivating the plugin does not cancel pending delayed actions. Uninstalling the plugin and its data would remove them, but a standard update or temporary deactivation does not affect scheduled workflows.

Can I give existing customers early access to my Black Friday deal before the public sale opens?

Yes. Use a schedule trigger set to a date and time before your public sale, with a condition that checks whether the customer’s purchase history or CRM tag qualifies them for early access. This post on giving best customers early access to Black Friday deals has a step-by-step example.

How do I handle Cyber Monday follow-up for customers who already bought on Black Friday?

Build a separate workflow triggered by the schedule trigger, set to fire on November 30, with a condition excluding anyone tagged as a Black Friday buyer from receiving the same offer twice. The Cyber Monday follow-up email guide covers the exact branching logic.

The Verdict

If you sell plugins, software, or digital downloads through Easy Digital Downloads and you are still manually sending license emails or checking orders on Black Friday, you are spending time that should be spent on nothing. A fully automated sale takes 6 to 8 hours to set up, runs without you, and handles 500 orders exactly as reliably as it handles 5.

The case for Krom Automation over Zapier for this use case is straightforward: no per-execution billing, self-hosted data, and native WordPress integration that does not route your customer’s purchase data through a third-party server. The case for starting with the simulator before the sale opens is equally simple: two hours of testing on November 14 prevents a bad day on November 27.

The free plugin is a useful starting point if you want to explore the workflow builder before committing. Download the free version from the WordPress.org plugin directory and build your first workflow today. When you are ready to connect EDD and your email tool, see the Pro pricing and compare all three plans before Black Friday gets any closer.