You can get an instant WooCommerce high value order notification using Krom Automation. Set the trigger to Order Created or Order Completed, add a conditional branch that checks order total, and point the Yes path at an email, Slack message, Telegram alert or Twilio SMS.

The free plugin covers email alerts. Slack, Telegram and Twilio SMS require Krom Automation Pro, which starts at $69 a year.

Black Friday is November 27, 2026. Cyber Monday follows three days later on November 30. During those 96 hours, a $3,000 order sitting unacknowledged for 40 minutes is a real risk.

Standard WooCommerce order emails arrive when they arrive, assuming the spam filter cooperates. A dedicated alert channel changes that. Your team knows within seconds, not minutes.

This guide covers the full setup: trigger selection, condition logic, channel options, tiered routing for different order thresholds, a setup timeline counting back from Black Friday, and how to stress test everything with the workflow simulator before the sale starts.

Browse the full feature list to see every trigger and action included in the free plugin and Pro.

Why Default WooCommerce Order Emails Are Not Enough on Peak Days

WooCommerce sends an admin order notification email for every order by default. On a slow Tuesday that is fine.

On Black Friday, when 200 orders arrive in 4 hours, the signal-to-noise ratio collapses. A $4,500 wholesale order looks identical in the inbox to a $12 single-item order.

The second problem is delivery. Shared hosting under high load throttles outbound mail.

Transactional emails on busy days are the first thing to queue and the last thing to clear. A notification that arrives 90 minutes after the order was placed is not a notification, it is a log entry.

An alert that arrives 90 minutes after a $4,000 order is not a notification. It is a log entry nobody acted on.

Third, standard order emails go to one address: the admin email. If you want a sales manager to see orders above $1,000 and an account director to see orders above $5,000, you cannot express that in native WooCommerce without custom code.

What You Need Before You Start

Before building the workflow, confirm these are in place:

• Krom Automation free plugin installed on your WooCommerce site. Follow the installation guide if you have not done this yet.
• WooCommerce active on the same site. Krom’s WooCommerce triggers only appear when WooCommerce is detected.
• Krom Automation Pro if you want Slack, Telegram or Twilio SMS. The free plugin covers email only.
• API keys ready for whichever messaging service you choose. Krom never marks up API costs. You pay your provider directly at standard rates.
• A real server cron configured on shared or budget hosting. WP-Cron fires on page load. On a low-traffic staging environment, a cron-triggered delay action could sit for hours. The delays and scheduling documentation explains how to set this up correctly before Black Friday.

How to Build the High Value Order Notification Workflow

Building a workflow in Krom Automation follows the same shape every time: pick a trigger, add conditions, then add actions on each branch. Here is the exact path for a high value order alert.

Step 1: Choose the Right Trigger

Krom Automation includes two WooCommerce triggers in the free plugin: Order Created and Order Completed. Order Created fires the moment a customer submits the order, before payment clears. Order Completed fires when fulfilment is marked done.

For a real-time alert on a big purchase, Order Created is the right choice. You want to know before you start picking and packing, not after.

Step 2: Add a Conditional Branch on Order Total

After the trigger, add a conditional branch. Set the condition to check order total. Set the threshold to whatever your “high value” floor is, for example $500, $1,000 or $2,500 depending on your typical order size.

The Yes path fires when the order meets or exceeds that amount. The No path can be left empty or used for standard handling. The conditions and branching documentation covers every operator available, including greater than, less than and between.

Step 3: Add the Alert Action on the Yes Path

On the Yes branch, add whichever action fits your team’s workflow:

• Send Email (free): fires immediately, using your SMTP or transactional mail provider. Use merge tags to pull in order total, customer name, order ID and product list so the email body carries real data, not a generic alert. The merge tags documentation lists every WooCommerce field available.
• Slack message (Pro): posts directly to a channel or a DM. A $3,200 order notification in #high-value-orders is visible to the whole fulfilment team without anyone checking email.
• Telegram alert (Pro): useful for store owners managing fulfilment from a phone. Telegram delivers in under 2 seconds on a good connection and does not end up in a spam folder.
• Twilio SMS (Pro): the right choice when someone needs to be reached regardless of whether they have a data connection. SMS delivery is more reliable than app notifications in poor signal areas like warehouses.

All four messaging channels are covered in the messaging integrations documentation for Slack, Discord, Twilio and Telegram.

Tiered Routing: Sending Different Alerts to Different People

This is the gap none of the competing guides address. A single threshold sends one alert to one place.

Tiered routing uses nested conditional branches to escalate based on order size. Here is the structure:

1. Trigger: Order Created
2. Branch 1: Order total is greater than or equal to $500. Yes path continues. No path exits.
3. Branch 2 (on the Yes path): Order total is greater than or equal to $2,000. Yes path notifies the account director. No path notifies the sales manager.
4. Branch 3 (optional, on the second Yes path): Order total is greater than or equal to $5,000. Yes path triggers a phone call via Twilio or a high-priority Slack alert in a separate escalation channel.

The result is a three-tier system. Orders between $500 and $1,999 alert the sales manager. Orders between $2,000 and $4,999 alert the account director.

Orders at $5,000 or above trigger both a Slack post and an SMS. Every recipient gets only the alerts relevant to their role. No one is buried in volume.

Tiered routing is the difference between a notification system and a genuine escalation policy. Most stores have neither.

A VIP Order Workflow: Beyond the Alert

A high value order notification is the first step. The full VIP order workflow does more than alert. It handles follow-up automatically so nothing falls through during a high-volume sale.

Here is what the extended workflow looks like after the initial alert fires:

• Alert action: Slack or SMS fires within seconds of the order.
• Tag the customer: Update User Meta or, with a CRM connected, add a tag like “VIP” or “High Value” to the customer record. This feeds future segmentation without manual work.
• Create a coupon: Krom’s Create Coupon action can generate a personalised thank-you discount code and attach it to a follow-up email. Sending Black Friday coupon codes automatically covers this exact pattern.
• Delayed follow-up: Use a delay of 2 days, then send a personalised check-in email using merge tags to reference the original order. This runs via Action Scheduler in the background, so the page load that triggers the workflow is long over by the time the follow-up fires.

The visual workflow builder makes this branching structure easy to read and audit. You can see the entire logic on one canvas rather than reading a list of rules.

Plan Comparison: Free vs Pro for High Value Alerts

What you need	Free plugin	Pro (from $69/year)
Email alert when order exceeds threshold	Yes	Yes, plus visual email builder
Conditional branch on order total	Yes	Yes, with extended operators
Slack or Discord notification	No	Yes
Telegram alert	No	Yes
Twilio SMS	No	Yes
Tiered routing to multiple recipients	Yes (email only)	Yes, any channel combination
Workflow simulator for dry run testing	Yes	Yes
Execution logs with per-step audit trail	Yes	Yes
Failure notifications and automatic retry	Yes	Yes

Cost Comparison at Black Friday Scale

Option	Year 1 cost	Year 2 cost	Per-task billing	Self-hosted data
Krom Automation free (email only)	$0	$0	No	Yes
Krom Automation Pro (Slack, SMS, Telegram)	From $69/year	From $69/year	No	Yes
Uncanny Automator (as of September 2026)	From $199/year	From $199/year	No	Yes
Zapier Professional (as of September 2026)	Around $240/year	Around $240/year	Yes, 750 tasks/month then overage	No

Zapier’s task-based billing is the critical difference at scale. On Black Friday, 800 orders across two days pushes a 750-task-per-month plan into overage territory immediately. Krom Automation has no per-task or per-execution billing at any tier.

Black Friday Setup Timeline

Work backwards from November 27. Here is the schedule we recommend:

• November 10 (17 days out): Install Krom Automation and activate Pro if you need Slack, Telegram or SMS. Configure your messaging API keys. The Pro installation guide covers the activation steps.
• November 13 (14 days out): Build the high value order workflow. Set your threshold, build your branches, write your alert message bodies using merge tags.
• November 17 (10 days out): Run the workflow simulator. The simulator documentation explains how to fire a dry run with zero side effects. Confirm the correct branch fires for an order of $499, $501, $1,999 and $2,001 if you are using tiered thresholds.
• November 20 (7 days out): Place a real test order on your store. Confirm the alert arrives in Slack, Telegram or SMS within 30 seconds. Check the execution log to verify per-step status. Fix any delivery issues before the volume arrives.
• November 24 (3 days out): Final check. Confirm server cron is configured if you are on shared hosting. Review failure notification settings so your team is alerted if a workflow errors under load.
• November 27 (Black Friday): Workflows running. Monitor the analytics dashboard. Total executions, failed execution count and the execution trend chart are all visible without opening individual workflow logs.

The broader Black Friday automation picture, including abandoned cart recovery and post-sale sequences, is covered in how to automate your WooCommerce store for Black Friday.

Testing with the Workflow Simulator Before the Sale

The workflow simulator lets you fire a dry run using real order data without triggering any action. No Slack message is sent. No SMS fires.

No coupon is created. You see exactly which branch the workflow takes and whether the condition logic evaluates correctly.

This matters more on Black Friday than any other day. A condition that evaluates on the wrong field, a merge tag that returns an empty string, or a Slack webhook URL that has expired will fail silently unless you have tested it.

Silent automation failures during a sale are expensive. When an automation fails silently on WordPress covers how to catch these before they cost you.

Testing on a quiet Wednesday is free. Discovering a broken condition on Black Friday afternoon costs real money.

After the dry run, check the execution log. Every step shows its status, the data it received and the data it passed forward. If a condition branch is evaluating against the wrong value, it is visible in the log within 30 seconds of the test run.

What to Watch for on the Day

Even a correctly built workflow can encounter issues under Black Friday volume. Here is what to watch:

• WP-Cron timing on shared hosting: If your site goes quiet between order bursts, delayed actions may fire late. A real server cron eliminates this. Set it up before the sale, not during.
• Slack rate limits: Slack’s API has a per-channel rate limit of 1 message per second by default. If 50 orders arrive in 30 seconds, some messages will queue. This is a Slack constraint, not a Krom constraint. Consider posting a summary rather than one message per order at extreme volume.
• Twilio SMS delivery: Twilio charges per SMS segment. A message body over 160 characters splits into two segments and costs twice as much. Keep your SMS alert body under 120 characters to stay safe. Pull only the essential merge tags: order ID, total and customer name.
• API key expiry: Messaging API keys do not expire on a schedule, but they can be invalidated if you rotate credentials elsewhere. Verify all keys are live during your November 20 test.

Also from wpRigel

Pollify is wpRigel’s Gutenberg native poll, survey and quiz plugin. Polls are built as real blocks inside the block editor, so there are no shortcodes to paste and no separate configuration interface to manage. It is a natural fit for post-purchase feedback or Black Friday promotion voting.

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

It is the only command palette with genuine WooCommerce depth: you can search orders by number, edit products, update stock and manage customers all from the keyboard. On a high-volume sale day, that speed compounds.

Frequently Asked Questions

Does the free version of Krom Automation support order total conditions?

Yes. The free plugin includes the Order Created and Order Completed triggers, conditional branching, and the Send Email action.

You can build a complete high value order email alert with a threshold condition at no cost. Slack, Telegram and Twilio SMS require Pro.

What WooCommerce data can I include in the alert message?

Merge tags let you pull in order ID, order total, customer name, customer email, billing address, shipping address, product list and order status. The merge tags documentation lists every available field. These work in email bodies, Slack messages and SMS text.

Can I notify different people for different order amounts?

Yes. Use nested conditional branches: one branch checks whether the order exceeds $500, and a second branch on that Yes path checks whether it exceeds $2,000.

Each branch can point to a different recipient or channel. The conditions and branching documentation covers nested logic in full.

Will high order volume on Black Friday cause alerts to miss or delay?

Krom Automation runs actions via Action Scheduler in the background, so no alert blocks a page load. The main timing risk is WP-Cron on low-traffic shared hosting.

Configure a real server cron before the sale and test it during your November 20 dry run. On high-traffic production sites this is not typically an issue.

Do I need a separate plugin for Slack or SMS alerts?

No. Slack, Telegram and Twilio SMS are built into Krom Automation Pro as native actions.

You connect your API credentials in the Krom settings, then select the action on the workflow canvas. No additional plugin is required.

What happens if the workflow fails during the sale?

Krom Automation sends an email failure notification and retries automatically with configurable backoff. Every failed execution appears in the execution log with a per-step trace so you can see exactly where the failure occurred.

Silent automation failures are the most common Black Friday risk. The retry and logging system is there specifically to surface them.

Our Verdict

If your store sees orders above $500 regularly and you are managing fulfilment with more than one person, a conditional notification workflow is not optional infrastructure. It is the difference between reacting to big orders and missing them until someone checks the dashboard an hour later.

The free plugin covers the email path completely. That is enough for a solo operator running a straightforward store. Agencies managing high-volume client stores, or any store where a single missed $3,000 order costs more than a year’s Pro licence, should be on Pro before Black Friday.

See full pricing details and the 14-day money-back guarantee, then get the workflow live and simulator-tested before November 24. The free plugin is available on the WordPress.org plugin directory with no trial period and no run caps.

You can send Black Friday coupon codes automatically using Krom Automation and WooCommerce. The free plugin creates coupons and sends email.

To deliver codes through Mailchimp, FluentCRM or ActiveCampaign, you need Krom Automation Pro, which starts at $69 a year. Build the workflow once, test it with the simulator, and every qualifying customer gets their own unique code without you touching a thing on November 27, 2026.

Most Black Friday coupon failures are not coupon problems. They are delivery problems.

A single shared code leaks to coupon sites within hours, unlimited-use codes bleed margin all weekend, and a manually-sent batch email misses anyone who joined the list after you hit send. Automating the full sequence, from code creation to delivery to expiry enforcement, closes all three gaps at once.

This guide covers the exact workflow structure, the setup timeline counting back from Black Friday, how to connect the right email channel, and what to watch when the campaign is live.

Browse the full feature list to see what triggers and actions are available before you start building.

What Does “Sending Coupon Codes Automatically” Actually Mean?

There are two distinct things people mean when they ask this question, and they require different setups. The first is a bulk send: one email blast to your whole list, all at the same time, with one shared code. The second is a triggered send: each subscriber or customer gets their own unique code when something happens, like placing a first order or joining a segment.

A shared code is simpler but carries real risk. Coupon aggregator sites index them within hours, and anyone can use them, not just your intended recipients. A unique-per-customer code costs slightly more to set up but eliminates sharing entirely and gives you trackable usage data per customer.

Krom Automation handles both approaches. The free plugin can generate a unique WooCommerce coupon and send it via WordPress email in a single workflow. Pro adds Mailchimp, FluentCRM and other ESP connections so the code lands in a properly branded campaign rather than a plain transactional email.

Quick Summary

Delivery Method	Free or Pro	Unique Code Per Customer	Branded Email Template
WordPress Send Email action	Free	Yes, via Create Coupon + merge tag	No, plain text
Mailchimp via Krom integration	Pro	Yes	Yes
FluentCRM via Krom integration	Pro	Yes	Yes
HTTP Request to any ESP API	Free	Yes, requires API mapping	Depends on ESP

How Does the Create Coupon Action Work?

The Create Coupon action in Krom Automation talks directly to WooCommerce. When it fires, it creates a new coupon in your WooCommerce dashboard with whatever parameters you configure on the action node. You set the discount type, the amount, the expiry date, the usage limit and whether the code is customer-specific, all inside the workflow builder without touching a PHP file.

The action returns the generated coupon code as a dynamic value. That value is then available as a merge tag in every action that runs after it in the same workflow. So the sequence is: Create Coupon fires, generates a code like BF2026-A7X3K, and the next Send Email action inserts that exact code into the message body using the merge tag.

The customer receives their own code. Nobody else has it.

You can read exactly how merge tags work in Krom Automation before you build, because getting the tag syntax right is what makes the variable code injection reliable.

A unique code per customer is not a luxury feature. It is the only way to know whether your campaign drove a sale or whether someone found the code on a deal site.

Which Trigger Should You Use?

The right trigger depends on who you want to receive the coupon. Here are the four most useful setups for Black Friday:

• Order Completed trigger: send a Black Friday coupon to customers who complete a purchase between November 27 and November 30. Rewards buyers and encourages a second order before Cyber Monday ends.
• User Registered trigger: new accounts created during the sale period automatically receive a welcome coupon. Useful for lead-generation campaigns where registering unlocks a discount.
• Schedule trigger (Pro): fire a workflow at a specific date and time, like 00:01 on November 27, to push codes to an existing segment. This is the correct approach for a timed launch send to your full list.
• Incoming Webhook trigger (Pro): an external tool, such as your ESP or CRM, pings your site when a subscriber hits a segment condition, and Krom Automation creates and returns the coupon in real time. This is the most flexible architecture for large lists.

If you are planning a timed launch, the Schedule trigger documentation explains how to set recurring and one-time schedules so your workflow fires at exactly 00:01 on Black Friday and not a minute later, assuming a real server cron is configured.

How to Build the Workflow, Step by Step

Open Krom Automation from your WordPress admin sidebar and click Add New Workflow. The visual canvas loads on a blank state. Every step below maps to a node you place on that canvas.

1. Place your trigger node. Select Order Completed for a post-purchase flow, or Schedule for a timed list send. Configure the trigger conditions, for example, order total above $0 and order date falls within the sale window.
2. Add a Delay node if needed. For a post-purchase coupon, a 10-minute delay gives the order confirmation email time to land first. Set the delay to 10 minutes in the Delays and Scheduling panel.
3. Add the Create Coupon action node. Set discount type to percentage or fixed. For Black Friday, 20 percent is a common choice. Set usage limit to 1 per code. Set expiry to November 30, 2026, so the code dies at midnight on Cyber Monday. Enable “restrict to email” if you want WooCommerce to enforce that only the recipient can use it.
4. Add the Send Email or ESP action node. In the email body, insert the coupon merge tag where the code should appear. For Mailchimp delivery, connect the Mailchimp integration and pass the coupon value as a custom field into the campaign. For FluentCRM, the FluentCRM integration lets you tag the contact and trigger a sequence that contains the code.
5. Add a Run Once setting. Open Workflow Settings and enable Run Once Per Entity. This prevents a single customer from triggering the workflow multiple times and receiving multiple codes.
6. Save and run the simulator. The workflow simulator fires the workflow with dummy data and logs every step result without creating a real coupon or sending a real email. Check that the coupon node shows the expected parameters and that the email node shows the merge tag resolved.

The step-by-step workflow builder guide covers the exact canvas interactions and node connection method if you are building your first workflow.

Which Email Channel Should You Use?

The channel choice affects how the coupon email looks, how it gets delivered and how you track opens and clicks. Here is the honest comparison for Black Friday:

Channel	Deliverability	Branded Design	Open Tracking	Setup Effort
WordPress Send Email (free)	Depends on your SMTP setup	No	No	Under 5 minutes
Mailchimp (Pro)	High, dedicated sending infrastructure	Yes, full template builder	Yes	20 to 30 minutes
FluentCRM (Pro)	Depends on your SMTP setup	Yes, block editor templates	Yes	15 to 20 minutes
HTTP Request to any ESP (free)	Depends on ESP	Yes, if the ESP supports it	Yes, if the ESP supports it	45 to 90 minutes

For most WooCommerce stores sending to under 5,000 customers, the free Send Email action with a properly configured SMTP plugin is sufficient. For stores with larger lists or complex segments, routing through Mailchimp or FluentCRM gives you deliverability infrastructure and click tracking that WordPress email cannot match.

One warning worth naming: if you are using WordPress email without an SMTP plugin and your hosting server’s mail reputation is poor, Black Friday coupon emails will land in spam at a rate that makes the campaign pointless. Read why automated WordPress emails go to spam before you build, not after.

Deliverability is not a nice-to-have on Black Friday. An email that arrives on December 2 is not a coupon email. It is an apology waiting to happen.

Setting Expiry Dates and Usage Limits the Right Way

The Create Coupon action gives you four parameters that matter most for a Black Friday campaign:

• Expiry date: set to November 30, 2026. This is Cyber Monday and a natural end to the sale window. A coupon with no expiry that someone finds in their inbox in February is a margin problem.
• Usage limit per coupon: set to 1. This makes the code single-use, so it cannot be shared. Even if a customer posts it somewhere, it redeems once and becomes invalid.
• Usage limit per customer: set to 1. WooCommerce enforces this at checkout. The same customer cannot use the code twice by checking out from different browsers.
• Restrict to email: when enabled, WooCommerce checks that the billing email matches the email the coupon was assigned to. This is the strongest protection against code sharing and it requires the customer to be logged in or to enter the matching email at checkout.

Setting all four correctly takes about 3 minutes inside the Create Coupon node. Skipping the usage limit is the most common mistake and the one that costs the most money when a campaign runs over a 72-hour sale window.

How to Monitor the Campaign When It Goes Live

This is the section most coupon automation guides skip, and it is the one that separates a campaign that runs cleanly from one that silently fails partway through. Krom Automation’s execution log records every workflow run at the step level, so you can see exactly which coupon was created, what code was assigned and whether the email action succeeded.

Check these three things within the first 30 minutes of your campaign going live:

• Execution log: go to Krom Automation, open the workflow, and click Execution History. Every run should show a green success state on both the Create Coupon step and the Send Email step. A red step means the action failed, and the customer did not receive their code.
• Failure notification emails: Krom Automation sends an email alert when a workflow execution fails. Make sure the notification address in settings is one you check on sale day, not a shared inbox that nobody monitors on a Saturday.
• WooCommerce coupon list: go to WooCommerce, Marketing, Coupons. You should see new coupons appearing with the BF prefix you configured. If the list is not growing during the sale, the trigger is not firing.

The analytics dashboard shows total executions and failed execution count in real time. If your failed count climbs above 2 to 3 percent, pause the workflow and check the execution log before it runs further. A failed workflow that runs 1,000 times without anyone noticing is 1,000 customers who expected a code and did not receive one.

For a broader look at what can go wrong and how to catch it early, this guide on silent automation failures is worth reading before the campaign starts.

Set It Up By: A Countdown Timeline

Black Friday is November 27, 2026. Work backwards from that date and you have enough time to build, test and fix anything that breaks before the sale starts.

• By November 10: install Krom Automation and configure your trigger and Create Coupon action. Set expiry to November 30 and usage limit to 1.
• By November 14: run the workflow simulator at least 3 times with different test scenarios. Confirm the merge tag resolves correctly in the email body.
• By November 17: connect your ESP if you are using Mailchimp or FluentCRM. Send a real test email to yourself and check that the coupon code appears in the correct position and that the code exists in WooCommerce.
• By November 21: enable Run Once Per Entity, set failure notification email, and export the workflow JSON as a backup. If something breaks on November 27, you can reimport and restart in under 5 minutes.
• November 26, evening: run the simulator one final time. Check the execution log is empty and ready. Confirm the workflow is set to active.

The workflow simulator documentation explains what the dry run does and does not test, including which steps are skipped in simulation mode so you know what still needs a live test.

What Are the Real Limits of This Approach?

Krom Automation is WordPress native, so there are a few constraints worth naming before you commit to this setup.

WP-Cron timing: if you are using the Schedule trigger on a low-traffic site, WP-Cron only fires when someone visits the site. On a site that receives no visits between midnight and 8am, your 00:01 Black Friday launch fires late. The fix is a real server cron job that pings WordPress on a defined schedule.

This is a one-time server configuration and most managed WordPress hosts support it. The delays and scheduling documentation covers this constraint.

WooCommerce required: the Create Coupon and Update Order Status actions only appear when WooCommerce is installed and active. If you are running a non-WooCommerce store, those actions are not available and the coupon creation step needs a different approach, such as an HTTP Request to your commerce platform’s API.

ESP rate limits: if you are passing coupon codes to Mailchimp or FluentCRM via the integration, those services have their own API rate limits. Sending 10,000 codes in 30 seconds will hit a rate limit wall. For large list sends, space the triggers with a delay node or use the batch architecture described in the incoming webhook receiver documentation.

Building the workflow in October means you have time to discover the WP-Cron problem before it costs you the first hour of your sale.

How Much Does This Cost?

The free version of Krom Automation covers the core coupon-and-email workflow with no trial period and no run caps. You can build and run the workflow for the entire sale window at zero cost if you are using the WordPress Send Email action for delivery.

Krom Automation Pro adds the Mailchimp and FluentCRM integrations, the Schedule trigger for timed launches, and the incoming webhook receiver. Pro starts at $69 a year for a single site or $199 for a lifetime licence on one site. See the full plan breakdown to compare the annual and lifetime options across all three tiers.

For comparison, Uncanny Automator’s automation plans start from $199 a year for one site as of September 2026, and do not include a lifetime option. Zapier’s Professional plan is around $240 a year billed annually for 750 tasks a month, with task-based billing that adds up during a high-volume sale weekend. Krom Automation has no per-task or per-execution charge at any tier.

You can download the free plugin from the WordPress.org plugin directory and have the workflow running in the same afternoon.

For more on the full Black Friday automation picture, including order status updates, inventory alerts and post-sale follow-ups, see our guide to automating your WooCommerce store for Black Friday.

Also from wpRigel

Pollify is our Gutenberg native poll, survey and quiz plugin. Polls are built as real blocks inside the block editor with no shortcodes and no separate interface to learn. It is useful for post-sale feedback and NPS surveys after your Black Friday campaign closes.

Commandify gives the WordPress admin a keyboard-first command palette. Press Cmd or Ctrl plus K to jump anywhere in the admin, search orders by customer name, update product prices and run maintenance tasks without clicking through menus. It is the only WordPress command palette with real WooCommerce order, product and customer commands built in.

Our Verdict

If you are running a WooCommerce store and Black Friday is in your calendar, build this workflow now. The free plugin is enough to get a unique coupon into every qualifying customer’s inbox with zero manual work on sale day. If your list is larger than a few hundred contacts or you need branded email delivery, add Pro for $69 a year and connect Mailchimp or FluentCRM.

Who should not build this: stores not using WooCommerce, or anyone who needs automation between two external services with no WordPress involvement. Krom Automation is WordPress native, so the trigger or action needs to touch your site. If your commerce platform is entirely external, the HTTP Request action can reach it, but you will need to map the API fields yourself.

The setup takes under two hours including testing. The simulator means you can verify the workflow produces the right coupon with the right expiry before a single real customer sees it. Build it in October, test it in November, and spend Black Friday watching the execution log rather than manually copying and pasting codes.

Compare plans and start your setup before the November timeline runs out.

Frequently Asked Questions

Does the free version of Krom Automation create unique WooCommerce coupon codes?

Yes. The Create Coupon action is included in the free plugin. It creates a unique code in WooCommerce and makes that code available as a merge tag in the following Send Email action. No Pro licence is needed for this core flow.

Can I send different coupon codes to different customer segments automatically?

Yes, using conditional branching. Add a Yes/No condition node after your trigger and route different customer groups, such as first-time buyers versus returning customers, to separate Create Coupon nodes with different discount amounts. Each path generates its own code and sends its own email. The conditions and branching documentation covers the full logic options.

How do I prevent customers from sharing their Black Friday coupon code?

Set the usage limit to 1 per coupon and enable the Restrict to Email option in the Create Coupon action. WooCommerce then checks that the billing email at checkout matches the email the coupon was issued to. A code posted to a deal site will only work for the original recipient, and only once.

Will the Schedule trigger fire at exactly midnight on Black Friday?

On a high-traffic site with real server cron configured, yes. On a low-traffic site relying on WP-Cron, the trigger fires the next time a page request hits WordPress after the scheduled time. If your site receives visits continuously, the delay is negligible. If traffic drops overnight, the delay could be 30 minutes or more. Configure a real server cron job before Black Friday if timing precision matters to your campaign.

Can I track which customers actually used the coupon code I sent them?

WooCommerce records coupon usage against the order. Every coupon created by Krom Automation appears in WooCommerce under Marketing, Coupons, and the usage count updates when the code is redeemed. For richer per-customer tracking, connect FluentCRM and tag each contact when their code is used, which lets you filter your list by redemption status after the sale.

Does Krom Automation work with Mailchimp for sending Black Friday coupon emails?

Yes, with Krom Automation Pro. The Mailchimp integration lets you pass the generated coupon code as a custom merge field into a Mailchimp campaign or automation sequence. The Mailchimp integration documentation covers the field mapping and authentication steps.

You can automate your WooCommerce store for Black Friday using Krom Automation, a visual workflow plugin for WordPress. The free version covers Order Created and Order Completed triggers plus 21 built-in actions, which handles most of what you need. If you want a Schedule trigger, incoming webhooks, or email marketing integrations like Mailchimp or FluentCRM, you will need Pro, which starts at $69 a year.

Black Friday 2026 falls on November 27 and Cyber Monday on November 30. That gives you roughly four weeks from today to build, test, and run your automations, which is enough time if you start this week. The stores that struggle are not the ones with small budgets, they are the ones that set up workflows two days before and never test them.

This guide covers which triggers to use, which actions to pair them with, how to test without sending real emails, and what to automate after the sale ends. That last part is the angle almost every other resource skips entirely.

Browse the full feature list to see every trigger and action available before you plan your workflows.

Quick Summary

Workflow	Trigger	Key Action	Free or Pro?
Order confirmation + upsell	Order Completed	Send Email	Free
First-purchase welcome	Order Completed + condition	Send Email, Change User Role	Free
Low stock alert to Slack	Order Completed + condition	HTTP Request to Slack	Free
Failed payment recovery	Order Created (status: failed)	Send Email	Free
Scheduled sale price emails	Schedule Trigger	Send Email via visual builder	Pro
Post-sale Mailchimp tagging	Order Completed	Mailchimp integration	Pro
Post-BFCM re-engagement	Schedule Trigger (Dec 3)	Send Email sequence	Pro

What Should I Set Up Four Weeks Before Black Friday?

Four weeks out, your job is infrastructure, not campaigns. This is when you install and configure Krom Automation, connect your email provider, and build one test workflow end to end. Trying to build five workflows at once without a working baseline is how things break on the day.

Start with the installation guide if Krom Automation is not already active. Once it is, build a simple Order Completed workflow that sends you a plain-text notification email. This confirms your WooCommerce triggers are firing correctly and that Action Scheduler is processing jobs in the background.

Your four-week checklist, in priority order:

• Week 4 (now): Install Krom Automation, configure Action Scheduler, run one test Order Completed workflow, confirm emails arrive
• Week 3: Build your core sale workflows, order confirmation, first-purchase welcome, low-stock alert
• Week 2: Add post-sale and recovery workflows, failed payment email, Mailchimp tagging if using Pro
• Week 1: Stress test everything using the workflow simulator, fix edge cases, freeze changes
• Nov 27 to Nov 30: Monitor the execution log dashboard, do not edit live workflows
• Dec 1 onward: Run post-BFCM re-engagement sequence, reconcile inventory, review analytics

Work through these in order. Skipping to Week 2 workflows before Week 4 infrastructure is confirmed means you will not catch configuration problems until they fail silently on the actual day.

The stores that struggle are not the ones with small budgets. They are the ones that set up workflows two days before and never run a single test.

Which Triggers Should I Use for Black Friday Automation?

Krom Automation’s free version includes 2 WooCommerce triggers: Order Created and Order Completed. Those two cover the majority of what a Black Friday campaign actually needs. You can see every available trigger in the free triggers reference.

Here is how to use each one:

• Order Completed: Fires when payment is confirmed and fulfillment is marked complete. Use this for post-purchase emails, loyalty tagging, and first-purchase detection. This is your highest-value trigger because it only fires for customers who actually paid.
• Order Created (status: failed): Use conditional branching to check whether the order status is “failed” immediately after creation. This is your failed payment recovery trigger. A one-email recovery sequence sent within 30 minutes recovers a meaningful share of abandoned checkouts.
• Schedule Trigger (Pro): Fires on a date and time you define. Use this to send your Black Friday teaser email on November 25, your launch email at midnight November 27, and your last-chance email on November 30 at 6 PM. The Schedule Trigger documentation covers one-time and recurring options.
• User Registered: If you gate a Black Friday deal behind account creation, this trigger fires the moment someone signs up. Pair it with a Send Email action and a coupon code in the body.

For low-stock alerts, there is no dedicated inventory trigger in the free version. The practical workaround is a conditional branch on the Order Completed trigger: after each order, check the remaining stock count using a merge tag and branch to a Slack or email notification if it falls below your threshold. This is documented in the conditions and branching guide.

Which Actions Should I Pair With Each Trigger?

Krom Automation’s free version includes 21 built-in actions. The ones that matter most for Black Friday are Send Email, HTTP Request, Change User Role, and Update Post Field. The free actions reference lists every option with field descriptions.

Send Email is the workhorse. Use merge tags to pull the customer’s first name, order total, and order number directly into the email body. The merge tags documentation shows exactly which variables are available from WooCommerce order events.

HTTP Request lets you hit any external endpoint, including Slack’s incoming webhook URL, without a Pro integration. A five-line JSON payload to a Slack webhook is enough to get real-time low-stock and failed-payment alerts into your team’s channel. We have a full walkthrough of WooCommerce order alerts to Slack and SMS if you want the exact payload structure.

Change User Role lets you tag first-time buyers with a custom WordPress role the moment their order completes. That role can then gate loyalty pricing, exclusive content, or early access to future sales. It runs entirely inside WordPress with no external CRM required.

If you are on Pro, the Mailchimp integration and FluentCRM integration let you subscribe contacts, apply tags, and trigger sequences directly from Order Completed without an HTTP Request workaround.

How Do I Build the Four Core Black Friday Workflows?

These four workflows cover the most valuable automation ground for a BFCM sale. Build them in this order because each one teaches you something about the canvas before the next one adds complexity.

Workflow 1: Order Confirmation Email

Trigger: Order Completed. Action: Send Email. Use merge tags for first name, order number, and order total.

Add a one-line cross-sell suggestion pointing to a related product. This replaces WooCommerce’s default plain-text receipt with something that actually represents your brand.

Workflow 2: First-Purchase Welcome

Trigger: Order Completed. Add a conditional branch immediately after the trigger: check whether the customer’s total order count equals 1. The Yes path sends a welcome email with a loyalty discount code for their next purchase.

The No path ends. The step-by-step workflow builder guide shows how to add conditions to any workflow.

Workflow 3: Failed Payment Recovery

Trigger: Order Created. Add a conditional branch checking order status equals “failed”.

The Yes path waits 30 minutes using a delay action, then sends a recovery email with a direct link to the cart. Enable “run once per entity” in workflow settings so the same customer does not receive the email twice if two orders fail in the same session.

Workflow 4: Low-Stock Team Alert

Trigger: Order Completed. Add a conditional branch checking remaining stock on the purchased product. Set the threshold to whatever your reorder point is, say 10 units.

The Yes path sends an HTTP Request to your Slack webhook with the product name, SKU, and remaining quantity as merge tag values. This workflow alone saves your team from discovering a stockout on the morning of Black Friday.

A low-stock alert that fires after every order costs you nothing and prevents the one situation no discount strategy can fix: running out of stock at peak traffic.

How Do I Test Workflows Before the Sale Starts?

Krom Automation includes a workflow simulator that runs a dry-run of any workflow with zero side effects. No emails send, no Slack messages fire, no database records change. You supply the trigger data manually and the simulator steps through every node, showing you what each action would do and flagging any configuration error before it reaches a real customer.

Run the simulator on every workflow at least once before November 27. Pay particular attention to:

• Conditional branch logic: Simulate both the Yes and No paths separately to confirm each one behaves correctly
• Merge tag resolution: Check that order number, customer name, and product fields populate with real-looking values rather than empty strings
• Delay timing: Verify the delay unit is set correctly. A delay set to “30” with the unit left on “days” instead of “minutes” sends your recovery email a month late
• Run once per entity: Confirm it is enabled on any workflow that could fire multiple times for the same order or customer

The simulator documentation explains how to supply custom trigger data for WooCommerce order events specifically. Use it on November 24 or 25 at the latest. Freezing changes at least 48 hours before the sale starts is a discipline worth enforcing.

One honest constraint: workflow execution runs on Action Scheduler, which depends on WordPress Cron. On very low-traffic sites where no page loads occur for hours, WP-Cron fires late.

If your store is running a major sale, traffic will not be the problem. But if you are running Black Friday automation on a staging or low-traffic site, configure a real server cron job to call wp-cron.php on a one-minute interval.

What Should I Automate After Cyber Monday?

Almost every Black Friday automation guide stops at November 30. That is the wrong place to stop. The customers who bought from you during BFCM are your highest-intent audience for the next 90 days, and most stores do nothing with them beyond a generic December newsletter.

Here is what to build for the post-sale period:

• Re-engagement sequence (Dec 3): Use the Schedule Trigger to send a “thank you for your BFCM order” email on December 3, including a preview of upcoming holiday deals. Buyers who hear from you within a week of purchase are significantly more likely to return before Christmas.
• Review request (Dec 5 to 7): Trigger: Order Completed, with a 7-day delay action. Action: Send Email asking for a product review. Seven days gives the customer time to use the product before you ask.
• Inventory reconciliation alert: Use the Schedule Trigger set to December 1 at 9 AM to send an HTTP Request to your warehouse system or a Slack message summarising which SKUs dropped below reorder thresholds during the sale period.
• Segment buyers for January: If you are on Pro and using FluentCRM, the Order Completed trigger can apply a “BFCM 2026 buyer” tag to every customer automatically. That tag becomes your January re-engagement segment without any manual list building.

Our companion post on WordPress automations to set up before Black Friday covers the broader pre-sale preparation if you want to go deeper on timing.

The post-sale window is where most stores leave money on the table. Your BFCM buyers are warmer than any other segment you have, and the window to act is short.

Free vs Pro: Which Plan Do You Actually Need for Black Friday?

What you want to do	Free	Pro
Order Completed and Order Created triggers	Yes	Yes
Send transactional emails with merge tags	Yes	Yes
Conditional branching (first purchase, failed payment, low stock)	Yes	Yes
Delay scheduling (30-minute recovery email, 7-day review request)	Yes	Yes
Slack and SMS alerts via HTTP Request	Yes	Yes
Workflow simulator for dry-run testing	Yes	Yes
Schedule Trigger for timed campaign emails	No	Yes
Mailchimp, FluentCRM, ActiveCampaign integration	No	Yes
Visual email builder for branded transactional emails	No	Yes
Incoming webhook receiver for external triggers	No	Yes
80+ additional triggers and 60+ additional actions	No	Yes

The free version handles the four core workflows described above without restriction. You need Pro if you want timed campaign emails, native email marketing integrations, or branded transactional emails built with the visual email builder. See the free vs Pro comparison for the complete breakdown.

Pro plans start at $69 a year for one site, or $199 as a one-time lifetime payment. There is a 14-day money-back guarantee on every plan. Compare all three plans to find the right fit for your number of sites.

What Are the Real Costs of Running This Manually Instead?

If you skip automation and handle BFCM manually, here is what that actually looks like in hours. A typical BFCM weekend for a mid-size WooCommerce store involves roughly 200 to 500 orders over four days. Manually sending order follow-ups, checking stock levels, and fielding failed payment queries at that volume takes 8 to 12 hours of staff time across the weekend, at a minimum.

A developer building these workflows from scratch in custom code would charge between $500 and $1,500 depending on complexity. Krom Automation Pro for one site costs $69 a year, or $199 as a lifetime purchase. The math is not close.

If you are managing Black Friday automation across multiple client stores, the Standard plan at $149 a year covers 5 site activations. The WordPress automation across multiple client sites post covers how to structure that work efficiently.

Also from wpRigel

Pollify is wpRigel’s Gutenberg-native poll, survey and quiz plugin. If you want to run a Black Friday customer preference survey or a product feedback poll, Pollify builds it as real editor blocks with no shortcodes and no separate interface to configure.

Commandify is a command palette for the WordPress admin. Press Cmd or Ctrl plus K to search orders, switch products, update stock status, and run WooCommerce actions without clicking through menus. During a high-volume sale weekend when speed matters, it saves more time than it sounds like it would.

Our Verdict: Who Should Act on This Now?

If you are running a WooCommerce store and Black Friday is four weeks away, start with the free plugin today. Install it, build the Order Completed confirmation workflow, and confirm your Action Scheduler is processing correctly. That single step eliminates the most common failure mode: discovering on November 27 that background jobs are not running.

If you want timed campaign emails, email marketing integrations, or branded transactional emails, upgrade to Pro before November 14. That gives you two weeks to build and test the additional workflows before the sale starts. Do not upgrade on November 25 and expect to have everything working correctly by the 27th.

If you are an agency running BFCM automation across multiple client stores, the Standard plan covers 5 sites and includes every Pro feature. That is the right tier. Trying to manage client automations on individual free installs is the slower path.

Download the free plugin from the WordPress.org plugin directory and run your first workflow today. See full pricing details for Pro if you need the Schedule Trigger or integrations before November 27.

Frequently Asked Questions

Does Krom Automation work with WooCommerce Subscriptions?

Yes. The WooCommerce Subscriptions integration adds subscription-specific triggers in Pro, including renewal events and cancellation triggers. For a Black Friday subscription promotion, you can fire a workflow whenever a new subscription is created during the sale window.

Can I send emails to Mailchimp lists automatically when an order completes?

Yes, but this requires Pro. The Mailchimp integration lets you subscribe contacts, apply tags, and trigger automations directly from Order Completed. On the free version, you can approximate this with an HTTP Request action pointing to the Mailchimp API.

What happens if a workflow fails during the Black Friday rush?

Krom Automation sends a failure notification email and retries automatically with configurable backoff. Every execution is logged step by step in the execution history, so you can see exactly where a workflow failed and why. Our post on automations that fail silently explains how to catch these before they cause real problems.

Can I run the same Black Friday workflows on multiple client stores?

Yes. Krom Automation supports workflow import and export as portable JSON.

Build the workflow once, export it, and import it on each client site. You will need to update site-specific settings like email addresses and Slack webhook URLs after importing, but the workflow structure transfers completely.

Will WP-Cron cause delays during a high-traffic Black Friday sale?

On a high-traffic store during BFCM, WP-Cron fires frequently because every page load can trigger it. The risk of late execution is highest on low-traffic sites.

If your store is expecting significant Black Friday volume, WP-Cron timing is not the thing to worry about. If you are cautious, configure a real server cron job to call wp-cron.php every minute for the sale weekend.

Is there a way to test my Black Friday workflows without sending real emails?

Yes. The workflow simulator runs a complete dry-run with zero side effects.

You supply test order data and the simulator steps through every node, showing what each action would produce without actually executing it. Use it on every workflow at least once before November 27.

The eight WordPress automations every store needs before Black Friday 2026 are: order alerts to your team, low stock warnings, failed payment recovery, post-purchase review requests, VIP early access emails, Cyber Monday follow-up, post-sale teardown workflows, and a stress test run before the sale opens. Krom Automation covers all eight, and most run on the free plugin. The Schedule trigger, incoming webhook, and visual email builder require Pro, but the core order and stock workflows do not.

Black Friday 2026 falls on November 27. Cyber Monday is November 30. That gives you a hard deadline, not a rough target.

Workflows you build in October run during the quietest week of the retail year. Workflows you try to configure on November 26 get tested under real load, with real customers, with no margin for error.

This checklist is ordered by impact. Work through it in sequence. Skipping ahead to the VIP email sequence before order alerts are wired up means your team will not know an order failed while you are busy crafting subject lines.

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

Quick Summary: 8 Automations, Free vs Pro, and When to Build Each

Workflow	Free or Pro	Build by	Template available
Order alerts to team	Free	Oct 31	Yes
Low stock warnings	Free	Oct 31	Yes
Failed payment recovery	Free	Nov 7	Yes
Post-purchase review request	Free	Nov 7	Yes
VIP early access email	Pro (Schedule trigger)	Nov 14	Yes
Cyber Monday follow-up	Pro (Schedule trigger)	Nov 14	Yes
Post-sale teardown	Pro (Schedule trigger)	Nov 14	No
Simulator stress test	Free	Nov 21	N/A

Why Black Friday Breaks Manual Processes

On a normal Tuesday your store might process 20 orders. On Black Friday it might process 200, and those orders arrive in bursts rather than spread evenly through the day. Every manual step that takes 2 minutes on a quiet day takes the same 2 minutes on a peak day, except now there are 10 times as many of them and customers are watching a countdown timer.

The workflows below replace manual steps with automated responses that fire the moment a trigger condition is met, whether that is an order placed, a stock level crossed, or a payment declined. How Krom Automation works is a useful reference if you are new to the trigger-action model before you start building.

The workflows you skip in October are the ones you will spend Black Friday morning building by hand, under pressure, in front of angry customers.

Workflow 1: Order Alerts to Your Team (Build by October 31)

When an order completes, your fulfilment team needs to know within seconds, not when someone next checks the WooCommerce dashboard. The Order Completed trigger in Krom Automation fires immediately and can send a Slack message, an email, or both, with the order number, customer name and total pulled in via merge tags.

On peak days this matters because delayed fulfilment is the most common source of 1-star reviews after Black Friday. A team alert that fires 30 seconds after payment clears means picking and packing can start before the customer has closed the confirmation tab. The messaging integrations for Slack, Discord, Twilio and Telegram cover setup for each channel.

• Trigger: Order Completed (WooCommerce, free)
• Action: Send Email to fulfilment team, or HTTP Request to Slack webhook
• Merge tags to include: order number, customer name, order total, items ordered
• Template: Available in the 20 free templates under the WooCommerce category

Workflow 2: Low Stock Warnings (Build by October 31)

Running out of a bestseller at 11am on Black Friday and not knowing until a customer complains is an avoidable problem. WooCommerce does send a default low stock email, but it goes to the admin email address and carries no context about which supplier to contact or what the reorder lead time is.

A Krom Automation workflow triggered by a stock threshold can send a richer alert, route it to the right person, and log the event for reporting. Our full guide on setting up WooCommerce low stock notification emails covers the trigger configuration in detail. Set the threshold higher than you think you need it: if your reorder lead time is 3 days and you sell 50 units a day on Black Friday, a warning at 100 units remaining is not paranoid, it is arithmetic.

• Trigger: Order Completed, with a conditional branch checking remaining stock
• Action: Send Email to purchasing manager
• Condition: Stock quantity falls below your reorder point
• Template: Available in the free WooCommerce workflow templates

Workflow 3: Failed Payment Recovery (Build by November 7)

Payment failures spike on Black Friday because customers are using unfamiliar cards, hitting credit limits, or experiencing bank fraud holds triggered by an unusual large purchase. WooCommerce records these as failed orders. Without automation, they sit there until someone manually reviews the order list, which on a peak day may be never.

A workflow triggered by Order Created with a conditional branch checking for failed status can send a recovery email within 5 minutes of the failure, while the customer is still at their desk and still wants to buy. A 5-minute recovery window converts at a significantly higher rate than an email sent hours later. The conditions and branching documentation explains how to build the Yes/No logic that routes failed orders to the recovery email and successful orders elsewhere.

• Trigger: Order Created (free)
• Condition: Order status equals Failed
• Action: Send Email with payment retry link and alternative payment options
• Delay: Optional 10-minute delay before a second recovery email if status has not changed

A failed payment email sent 5 minutes after the failure recovers customers. The same email sent 5 hours later recovers receipts they have already forgotten about.

Workflow 4: Post-Purchase Review Request (Build by November 7)

Black Friday generates more orders in 24 hours than many stores see in a typical fortnight. That volume of verified purchases is a rare opportunity to build review count quickly, but only if you ask at the right time.

A review request sent immediately after an order is placed lands before the product arrives. A request sent 7 days after delivery lands when the product is fresh and the customer has formed an opinion.

Build this with a Delay of 7 days after the Order Completed trigger, then send a personalised email using merge tags to pull in the product name and order number. The delays and scheduling documentation shows exactly how to configure the delay unit so it counts from the trigger moment rather than from when the workflow was created. Enable run once per entity to prevent a customer who placed three separate orders from receiving three review requests in the same week.

• Trigger: Order Completed (free)
• Delay: 7 days
• Action: Send Email with review link, personalised with product name merge tag
• Setting: Run once per user to prevent duplicate sends

Workflow 5: VIP Early Access Email (Build by November 14, Pro Required)

Your best customers are the ones most likely to buy again, and the ones most likely to leave if a competitor gives them a better experience. An early access email sent 24 to 48 hours before the public sale opens gives VIP customers a reason to stay subscribed and rewards the behaviour you want to encourage.

This workflow uses the Schedule trigger, which is a Pro feature. You set the exact date and time the email fires, and Krom Automation handles the rest. Set it for November 25 at 9am and the email reaches your VIP segment 48 hours before Black Friday opens.

Combine it with the visual email builder to design a branded email without touching code. If you are syncing your VIP list to Mailchimp or ActiveCampaign, the Mailchimp integration and ActiveCampaign integration let you tag or segment contacts automatically when the workflow fires.

• Trigger: Schedule trigger, November 25 at 9am (Pro)
• Condition: User role equals VIP customer, or user has a specific tag in your CRM
• Action: Send Email with early access link and exclusive discount
• Template: Available in the Pro template library

Workflow 6: Cyber Monday Follow-Up (Build by November 14, Pro Required)

Cyber Monday on November 30 is 3 days after Black Friday closes. Customers who browsed but did not convert on Black Friday are warm leads with a short memory. A Cyber Monday email that references their Black Friday browsing or abandoned cart, sent automatically on the morning of November 30, catches them at a moment when they are already in a buying mindset.

This also uses the Schedule trigger. Build it alongside the VIP early access workflow in the same session, so both are live and tested before November 21. The Schedule trigger documentation covers how to configure one-time sends versus recurring schedules, which matters here because you want this to fire once and not repeat the following Monday.

• Trigger: Schedule trigger, November 30 at 8am (Pro)
• Action: Send Email to your full list or a segment of non-converters
• Merge tags: First name, last browsed product if available via your CRM integration
• Template: Available in the Pro template library

Workflow 7: Post-Sale Teardown (Build by November 14, Pro Required)

This is the workflow nobody else talks about. Every checklist covers setup. Nobody covers teardown.

On December 1 you need sale prices reverted, countdown banners removed, Black Friday coupon codes deactivated, and social posts paused. If you do this manually you will forget at least one thing, and it will stay live for days until a customer queries it.

A teardown workflow uses the Schedule trigger set for December 1 at midnight. Actions can include HTTP Requests to your banner plugin’s API to disable banners, a Change Post Status action to move Black Friday promotional posts back to draft, and an Update Post Field action to revert sale prices.

For coupon deactivation you can use the Update Order Status action combined with a coupon expiry date set in WooCommerce itself, which is simpler than an API call. There is no pre-built template for teardown because every store’s setup is different, but the step-by-step workflow builder guide walks through constructing a multi-action sequence from scratch.

• Trigger: Schedule trigger, December 1 at 12:00am (Pro)
• Actions (sequence): Change Post Status on promotional posts to Draft, HTTP Request to disable banner plugin, Update Post Field to clear sale prices
• Benefit: Nothing stays live past its end date because a human forgot to log in

The teardown is where manual processes fail most visibly. A sale price still showing on December 5 creates refund requests, not repeat customers.

Workflow 8: Team Alerts via Slack or SMS (Bonus, Free)

Beyond order fulfilment alerts, your team benefits from real-time notifications for anything that requires human attention: a very high value order that needs manual review, a refund request on a specific product category, or a spike in failed payments that might indicate a card testing attack. Each of these is a separate workflow with a different trigger condition.

The HTTP Request action in the free version supports POST requests with JSON bodies, which is all Slack’s incoming webhook needs. See our post on WooCommerce order alerts to Slack and SMS with Twilio for the exact payload structure. For SMS you will need a Twilio account, and the same HTTP Request action handles the Twilio API call directly.

What Breaks at Scale: WP-Cron and the Honest Limitation

Krom Automation runs workflows via Action Scheduler, which means nothing executes during a page load. That is the right architecture.

However, Action Scheduler depends on WordPress Cron, and WordPress Cron depends on site traffic to fire. On a low-traffic site where no visitors arrive for 2 hours, a workflow scheduled for 3pm might not fire until 5pm.

On Black Friday your traffic is not low, so this is less of a concern than on a quiet Tuesday in March. But the Schedule trigger workflows, specifically the VIP email and Cyber Monday follow-up, should have a real server cron job configured rather than relying on WP-Cron alone.

Most managed WordPress hosts provide this via their control panel in under 5 minutes. This is worth doing before November 21 so you can verify it is firing on schedule during your stress test.

How to Stress Test Before the Sale Starts (Do This by November 21)

Krom Automation includes a workflow simulator that runs a dry-run of any workflow with zero side effects. No emails are sent, no posts are changed, no Slack messages fire.

The simulator steps through each node and shows you exactly what data would flow through, where a conditional branch would route, and which merge tags would resolve to what values. Use it on every workflow in this list before Black Friday week begins.

The workflow simulator documentation explains how to load test data into the simulator and read the per-step audit output. Pay specific attention to workflows with conditional branches: a branch condition that is too narrow may route every order down the No path and silently skip all your recovery emails. Silent failures on automation are the hardest kind to diagnose under pressure, which is why we wrote a separate post on what happens when an automation fails silently.

• Run the simulator on every workflow by November 21, 6 days before Black Friday
• Check that merge tags resolve to real values, not empty strings
• Verify that conditional branches route correctly for both the Yes and No paths
• Confirm that run once per entity is enabled on any workflow that should not repeat per customer
• Check the execution log after one live test order to confirm the workflow fired and all steps completed

What Each Plan Costs Across Different Store Sizes

Store count	Free tier	Pro Basic (1 site)	Pro Standard (5 sites)	Pro Enterprise (unlimited)
1 store	$0/year	$119/year or $299 lifetime	$199/year or $499 lifetime	$369/year or $799 lifetime
5 stores	$0/year	5 x Basic = $595/year	$199/year or $499 lifetime	$369/year or $799 lifetime
10+ stores	$0/year	Not viable per-site	Not viable per-site	$369/year or $799 lifetime

For a single store running Black Friday campaigns, Pro Basic at $119 per year unlocks the Schedule trigger, visual email builder, and all 101 Pro templates. The breakeven against the Standard plan is at 2 stores.

Agencies managing 10 or more client stores should compare the Enterprise lifetime price of $799 against annual fees: year 3 and beyond is fully covered with no renewal. Compare all three plans in detail before choosing.

The Setup Timeline Counting Back from Black Friday

• October 31: Order alerts and low stock warnings live and tested
• November 7: Failed payment recovery and review request workflows live
• November 14: VIP early access, Cyber Monday follow-up, and teardown workflows built
• November 21: Simulator stress test complete on all 7 workflows, server cron confirmed
• November 25, 9am: VIP early access email fires automatically
• November 27: Black Friday opens. All workflows running in the background.
• November 30, 8am: Cyber Monday follow-up fires automatically
• December 1, 12am: Teardown workflow fires. Sale is over and cleaned up.

Also from wpRigel

Pollify is our Gutenberg native poll, survey and quiz plugin. If you want to run a post-Black Friday customer satisfaction survey or gather product feedback during the sale, Pollify adds it as a real block inside the editor with no shortcodes and no separate interface to learn.

Commandify is a command palette for the WordPress admin. Press Cmd or Ctrl plus K to jump to any order, product, customer or setting without clicking through menus.

During Black Friday when speed matters, it is the fastest way to review a flagged order or update a stock level without navigating the full WooCommerce screen. It is the only WordPress command palette with real WooCommerce order, product and customer commands built in.

Our Verdict: Who Should Act on This Now

If your store processed more than 50 orders on last Black Friday, every workflow in this list will pay for itself before Cyber Monday closes. The free plugin covers the highest-impact workflows: order alerts, low stock warnings, failed payment recovery, and review requests. Those four alone, built by November 7, will reduce manual intervention by several hours over the sale weekend.

Pro is worth adding if you want the Schedule trigger for timed emails and the teardown workflow. At $119 for a single store, the cost is recovered by one recovered failed payment or one repeat customer from the Cyber Monday follow-up.

Download the free plugin from the WordPress.org plugin directory and build the first two workflows today. The remaining six will follow naturally once you see how the canvas works.

Who should not act yet: stores that have not confirmed their hosting can handle Black Friday traffic levels. Automation adds value on a stable site.

On a site that will slow to a crawl under load, fix infrastructure first. That is a separate conversation from automation, and not one we can shortcut.

See Krom Automation pricing and choose the right plan for your store count.

Frequently Asked Questions

Does the free version of Krom Automation cover the most important Black Friday workflows?

Yes. Order alerts, low stock warnings, failed payment recovery, and post-purchase review requests all run on the free plugin. The Schedule trigger for timed VIP emails and the teardown workflow requires Pro, but those are secondary priorities.

What is the Schedule trigger and why do I need it for timed emails?

The Schedule trigger fires a workflow at a specific date and time, or on a recurring interval. It is a Pro feature. Without it, you can only trigger workflows in response to events like an order or a user action, not at a fixed point in the calendar.

Will the workflows still fire on Black Friday if my site gets a lot of traffic?

Krom Automation uses Action Scheduler to run workflows in the background, so they do not compete with page loads. High traffic actually helps WP-Cron fire on time. Configure a real server cron if you are using the Schedule trigger and want precise timing regardless of traffic levels.

How do I know if a workflow ran correctly during the sale?

Every workflow execution is logged with a per-step audit trail. The analytics dashboard shows total executions, success rate, and failed execution count. Failed workflows trigger an email notification and retry automatically with configurable backoff.

Can I run these automations on multiple WooCommerce stores?

The free plugin runs on as many sites as you like. Pro licences cover 1 site (Basic), 5 sites (Standard), or unlimited sites (Enterprise). For agencies running Black Friday campaigns across multiple client stores, the Enterprise plan is the only one that scales without per-site costs.

What happens to my workflows after Black Friday? Do I need to delete them?

You can pause any workflow without deleting it. The teardown workflow handles time-sensitive cleanup automatically on December 1. Evergreen workflows like order alerts and review requests should stay active year-round since they add value on every order, not just during the sale.

Good WordPress automation documentation is not a nice-to-have. It is the difference between a client who can operate a site independently and one who calls you every time a workflow stops firing. If you are handing over a site built on Krom Automation, this guide covers exactly what to capture, what to abstract for non-technical clients, and how to use the built-in notes field and export features as a documentation layer that travels with the site.

Most automation documentation fails because it describes what a workflow does, not why it exists or what happens when it stops. A client reading “Send Email on User Registered” learns nothing useful.

A client reading “Sends the welcome email with the login link. If this fails, new users see no confirmation and email support volume spikes” knows what to watch and when to panic.

The guide below is written for agency owners and developers handing off client sites. The same principles apply if you are building internal tooling and documenting for a team rather than a client.

Browse the full Krom Automation feature list to see what is available before you decide what needs documenting.

Why Automation Documentation Fails at Handover

The standard handover document covers credentials, hosting details, and plugin licences. It almost never covers the automation layer. That gap matters because automations are invisible when they work and catastrophic when they do not.

A silent automation failure on a WooCommerce site can mean hundreds of orders processed without fulfilment notifications. On a membership site it can mean new subscribers who never receive their access email.

Neither failure throws an error the client sees. They only surface when a customer complains, and by then the damage is done.

An undocumented automation is a liability that transfers with the site. The client inherits the risk but none of the context needed to manage it.

There are three failure modes that handover documentation must prevent:

• The trigger changes and nobody knows the workflow depended on it. A form is renamed or a post type is removed. The workflow still shows as active. Nothing fires.
• A plugin that a workflow depends on gets deactivated or updated. WooCommerce, a CRM plugin, or a forms plugin changes its hook structure. The workflow breaks silently.
• The client edits a workflow without understanding the downstream effects. They change a delay from 24 hours to 0 hours because they want emails faster. Three actions that depended on that delay window now fire simultaneously.

Good documentation does not prevent all of these. It makes each one diagnosable in under 10 minutes rather than 3 hours.

What to Document: The Non-Negotiable List

For each workflow on the site, capture the following. This is the minimum. Anything below this and the handover is incomplete.

1. Business purpose in one sentence. Not a technical description. What happens in the business if this workflow stops running?
2. Trigger: what fires it, and under what conditions. Name the exact trigger, any conditions on the trigger, and what the source is (a specific form, a specific post type, a specific user role).
3. Actions in sequence. List every action in order. Include delays as part of the sequence, not as an afterthought.
4. Dependencies. Which plugins must be active for this workflow to run? If the FluentCRM integration powers a contact tagging step, note that FluentCRM must stay active and at a minimum version.
5. Owner. Who is responsible for this workflow? Whose job breaks if it fails?
6. Last tested date and tester. A workflow that has never been tested in production is an assumption, not a fact.
7. Failure behaviour. What does the client see or not see when this fails? How do they check the execution log?

Seven fields per workflow. On a site with 12 active workflows, that is roughly 4 hours of documentation work.

A developer billing at $120/hour should charge for it, and most should. The alternative is a support ticket backlog that costs more.

Using the Krom Automation Notes Field

Krom Automation includes a notes field on every workflow, visible inside the workflow settings panel. This is not a hidden feature. It is the right place to store the business purpose and dependency information for each workflow, because it travels with the workflow when the site is handed over.

The notes field renders inside the canvas view. A client or future developer opening a workflow sees the note before they see anything else. That means documentation that lives in a separate Google Doc or Notion page, where nobody will look, becomes documentation that is impossible to miss.

The workflow settings documentation covers the notes field alongside the run-once setting, pause controls, and import/export. Read that before you build your first client workflow so the notes habit is built in from the start, not retrofitted at handover.

Our recommended note format for each workflow:

• Purpose: [one sentence business reason]
• Trigger source: [form name, post type, or event]
• Depends on: [plugin names and minimum versions]
• Owner: [name or role]
• Last tested: [date]

Paste this as plain text into the notes field on every workflow before you hand over. It takes 3 minutes per workflow and eliminates the most common support call: “We changed something and now the emails stopped. Can you look at it?”

Export as Portable Documentation

Krom Automation supports workflow export as JSON. Each exported file contains the complete workflow structure: trigger configuration, all actions, delays, conditions, merge tags, and settings. The notes field travels with the export.

For a client handover, export every active workflow and include the JSON files in the handover package alongside credentials and hosting details. This gives you three things:

• A point-in-time snapshot of every workflow as it was at handover
• A restore path if a workflow is accidentally deleted or corrupted
• A portable copy that can be imported to a staging or development environment for testing

The JSON export is also your migration safety net if the client ever moves hosts. Importing 12 workflows from JSON takes under 10 minutes. Rebuilding 12 workflows from memory takes a day.

The export file is the closest thing to version control that most WordPress automation setups will ever have. Treat it like a build artefact, not an afterthought.

Store the exports in the same place as the site backup. If the client uses a project management tool, attach the JSON files to the project closeout ticket so they are searchable later.

What to Abstract for Non-Technical Clients

Not every client needs to understand conditional branching or merge tags. Most need to understand three things: what the workflow does, what it costs them if it stops, and how to tell if it has stopped.

Build a separate one-page summary for the client. This is distinct from the technical documentation above, which is for the next developer. The client summary covers:

• Workflow name (match the name in Krom Automation exactly, so they can find it)
• What it does in plain English (two sentences maximum)
• How often it should run (on every order, daily, on new user registration)
• How to check if it is running (point them to the execution log in the analytics dashboard)
• Who to call if it stops (your support contact or their internal team)

The analytics dashboard in Krom Automation shows total executions, success rate, failed execution count, and an execution trend chart. A client who checks this once a week will catch a silent failure within 7 days. A client who has never been shown the dashboard will call you 6 weeks later wondering why conversion rates dropped.

Documenting Integrations Separately

Integrations deserve their own section in the handover document because they carry external dependencies the client controls, and those dependencies can change without warning.

For each external integration in use, document:

• Which service it connects to (Mailchimp, FluentCRM, Google Sheets, Slack)
• What credential or API key is stored in WordPress
• Who owns that credential (the agency or the client)
• What happens to the workflow if the API key is revoked or the account is closed
• Where to regenerate the credential if needed

If the site sends data to Google Sheets or Google Calendar, note which Google account owns the connection and what happens if that account loses access. If the site posts to social media via the social media integration, note the connected page, the connected account, and the token expiry behaviour.

Messaging integrations to Slack, Discord, Twilio or Telegram are particularly fragile at handover because they use workspace-level credentials the client may rotate during an internal IT change. A single paragraph in the handover document explaining this saves a support call.

For form-triggered workflows, link the integration doc so the next developer can verify the setup. For example, a workflow triggered by Gravity Forms or WPForms will break if the form is renamed or the field mapping changes. That is worth one sentence in the handover notes.

The Handover Documentation Structure

A complete handover documentation package for a site running Krom Automation has four parts. The table below shows who reads each part and what they do with it.

Document	Audience	Format	Lives Where
Workflow notes (per workflow)	Next developer	Plain text in Krom Automation notes field	Inside the plugin, travels with export
Technical handover document	Next developer or internal team	Markdown or PDF	Project folder, handover package
Client summary (one page)	Client or site owner	PDF or shared doc	Client’s preferred tool (Notion, Google Drive, email)
Workflow JSON exports	Next developer, disaster recovery	JSON files	Site backup folder, project archive

The technical handover document should list every active workflow, its dependencies, the credential owner for each integration, and the support contact. It does not need to explain how Krom Automation works. It needs to explain how this specific site’s workflows work.

Cost of Getting This Wrong

Skipping automation documentation is a pricing decision, even if it does not feel like one. The cost lands somewhere. The question is whether it lands on your support hours or on the client’s operations.

Scenario	Without documentation	With documentation
Workflow breaks 3 months post-handover	2 to 4 hours to diagnose without context. $240 to $480 in unbilled support at $120/hr	Client checks execution log, finds the failed step, calls you with the error. 30 minutes to fix
Client changes a plugin and breaks an integration	Root cause unclear. Developer rebuilds from memory. 3 to 6 hours	Dependency listed in notes. Developer restores from JSON export. Under 1 hour
New developer takes over the site	Discovery audit needed. 4 to 8 hours billed to client	Technical handover document covers it. 1 hour onboarding
API key rotated, integration breaks	Unknown which workflows are affected. Full audit required	Integration doc lists credential owner and regeneration steps. Fixed in 20 minutes

Across an agency running 20 client sites with automation, the difference between documented and undocumented handovers is realistically 40 to 80 support hours per year. At $120/hour, that is $4,800 to $9,600 in unrecoverable time.

Charging $300 to $500 per site for a documentation package at handover is not overhead. It is margin recovery.

Charging for handover documentation is not adding a line item. It is pricing the risk correctly instead of absorbing it silently in your support queue.

Testing Before You Hand Over

Documentation of an untested workflow is documentation of an assumption. Before any handover, run every workflow through the simulator.

Krom Automation includes a workflow simulator for dry-run testing with zero side effects. It runs the workflow logic without sending emails, creating posts, or firing HTTP requests. Use it to verify that every branch executes as expected and that merge tags resolve correctly.

For workflows that cannot be fully validated by simulation, such as those that depend on a live payment gateway or a production form submission, document the test procedure in the handover notes. Describe the exact steps, the expected output, and how to check the execution log to confirm it ran. The client or next developer should be able to run the test themselves in under 15 minutes.

If a workflow has never been tested in production, say so in the handover document. An honest note that says “validated in staging but not confirmed in production” is more useful than silence. It tells the next person where to start.

Multi-Site and Agency Considerations

If you are managing automation across multiple client sites, the documentation burden multiplies quickly. The answer is not to document less. It is to standardise the documentation format so each site takes less time.

We cover the broader strategy for WordPress automation across multiple client sites in a separate guide, including how to build reusable workflow templates and what to centralise versus what to configure per site. The short version: standardise the workflow structure, standardise the notes format, and export templates from your reference build rather than rebuilding from scratch for each client.

Krom Automation’s import/export system is designed for exactly this. Build a workflow on one site, export the JSON, and import it to a new client site in under 2 minutes. The notes field travels with the import, which means your documentation template travels too.

For agencies evaluating the cost model across client sites, the per-site cost analysis we published covers what automation tooling actually costs at 1, 5, 10 and 20 sites, including licence costs, time costs, and the break-even point between free and Pro tiers.

Also from wpRigel

Pollify is wpRigel’s Gutenberg-native poll, survey and quiz plugin. Polls are built as real blocks inside the block editor, so there are no shortcodes to paste and no separate interface to learn. It pairs naturally with automation workflows that trigger on user responses.

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.

For developers managing client sites, it is the fastest way to navigate without knowing every menu path. It is the only command palette with real WooCommerce order, product and customer commands built in.

Our Verdict

If you are handing over a WordPress site with active automations and you have not written workflow notes, exported the JSON files, and produced a one-page client summary, the handover is not complete. It will cost you or your client time within 6 months.

That is not a prediction. It is the pattern we see repeatedly across agency builds.

The tools to do this correctly are built into Krom Automation: the notes field, the JSON export, the execution log, the analytics dashboard, and the workflow simulator. None of them require extra setup. They require the habit of using them before you hand over, not after the first support ticket arrives.

Who should invest in this now: any agency handing over more than 3 client sites per quarter, and any developer who has ever spent a Saturday debugging an automation they built 8 months ago and cannot remember. Who can wait: teams where all automation is internal, the codebase is under version control, and the same developer maintains it indefinitely.

The free version of Krom Automation is available on the WordPress.org plugin directory with no trial period and no feature caps. If you are evaluating it for client work, start there and review the free vs Pro comparison before you decide whether the Pro integrations are worth it for your stack.

See the full Krom Automation pricing and plan details to find the right licence for your site count.

Frequently Asked Questions

Where does automation documentation live in Krom Automation?

Each workflow has a notes field inside the workflow settings panel. Text entered there travels with the workflow when exported as JSON, making it the most reliable place for handover documentation. It is visible to any developer who opens the workflow on the destination site.

What happens to workflows if a dependent plugin is deactivated?

The workflow remains active in Krom Automation but the affected triggers or actions will fail to execute. The failure is logged in the execution history with a per-step audit trail, which is how you diagnose it. Documenting plugin dependencies at handover is what makes this diagnosable in minutes rather than hours.

Can I export all workflows at once for a client handover package?

Krom Automation exports workflows individually as JSON files. For a full site handover, export each active workflow separately and bundle the files in the handover package. Each file is self-contained and can be imported to a new or staging environment without any additional configuration.

How does the workflow simulator help with handover testing?

The simulator runs the full workflow logic without executing any real actions, so you can verify trigger conditions, branch logic, and merge tag resolution without sending emails or modifying data. It is the right tool for pre-handover validation and for testing changes on a live site without side effects.

Is Pro required to use the notes field and JSON export?

No. Both the workflow notes field and JSON import/export are included in the free version of Krom Automation. You do not need a Pro licence to document and export workflows as part of a client handover.

You can connect WooCommerce to Mailchimp without Zapier using Krom Automation, a native WordPress plugin. The free version handles basic subscriber sync. The Pro version adds the Mailchimp action that subscribes contacts, applies tags, and updates audience fields directly from any WooCommerce trigger, at no per-task cost.

The official Mailchimp plugin for WooCommerce handles audience sync reasonably well, but it gives you a fixed pipeline. You cannot add conditional logic, delay the subscription, branch based on order value, or chain Mailchimp into a wider workflow. Krom Automation treats Mailchimp as one action inside a workflow you control, which means you can subscribe a customer, send an internal Slack alert, and update a Google Sheet in the same automation without touching Zapier.

This guide follows the integration post structure: what syncs, how to set it up step by step, what does not transfer, the three real failure modes, and a verdict on when this approach makes sense versus the official plugin.

Browse the full Krom Automation feature list to see what else you can connect alongside Mailchimp.

What Gets Synced: WooCommerce to Mailchimp

The table below shows every data point the Krom Automation Mailchimp integration can pass from WooCommerce to Mailchimp, and exactly where it lands in your audience. Fields not listed here do not transfer automatically and require a custom HTTP Request action or a separate workflow step.

WooCommerce Field	Where It Lands in Mailchimp
Customer email address	Audience contact email (primary identifier)
First name	FNAME merge field
Last name	LNAME merge field
Order total	Custom merge field (mapped manually in workflow)
Order status	Tag applied to contact (e.g., “order-completed”)
Product name(s)	Tag or custom merge field (one per workflow action)
Billing country	Custom merge field or audience segment data
Opt-in status at checkout	Subscribed vs. non-subscribed contact status
Workflow-assigned tag	Tag on Mailchimp contact, set per workflow branch

Order line items beyond the first product require a loop or separate action per product. There is no native array-to-tag bulk operation. If your store sells bundles with 8 to 12 line items and you need every product tagged individually, plan for that complexity before you build the workflow.

Requirements Before You Start

• WordPress 6.2 or higher
• PHP 7.4 or higher
• WooCommerce installed and active
• Krom Automation free plugin active (handles the WooCommerce triggers)
• Krom Automation Pro active (required for the Mailchimp subscribe action)
• A Mailchimp account with at least one audience created
• A Mailchimp API key with read/write access

The free Krom Automation plugin gives you the Order Created and Order Completed WooCommerce triggers at no cost. The Mailchimp action itself is a Pro integration.

See the full free vs. Pro comparison if you want to check which other actions require the Pro licence before committing.

Step-by-Step Setup

Step 1: Install and Activate Krom Automation

Go to Plugins > Add New Plugin in your WordPress admin. Search for “Krom Automation” and install the plugin listed by wpRigel. Activate it.

A new Krom Automation menu item will appear in your left admin sidebar. If you have the Pro licence, upload the Pro zip at Plugins > Add New Plugin > Upload Plugin and activate it alongside the free plugin. The Pro installation guide covers licence key activation and what to do if the Pro features do not appear after activation.

Step 2: Connect Your Mailchimp Account

Go to Krom Automation > Settings > Integrations. Find the Mailchimp card and click Connect. You will be prompted for your Mailchimp API key.

Paste it into the API Key field and click Save. Krom Automation will verify the key and display your account name if the connection succeeds. If you see a “401 Unauthorized” error, the key does not have the required audience read/write scope, generate a new one from your Mailchimp account under Account > Extras > API Keys.

Step 3: Create a New Workflow

Go to Krom Automation > Workflows > Add New. This opens the visual workflow builder canvas. Click the Add Trigger node at the top of the canvas.

From the trigger panel on the right, select the WooCommerce category, then choose Order Completed as your trigger. If you want to subscribe customers the moment they place an order rather than after payment clears, choose Order Created instead. The difference matters for refund handling, which we cover in the limitations section below.

Step 4: Add the Mailchimp Subscribe Action

Click the plus icon below your trigger node to add an action. Select the Mailchimp category from the action panel.

Choose Subscribe Contact. The action card will show the following fields, all of which are required unless marked optional:

• Audience: select your Mailchimp audience from the dropdown (populated automatically from your connected account)
• Email Address: use the merge tag {{order.billing_email}}
• First Name: use {{order.billing_first_name}}
• Last Name: use {{order.billing_last_name}}
• Status: set to Subscribed if opt-in was captured, or Pending to trigger Mailchimp’s double opt-in email
• Tags (optional): enter a static tag such as “woo-customer” or use a merge tag to apply a dynamic value

The merge tags documentation lists every available WooCommerce order variable you can inject into action fields, including order total, product names, and billing address components.

Step 5: Add Conditional Branching (Recommended)

If you only want to subscribe customers who opted in at checkout, add a Condition node between the trigger and the Mailchimp action. Click the branch icon on the trigger node. Set the condition to: Order > Customer opt-in > equals > true.

Connect the Yes path to the Mailchimp subscribe action. Leave the No path empty or route it to a different action.

This single step prevents you from adding non-consenting contacts to your audience, which matters for GDPR compliance and Mailchimp’s own terms of service. The conditions and branching documentation covers every available operator and how to stack multiple conditions in a single node.

Step 6: Test with the Workflow Simulator

Before setting the workflow live, click Simulate in the top toolbar. The simulator runs every node against a sample payload with zero side effects: no real Mailchimp contact is created, no email is sent.

You can verify that your merge tags resolve correctly and that the conditional branch routes as expected. Fix any errors the simulator flags, then click Activate to set the workflow live.

A workflow that looks correct in the builder and fails silently on real orders is the most expensive kind of mistake. Run the simulator before you activate, not after you notice missing subscribers.

What Does NOT Transfer: Honest Limitations

Most integration guides skip this section. We will not, because this is where stores waste hours debugging something that was never going to work.

• Historical orders: Krom Automation is event-driven. It fires when something happens from the moment the workflow is active. Customers who ordered before you activated the workflow are not synced retroactively. If you need to backfill 3,000 existing customers, export them from WooCommerce as CSV and import directly into Mailchimp.
• Automatic unsubscribes on refund or cancellation: The free WooCommerce triggers include Order Created and Order Completed, but not a dedicated “Order Refunded” trigger in the free tier. You can handle this in Pro with a Post Status Changed trigger on the shop_order post type, but it requires an additional workflow. Do not assume a cancelled order removes the contact from Mailchimp automatically.
• Mailchimp e-commerce data (purchase history, revenue): The Mailchimp subscribe action adds and updates contacts. It does not write to Mailchimp’s e-commerce data layer (orders, products, revenue), which the official Mailchimp plugin populates via a separate API. If you rely on Mailchimp’s purchase-based segments or revenue reporting, you need the official plugin running alongside Krom Automation, or you need to write to Mailchimp’s Orders API via the HTTP Request action.
• Abandoned cart: Krom Automation does not currently fire a trigger on cart abandonment. Abandoned cart emails require the official Mailchimp plugin or a dedicated WooCommerce abandoned cart plugin that exposes a hook Krom can listen to.
• Checkout Block opt-in checkbox: The native WooCommerce Checkout Block does not expose a Mailchimp opt-in checkbox in the same way the classic checkout does. If your store uses the Checkout Block, test the opt-in field rendering before going live. The Mailchimp official plugin has better handling of the Checkout Block opt-in at present.

For stores that need WooCommerce Subscriptions events such as subscription created, cancelled, or renewed, the WooCommerce Subscriptions integration documentation covers the additional triggers available in Pro and how to chain them into Mailchimp or any other email platform.

The official Mailchimp plugin and Krom Automation are not rivals here. For stores that need Mailchimp’s e-commerce data layer populated, running both is the honest answer.

Troubleshooting: The Three Real Failure Modes

Failure 1: Customers Appear as “Non-Subscribed” Instead of “Subscribed”

This is the most common complaint. The cause is almost always one of two things. First, the Status field in your Mailchimp subscribe action is set to Pending, which means Mailchimp sends a confirmation email and the contact stays non-subscribed until they click.

If you captured consent at checkout and want immediate subscription, change the Status field to Subscribed. Second, Mailchimp’s own audience settings may have double opt-in forced on at the audience level. Check under Audience > Settings > Audience name and defaults in Mailchimp and disable double opt-in if you want single opt-in behaviour from the API.

Failure 2: Workflow Fires but No Contact Appears in Mailchimp

Open Krom Automation > Execution Logs. Find the execution for the order in question and expand the Mailchimp action step. The log will show either a success response or the exact error Mailchimp returned.

The two most common errors are “Invalid API Key” (the key was regenerated in Mailchimp after you connected) and “Audience not found” (the audience ID stored in the action no longer matches your Mailchimp account). For the API key issue, go to Krom Automation > Settings > Integrations > Mailchimp and reconnect. For the audience mismatch, open the workflow, click the Mailchimp action node, and reselect the audience from the dropdown.

The per-step audit trail in the execution log is the fastest path to the actual error. If you have had silent failures before and want to understand why they are hard to catch, this post on silent automation failures covers the structural reasons and how to set up failure notifications.

Failure 3: Duplicate Contacts or Duplicate Emails

Duplicate contacts in Mailchimp usually mean the workflow is firing more than once per order. This happens when both Order Created and Order Completed triggers are active in separate workflows pointing to the same Mailchimp subscribe action. Decide which event is the correct subscription point and disable the other workflow.

Duplicate transactional emails (the customer receiving two order confirmation emails) are a separate issue caused by WooCommerce’s own emails and a Krom Automation send email action both firing. If Krom Automation handles your order email, disable the equivalent email under WooCommerce > Settings > Emails. Enable Run Once Per Entity in the workflow settings to prevent the same order ID from triggering the same workflow twice, regardless of how many times the order status changes.

Official Plugin vs. Krom Automation: Which Setup Fits Your Store

The right choice depends on what you are trying to accomplish. This table answers the decision rather than listing features side by side.

Your Situation	Better Fit	Why
You need Mailchimp’s purchase history, revenue data, and e-commerce segments	Official Mailchimp plugin	Writes to Mailchimp’s e-commerce API layer; Krom does not
You want abandoned cart emails through Mailchimp	Official Mailchimp plugin	Has built-in cart abandonment tracking
You want to subscribe customers AND post to Slack, update a Sheet, and tag in a CRM in one workflow	Krom Automation Pro	Mailchimp is one action in a multi-step workflow; official plugin is Mailchimp only
You need conditional logic (only subscribe if order total exceeds $100)	Krom Automation Pro	Visual conditional branching; official plugin has no equivalent
You want to avoid per-task fees from Zapier at scale	Krom Automation Pro	Flat annual fee, no execution caps, self-hosted
You run 10+ WooCommerce client sites and need one licence	Krom Automation Pro Enterprise	Unlimited sites for $369/year or $799 lifetime
You use the WooCommerce Checkout Block and need opt-in checkbox support	Official Mailchimp plugin (currently)	Better Checkout Block integration at this time

For stores that need both the e-commerce data layer AND multi-step workflow logic, running the official plugin and Krom Automation together is a workable combination. The official plugin handles the Mailchimp-specific data sync.

Krom handles everything else. They do not conflict.

Scaling Considerations for High-Volume Stores

Krom Automation executes workflows via Action Scheduler, which means no workflow runs during a page load. At 500 to 1,000 orders per day, the queue processes in the background without affecting frontend performance.

The execution log stores a per-step audit trail in 9 custom database tables, so log size grows with volume. For stores processing more than 2,000 orders per day, review your log retention settings under Krom Automation > Settings > Logs and set a retention window (30 or 60 days) to prevent table bloat.

The Mailchimp API enforces a rate limit of 10 concurrent connections. On very high volume days (Black Friday, for example), queued workflows may take 20 to 40 minutes to fully process if order volume spikes above normal. Contacts will be subscribed, just with a delay.

If same-day subscription timing is critical for a campaign, test your queue throughput before the event. Our Black Friday WooCommerce prep guide covers queue and performance considerations in more detail.

Going Further: Related Integrations

If Mailchimp is not the right fit for your store, Krom Automation connects to several other email platforms using the same workflow structure. The setup pattern is identical: pick your WooCommerce trigger, add the platform action, map your merge tags, add a condition if needed. Detailed documentation is available for ConvertKit, MailerLite, ActiveCampaign, and FluentCRM.

For form-based subscription workflows, where a Gravity Forms or WPForms submission triggers the Mailchimp subscribe action rather than a WooCommerce order, see the Gravity Forms integration documentation and the WPForms integration documentation. The merge tag structure differs slightly from the WooCommerce fields shown above, but the Mailchimp action configuration is identical.

Every hour you spend configuring Zapier tasks for a WooCommerce-to-Mailchimp connection is an hour you are paying for infrastructure that lives outside your site, outside your control, and on a billing meter that grows with your order volume.

Also from wpRigel

Pollify is our 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 configuration interface to learn. It is a natural complement to a WooCommerce store running post-purchase surveys or NPS feedback collection.

Commandify is a command palette for the WordPress admin. Press Cmd or Ctrl plus K to jump anywhere, search anything, and run admin actions without clicking through menus. It is the only command palette plugin with genuine WooCommerce depth: search orders by number, customer name or email, change order status, update product prices and stock, and manage customers, all without leaving the keyboard.

Our Verdict

Use Krom Automation for this integration if you need Mailchimp as part of a wider workflow, want to avoid Zapier’s per-task billing, or manage multiple WooCommerce sites under one licence. The Pro Enterprise plan at $369 per year covers unlimited sites, which works out to under $37 per site across a 10-site agency portfolio. That compares well against Zapier’s Growth plan at $299 per month for 2,000 tasks, which a mid-size WooCommerce store can exhaust in a week during a promotion.

Do not use Krom Automation as your sole Mailchimp connection if Mailchimp’s e-commerce segments, purchase-based automations, or revenue reporting are central to your marketing strategy. Those depend on Mailchimp’s e-commerce data layer, which requires the official plugin.

For stores where abandoned cart is the primary use case, the official Mailchimp plugin remains the simpler path. The honest answer is that these two tools solve different parts of the problem, and for many stores, both running together is the right call.

Download the free Krom Automation plugin from the WordPress.org plugin directory to get the WooCommerce triggers active, then see the Pro pricing when you are ready to add the Mailchimp action.

Frequently Asked Questions

Does WooCommerce integrate with Mailchimp natively, or do I need a plugin?

You need a plugin. WooCommerce has no built-in Mailchimp connection.

The two main options are the official Mailchimp for WooCommerce plugin (free, handles the e-commerce data layer) and Krom Automation Pro (paid, handles Mailchimp as part of a multi-step workflow). For most stores, the choice depends on whether you need Mailchimp’s purchase-based segments or whether you need Mailchimp connected alongside other tools in the same automation.

Why are my customers showing up as non-subscribed contacts in Mailchimp?

The two most common causes are: the Status field in the Mailchimp action is set to “Pending” instead of “Subscribed”, which triggers Mailchimp’s double opt-in flow before the contact activates; or double opt-in is forced on at the audience level in Mailchimp under Audience > Settings > Audience name and defaults. Change the Status field to “Subscribed” and disable audience-level double opt-in if you want immediate subscription without a confirmation email.

Can I send abandoned cart emails through this setup?

Not with Krom Automation alone. Krom Automation fires on WordPress and WooCommerce events, and abandoned cart is not a WooCommerce event in the standard sense as no order is created.

You need a dedicated abandoned cart plugin that captures the incomplete session and fires a hook, or you use the official Mailchimp plugin, which has built-in cart tracking. Krom Automation can handle everything that happens after an order exists.

How do I stop WooCommerce and my Mailchimp workflow from sending duplicate order emails?

If Krom Automation is sending a custom order confirmation email, disable the equivalent WooCommerce default email under WooCommerce > Settings > Emails. Find the email type (e.g., “Processing Order”), click Manage, and set it to disabled. The two systems will otherwise both fire independently for the same order event, and the customer receives two identical emails within seconds of each other.

What does this cost compared to running the same workflow through Zapier?

Krom Automation Pro starts at $119 per year for one site with no execution caps. Zapier’s Starter plan is $29.99 per month ($359.88 per year) with a 750-task cap per month. A WooCommerce store completing 100 orders per month and running 3 Zap steps per order uses 300 tasks monthly, leaving 450 in the buffer.

At 250 orders per month with 3 steps, you exceed the Starter cap and move to the Professional plan at $73.50 per month ($882 per year). Krom Automation’s cost does not change regardless of order volume.

Does this integration work with WooCommerce Subscriptions?

Yes, through Krom Automation Pro. The WooCommerce Subscriptions integration adds triggers for subscription created, cancelled, expired, and renewed.

You can subscribe a customer to a Mailchimp audience on initial sign-up and apply a different tag on renewal or cancellation, all in separate workflows. See the WooCommerce Subscriptions integration documentation for the full trigger list and setup steps.

You can connect WordPress to Zapier using the official Zapier for WordPress plugin, and the free Zapier plan works for basic testing. For anything beyond a handful of Zaps, you will hit task limits quickly, and for WordPress-native automation, Krom Automation handles the same workflows without per-task billing or a third-party dependency.

This guide covers both paths honestly. The Zapier integration is the right answer when you need to connect WordPress to an external service that has no native WordPress plugin. A self-hosted automation plugin is the right answer when the trigger and the action both live inside WordPress, because routing that traffic through Zapier’s servers adds latency, cost and a failure point you do not need.

We will walk through the exact setup steps for both, show you what each handles well, and be direct about where each one breaks down. If you are running this decision for a client site or an agency stack, the cost section will matter more than the setup section.

Browse the full feature list for Krom Automation if you want to see the native option before reading the setup steps.

What the Zapier WordPress Integration Actually Connects

The Zapier for WordPress plugin creates a two-way bridge. WordPress can act as a trigger source, firing a Zap when something happens on your site. It can also act as an action target, receiving data from Zapier and creating or updating content inside WordPress.

The plugin authenticates using WordPress application passwords, introduced in WordPress 5.6. You generate a password inside your user profile and paste it into Zapier during the connection flow. No OAuth app, no custom API keys, no coding required.

WordPress events you can use as Zapier triggers:

• New post published (any post type, filterable by category or tag)
• New user registered
• New comment posted
• Post updated (fires on any save, including autosave in some configurations)
• WooCommerce order created or completed (requires WooCommerce installed)

What Zapier can do inside WordPress as an action target:

• Create a new post or page with title, content, status and category
• Update an existing post by ID
• Create a new user with role, email and username
• Create a WooCommerce product or update an existing one

What Gets Synced: Field-Level Reference

WordPress field or event	Where it lands in Zapier
Post title	post_title key in the trigger payload
Post content (raw HTML)	post_content key, unsanitised
Post author ID	post_author key as an integer
Post status at trigger time	post_status key (publish, draft, etc.)
Post permalink	guid key in most configurations
User email on registration	user_email key
User display name	display_name key
User role at registration	roles key as a comma-separated string
Comment author name	comment_author key
Comment content	comment_content key
Comment status	comment_approved key (0, 1, or spam)
WooCommerce order total	total key as a string with currency symbol
WooCommerce order status	status key (processing, completed, etc.)
WooCommerce customer email	billing.email nested key
Custom post meta fields	Not included by default; requires custom code or a Pro Zap filter
User meta fields	Not included by default; requires a separate HTTP Request Zap step

The two rows at the bottom are where most Zapier setups run into trouble. Custom post meta and user meta do not appear in the default trigger payload. Pulling them requires a second Zap step that calls the WordPress REST API directly, which consumes an additional task per execution and adds conditional logic complexity.

Step-by-Step: Connecting WordPress to Zapier

Step 1: Install the plugin

Go to Plugins Add New inside your WordPress admin. Search for “Zapier for WordPress” and install the plugin listed as published by Zapier Inc.

Activate it. No settings page appears after activation because the plugin works entirely through the REST API and application passwords.

Step 2: Create an application password

Go to Users Profile for an administrator account. Scroll to the Application Passwords section near the bottom. In the “New Application Password Name” field, type something identifiable like “Zapier Integration 2026”.

Click Add New Application Password. Copy the generated password immediately. WordPress will not show it again.

The account you use here sets the permission scope for every Zap. Use a dedicated administrator account rather than your personal one, so you can revoke access cleanly if the integration is ever compromised.

Step 3: Authenticate in Zapier

Inside Zapier, create a new Zap and search for “WordPress” as the app. Choose your trigger or action and click Sign In. Zapier asks for three fields: your WordPress site URL (with https://), your WordPress username, and the application password you just generated.

Zapier will test the connection by hitting your site’s REST API. A green “Connection Successful” message confirms the link is live.

Step 4: Build your trigger

Select the WordPress event. Zapier will ask you to load sample data by fetching real recent records from your site. This step is required before you can map fields to the action.

If your site has no recent posts, users or orders, Zapier cannot load samples and the builder stalls. Create a test record in WordPress, then return to Zapier and click Load More.

Step 5: Configure the action and map fields

Choose the destination app and the action. Map WordPress trigger fields to the destination fields using Zapier’s dropdown interface.

Every mapped field counts as data that travels through Zapier’s servers. Turn on the Zap and run a live test with a real WordPress event to confirm the payload arrives correctly.

The Zapier connection takes about 15 minutes to configure. The cost of that connection compounds every month at scale, and most sites discover that cost only after the bill arrives.

Zapier Pricing: What WordPress Sites Actually Pay

The free Zapier plan allows 100 tasks per month across 5 Zaps. One task equals one action step in one Zap execution.

A Zap with two action steps consumes two tasks per trigger firing. Our detailed breakdown is in the Zapier pricing 2026 guide, but the headline numbers are these:

Scenario	Tasks per month	Zapier plan needed	Annual cost (approx)
New post published, notify Slack	30 to 50	Free	$0
Form submission to Google Sheets + email	200 to 600	Starter ($29.99/mo)	~$360
WooCommerce orders to CRM + Slack + email	600 to 2,000+	Professional ($73.50/mo)	~$882
Agency: 10 client sites, 3 Zaps each	3,000 to 10,000+	Team ($103.50/mo+)	~$1,242+

That last row is what stings agencies. Every client site runs independently, but all tasks pool into one Zapier account. A busy month on one site can push you into the next billing tier for all clients simultaneously.

If your automations stay inside WordPress, paying per task for that traffic makes no sense. A user registers, gets a welcome email, and has their role set.

Those three things touch only your WordPress database. Routing them through Zapier’s servers costs money and adds an external dependency for something your own server can handle in under a second.

The Native Alternative: Krom Automation

Krom Automation is a visual workflow automation plugin that runs entirely on your WordPress server. It connects WordPress events to automated actions using a drag-and-drop canvas, with no per-task fees and no third-party account required. The free version includes 16 triggers and 21 actions covering users, posts, comments, media and WooCommerce.

For WordPress-to-WordPress automations, the workflow is: choose a trigger, drag an action node onto the canvas, map your fields using merge tags, and activate. Execution logs are stored in your own database, and the analytics dashboard shows success rate per workflow so a failing workflow does not hide behind aggregate numbers. That matters because a workflow failing silently on WordPress looks identical to a working one until you check the per-step audit trail.

The Krom Automation documentation walks through triggers, actions and workflows if you want to understand the data model before installing.

Side-by-side: Zapier vs Krom Automation for WordPress

Dimension	Zapier + WordPress plugin	Krom Automation
Where automations run	Zapier’s servers (external)	Your WordPress server (self-hosted)
Cost model	Per task, per month	Flat annual or lifetime licence
Free tier limits	100 tasks/month, 5 Zaps	No task limits, no run caps
Custom post meta access	Extra Zap step required	Native via merge tags
Execution logs	30-day history on paid plans	Full per-step audit trail, your database
WooCommerce triggers (free)	Order Created, Order Completed	Order Created, Order Completed
WooCommerce depth (Pro)	Depends on WooCommerce Zapier add-on	Native Pro triggers and actions included
External service connections	6,000+ app integrations	24 Pro integrations (WordPress-native focus)
Data leaves your server	Yes, every execution	No
AI actions	Via OpenAI Zapier app (tasks consumed)	Built in free, bring your own API key

The external service count is where Zapier wins outright. If you need WordPress to talk to a service that has no native WordPress plugin, Zapier is often the fastest path. If everything you are automating lives inside WordPress, paying for that reach is waste.

Every task that touches only your own database should not be paying rent to a third-party server. That cost is invisible in month one and painful by month twelve.

Running Both: The Practical Agency Stack

The cleanest setup for most agencies is not either-or. Use Krom Automation for all WordPress-native workflows and reserve Zapier for the connections that genuinely need it. This keeps task counts low, which keeps Zapier on a cheaper plan, while giving you full native automation inside WordPress.

Krom Automation Pro adds an incoming webhook receiver with a unique secret URL per workflow and HMAC-SHA256 signature verification. That receiver can accept payloads from Zapier, Make, or any external service. So you can run a Zap that collects data from an external app and fires a webhook at WordPress, and Krom Automation handles everything that happens next.

The external-to-WordPress handoff costs one Zapier task. Everything after that is free.

For agencies managing multiple sites, Krom Automation’s Enterprise plan covers unlimited sites for $369 per year. That is a flat cost regardless of how many client workflows run across how many sites.

The equivalent Zapier spend at 3,000 tasks per month is roughly $882 per year, before you factor in additional app connections or team seats. The detailed agency cost comparison lives in what client automation costs per site.

Connecting Specific Plugins to Zapier, and the Native Alternative

Most guides cover WordPress and Zapier generically. The real questions are about specific plugins. Here is where the native approach typically wins:

Form plugins: If your form submissions need to reach Google Sheets or a CRM, Zapier works but consumes tasks for every submission. Krom Automation has native integrations for Gravity Forms, WPForms, Contact Form 7, Fluent Forms, and Elementor Forms. A form submission triggers the workflow directly in WordPress, with zero external API calls for the trigger step.

Email marketing: For syncing WordPress users or form entries to Mailchimp, ConvertKit or ActiveCampaign, native integrations handle subscribe, tag and list management without routing through Zapier. The Mailchimp integration, ActiveCampaign integration, and FluentCRM integration all cover this natively.

WooCommerce: The Zapier for WordPress plugin covers basic order triggers. For deeper WooCommerce work, including subscription events, the WooCommerce Subscriptions integration in Krom Automation Pro handles subscription lifecycle events that the standard Zapier plugin does not expose at all.

Membership and LMS: MemberPress, LearnDash and MemberPress have no meaningful Zapier triggers beyond basic webhook workarounds. Krom Automation Pro includes dedicated trigger sets for MemberPress and LearnDash covering signup, expiry, course completion and quiz events.

What Does Not Transfer and What Breaks

This is the section most guides skip. Read it before you build.

Custom post meta does not appear in the default trigger payload. If you are automating custom post types with ACF or Meta Box fields, Zapier only sends the standard WordPress post fields. You will need a separate Zap step using the HTTP Request action to call the WordPress REST API for the meta, which adds cost and failure surface.

Polling delay means Zapier is not real-time. Most WordPress triggers in Zapier use polling rather than webhooks, checking for new data every 1 to 15 minutes depending on your plan. A user who registers and expects an instant response may wait up to 15 minutes for a Zap to fire. Krom Automation executes via Action Scheduler, which fires within seconds of the trigger event on a normally trafficked site.

Zap history is capped and then deleted. Zapier keeps 30 days of task history on paid plans and 7 days on free. If an automation fails and you do not notice within that window, the evidence is gone. Krom Automation stores every execution log in your own database with no automatic expiry.

Multi-step Zaps multiply task cost. A Zap that checks a condition, sends an email, and updates a CRM record consumes 3 tasks per trigger firing. On a site with 500 form submissions per month, that Zap alone costs 1,500 tasks, which is above the Starter plan’s 750-task limit.

Application password revocation is site-level. If you revoke the application password Zapier uses, every Zap connected to that site stops silently. There is no Zapier-side notification. You discover the failure when a task that should have run did not.

Silent failures are the real cost of external automation. You pay for the task whether or not the action completed, and you find out what broke only when a customer complains.

Troubleshooting: The Three Real Failure Modes

Failure mode 1: The Zap is not triggering

The most common cause is the polling interval. Zapier polls WordPress for new events on a schedule, not in real time.

If your test fires immediately after activating a Zap, Zapier may not have polled yet. Wait 2 to 5 minutes, then check the Zap history in the Zaps Task History section of your Zapier dashboard.

If no history entries appear at all, check whether the WordPress REST API is accessible. Go to yoursite.com/wp-json/wp/v2/posts in a browser.

If that returns a 403 or a redirect to a login page, a security plugin or server firewall is blocking the REST API. Common culprits are Wordfence with “Disable WordPress REST API for logged out users” enabled, or a Cloudflare rule blocking unauthenticated API requests.

Failure mode 2: Authentication errors after initial setup

Application passwords stop working when the WordPress user account is deleted, when the specific application password is revoked from Users Profile Application Passwords, or when a security plugin force-resets all application passwords after detecting a login anomaly. The fix is to generate a new application password and re-authenticate the Zapier connection. Go to Zapier Connected Accounts, find your WordPress connection, and click Reconnect.

Failure mode 3: Payload mapping errors when field names change

If you update a form plugin, a WooCommerce version, or a custom post type structure, Zapier’s saved field map may reference field names that no longer exist in the trigger payload. The Zap continues to fire but sends empty or incorrectly mapped data downstream.

The fix is to open the Zap, click Trigger Test, load fresh sample data, and remap any fields that have changed. This is a manual step that Zapier does not alert you to.

Also from wpRigel

Pollify is a Gutenberg-native poll, survey and quiz plugin. Polls are built as real blocks inside the editor, so there are no shortcodes to paste and no separate interface to learn. It is worth knowing about if you collect audience feedback alongside your automations.

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

It is the only command palette plugin with real WooCommerce order, product and customer commands built in. For agencies managing client sites, it replaces a significant amount of menu-clicking.

When to Keep Zapier, When to Replace It, and What We Would Do

Keep Zapier when you need to connect WordPress to a service that has no native plugin integration. Posting a new WordPress article to a LinkedIn Company Page, syncing WooCommerce orders to a fulfilment system’s proprietary API, or pushing form submissions into a Salesforce instance are legitimate Zapier use cases because those connections have no WordPress-native equivalent.

Replace Zapier with a native plugin when the trigger and the action both live inside WordPress. Welcome emails, role changes, post status automations, CRM syncs to FluentCRM, email list subscriptions, LMS enrolments, and WooCommerce order handling all fall into this category. Routing any of those through an external service adds cost, latency and a failure point that serves no one.

What we would do: install Krom Automation free from the WordPress.org plugin directory, migrate any WordPress-to-WordPress Zaps in the first week, and keep Zapier only for the connections that need its external reach. Most sites find they can drop to Zapier’s lowest paid plan or eliminate it entirely within 30 days. The 20 WordPress automations most sites should have is a useful checklist for identifying what can move to native.

See Krom Automation plan pricing to compare annual and lifetime options across 1, 5 and unlimited sites.

FAQ

Do I need a paid Zapier plan to use it with WordPress?

The free Zapier plan supports up to 100 tasks per month across 5 Zaps. That is enough for light testing or a single low-volume workflow. Most WordPress sites with active forms, user registrations, or WooCommerce orders exceed 100 tasks within the first week of real use and need at least the Starter plan at $29.99 per month.

Why does my Zap fire on post update instead of only on publish?

Zapier’s “New Post” trigger polls the WordPress REST API for posts with a publish status and a date newer than the last check. If you update a post and it triggers the Zap again, it means Zapier is seeing the updated timestamp as a new record. The workaround is to add a Zapier filter step that checks whether the post date equals the post modified date, but that filter step consumes an additional task per execution.

Can Zapier send form submissions to Google Sheets without custom code?

Yes, using a contact form plugin that supports Zapier triggers (WPForms and Gravity Forms both do via their Zapier add-ons) or by using the standard WordPress REST API. Each submission consumes one Zapier task for the trigger and one for the Google Sheets action, so a site with 300 monthly submissions uses 600 tasks for this one workflow alone. Krom Automation’s Google Sheets integration handles the same sync natively without per-row task costs.

Is it safe to give Zapier an application password for my WordPress site?

Application passwords are scoped to the WordPress REST API and cannot be used to log into the WordPress admin directly. The main risk is account-level: if the Zapier account is compromised, the attacker can create posts, users and WooCommerce products using the REST API. Mitigate this by creating a dedicated WordPress user for the Zapier connection with the minimum role needed (Editor for post creation, Administrator only if user creation is required), and review the application passwords list in your user profile monthly.

What happens to my Zaps if Zapier has an outage?

Zapier queues tasks during outages and attempts to replay them after service resumes, but the replay window is not guaranteed for all plan levels. Time-sensitive automations, like sending a password reset email or confirming a WooCommerce order, may fire minutes or hours late during an incident. Self-hosted automation runs on your own server, so the only uptime dependency is your hosting provider rather than a third-party service.

WordPress automation across multiple sites is solved fastest by building each workflow once, exporting it as a JSON file, and importing it into every subsequent site. With Krom Automation, that export-import cycle takes under two minutes per site.

What changes per site is minimal: the sender email address, any site-specific merge tags, and the API credentials for third-party integrations. The workflow logic, branching conditions, and action sequence stay identical.

If you manage 10 or more client sites, rebuilding automation from scratch each time is the single most expensive configuration habit in an agency. A five-action welcome sequence that takes 45 minutes to build manually takes 3 minutes to deploy via import. Across 20 sites, that is 14 hours recovered from a single workflow type.

This guide covers the full operational picture: what transfers automatically, what needs changing per site, how to version-control your workflow library, and what the real cost looks like across a client portfolio. We have also written a broader piece on the automation stack we deploy on every client build if you want the full picture beyond just workflow reuse.

Browse the full feature list to see every trigger, action and integration available before diving into the deployment mechanics.

The Real Cost of Rebuilding Automation Per Site

Most agencies undercount configuration time because it happens in small increments across a project. A welcome email here, an order notification there.

Each one feels like 20 minutes. The actual number, once you count trigger setup, action configuration, merge tag wiring, condition logic and test runs, is closer to 45 minutes per workflow on a clean install.

At 6 workflows per client site and 20 clients, that is 90 hours of configuration work annually at current scale. Double the client count and you do not double the revenue if the configuration hours scale with it.

The automation that took 45 minutes to build the first time should cost 3 minutes to deploy the second time. Anything more is a process failure, not a complexity problem.

The table below shows what that looks like at three portfolio sizes, comparing manual rebuild against a template-and-import approach.

Portfolio size	Workflows per site	Manual build time	Import time	Annual hours saved
10 sites	6	45 min each	3 min each	42 hours
20 sites	6	45 min each	3 min each	84 hours
50 sites	8	45 min each	3 min each	280 hours

At a conservative $75 per hour for a developer or senior VA, the 50-site scenario represents $21,000 in recoverable labor annually. That number is why the workflow portability question matters to the person signing the budget, not just the person doing the configuration.

How Krom Automation Export and Import Works

Every workflow in Krom Automation can be exported as a portable JSON file from the Workflow Settings panel. The export captures the complete workflow definition: every node on the canvas, the trigger configuration, all action settings, branching conditions, delay rules, and the notes field. Nothing is stored server-side by wpRigel, so the file moves wherever you take it.

Importing on a new site is a single file upload in the same panel. The workflow appears on the canvas immediately in a paused state, which is intentional. Paused means you review and adjust the site-specific fields before it touches a live user or order.

What the import preserves exactly:

• The full canvas layout, node positions, and connection paths
• Every trigger type and its configuration fields
• All action types, field mappings, and conditional logic
• Delay scheduling rules, including unit types (minutes, hours, days)
• Merge tag placements in every action field
• The run-once-per-entity setting, preventing duplicate executions
• Workflow notes, useful for leaving deployment instructions for your team

What the import does not carry across, because it cannot:

• Third-party API credentials (Mailchimp API keys, Slack tokens, webhook URLs)
• The sender name and email address for outbound emails
• Site-specific post IDs or user role names that differ between installs
• Active or paused state, every import arrives paused

That second list is short on purpose. A well-built workflow template uses merge tags and generic role references rather than hard-coded IDs. If you build templates correctly once, the per-site adjustment time stays under 5 minutes for most workflow types.

Building a Reusable Workflow Library

The agencies that benefit most from workflow portability are the ones that treat their workflow files the way they treat their starter theme or their deployment checklist. Versioned, documented, and stored somewhere accessible to the whole team.

A practical library structure looks like this:

• Core workflows that run on every site regardless of client type: user registration welcome email, failed login alert, media upload notification
• WooCommerce workflows for every commerce client: order confirmation, order status change notification, low stock alert
• LMS workflows for education clients: course enrollment confirmation, quiz completion trigger, LearnDash or TutorLMS completion sequences
• Membership workflows for subscription sites: signup confirmation, renewal reminder, expiry handling via MemberPress triggers
• Form response workflows wired to the client’s form plugin: lead follow-up, internal notification, CRM sync

Store each file with a version number in the filename and a changelog in the workflow notes field. When you update a workflow type (because a client request reveals a better approach), bump the version and re-export. Sites still on the old version get upgraded on the next maintenance visit.

A workflow library is worth nothing if the person deploying it does not know which version to use. Filename discipline and notes fields are not optional extras.

Krom Automation’s workflow notes field is the right place to leave deployment instructions: which fields need updating, what credentials are required, and whether the workflow depends on a specific plugin being active. Future you, or the junior on your team, will thank present you.

Per-Site Configuration: What Actually Changes

The fastest way to make imports painful is to build workflows with hard-coded values. The fastest way to make imports fast is to build with merge tags and abstract references everywhere a value might differ between sites.

Here is a concrete breakdown of what typically needs adjusting after an import, ordered by how often it comes up:

What needs changing	How often	Time cost	Prevention
Third-party API credentials	Every site	2 to 5 min	Cannot be avoided; document which are needed
Sender email and name	Every site	30 seconds	Use a placeholder, note it in workflow notes
Webhook URLs	Every site with webhook actions	1 to 2 min	Note the endpoint pattern in the workflow notes
Post or page IDs	Only if hard-coded	1 to 3 min	Use merge tags or post slug references instead
User role names	Only on custom role installs	1 min	Match role names across your client installs
Email body copy	Client-specific branding	5 to 15 min	Keep logic in the workflow, copy in a variable field

The workflows that import cleanest are the ones built with the assumption that they will be deployed elsewhere. That means no hard-coded post IDs, no literal email addresses in action fields, and every piece of site-specific text in a field that is clearly labelled as such. The workflow builder documentation covers how to structure nodes cleanly from the start.

The Form Plugin Variable

One practical complication in multi-site deployment is that clients use different form plugins. A workflow that fires on a Gravity Forms submission does not transfer to a site running WPForms, because the trigger type is different even if the downstream logic is identical.

The fix is to maintain parallel versions of form-triggered workflows, one per form plugin you commonly deploy. Krom Automation supports Gravity Forms, WPForms, Fluent Forms, Contact Form 7, Elementor Forms, and Ninja Forms.

If you standardise on two or three form plugins across your client portfolio, you maintain two or three trigger variants of each workflow. The action chain after the trigger is identical and reusable.

The same applies to email marketing integrations. A lead follow-up workflow that syncs to Mailchimp needs a parallel version for clients using MailerLite or ActiveCampaign. Building this library of trigger-variant files upfront is a one-time cost that pays back across every future deployment.

Multisite vs. Separate Installs: The Workflow Angle

The Multisite versus separate installs debate usually centres on updates, hosting costs and user management. Rarely does it account for automation workflow behaviour, which is worth addressing directly.

On a WordPress Multisite network, each sub-site is a separate WordPress environment. Krom Automation installed network-wide means each sub-site gets its own workflow list, its own execution logs, and its own trigger scope.

Triggers fire per sub-site, not network-wide. That is almost always the right behaviour for client sites, since a user registering on one sub-site should not trigger a workflow on another.

On separate installs, each site is fully independent. There is no cross-site coordination by default, which is fine for most agency client work where clients are different businesses with no relationship to each other.

Where Multisite genuinely helps is when you need shared user accounts across sub-sites, or when you want to push a workflow update to all sub-sites simultaneously through a single plugin update. Where it hurts is when one client’s heavy traffic or misconfigured workflow affects performance for every other sub-site on the network.

Multisite is not a scalability solution. It is a shared-destiny architecture. Every client on that network inherits every other client’s problems.

For most agency portfolios where clients are independent businesses, separate installs with a standardised workflow library is the lower-risk, lower-drama approach. Multisite is worth it when the clients are genuinely related, such as a franchisor and their franchisee network, or a publisher with multiple regional editions of the same site.

Licensing Across a Client Portfolio

Workflow portability only saves time if you can actually activate the plugin across your full portfolio. Licensing is the constraint most agencies hit second, right after building their first solid workflow library.

Krom Automation Pro pricing by site count:

Plan	Sites	Annual	Lifetime	Annual cost per site (annual plan, 20 sites)
Basic	1	$119/year	$299	Not applicable
Standard	5	$199/year	$499	$39.80
Enterprise	Unlimited	$369/year	$799	$18.45 at 20 sites, $7.38 at 50

For any agency managing more than 5 client sites, the Enterprise plan is the only one that makes financial sense. At 20 sites on the annual plan, the per-site cost is $18.45 per year.

At 50 sites, it drops to $7.38. The lifetime option at $799 eliminates the renewal calculation entirely, which is worth considering if you expect the portfolio to grow.

The free version is available with no run caps, no trial period, and no features behind a paywall. For clients with simpler automation needs, the free tier covers 16 triggers and 21 actions, which is enough for most standard notification and user management workflows. Download the free plugin from the WordPress.org plugin directory and test the import workflow on your own site before rolling it out to clients.

We have also written a detailed breakdown of what client automation costs per site and what it should, which covers how to structure your own pricing when passing automation costs to clients.

Execution Monitoring at Scale

Deploying workflows across 20 sites creates a new problem: knowing when something breaks without logging into each site to check. A workflow failing silently on a client site is a support ticket waiting to happen, usually arriving from the client rather than from your monitoring.

Krom Automation handles failure notification by email with automatic retry and configurable backoff. That means the first failure triggers a retry, and if the retry fails, an email goes to the address configured in the plugin settings. Set that to your agency’s monitoring inbox, not the client’s email address, and you get first notice before the client does.

The execution log gives you a full per-step audit trail for every workflow run. When a client reports that their order confirmation email did not arrive, you can check exactly which step failed, what the trigger data contained, and whether the retry succeeded.

That is the difference between a 10-minute support call and a 2-hour investigation. We wrote a detailed piece on what happens when automation fails silently on WordPress and how to catch it before clients do.

The analytics dashboard shows total executions, active workflow count, estimated time saved, and failed execution count. Per-workflow success rate is visible without clicking into individual logs, which is the right level of detail for a weekly portfolio review. The reports page adds date range filtering and CSV export, useful if you want to include automation performance in a monthly client report.

Also from wpRigel

Pollify is our Gutenberg-native poll, survey and quiz plugin. Polls are built as real blocks inside the editor, with no shortcodes to configure and no separate admin interface to learn. If any of your clients publish editorial content or run community sites, it is worth adding to your standard deployment stack.

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

For agencies managing dozens of client sites, it is the fastest way to get around an unfamiliar admin without hunting through sidebar menus. It is the only command palette plugin with real WooCommerce order, product and customer commands built in.

Our Verdict

If you manage more than 5 client sites and are still building automation workflows from scratch on each one, you are spending 60 to 100 hours a year on configuration that should take a fraction of that. The workflow library approach, built once, exported, imported and adjusted in under 5 minutes per site, is the only version of multi-site automation that scales without hiring someone just to handle setup.

The agencies this approach does not suit are the ones where every client site is genuinely unique in its plugin stack, its trigger requirements, and its downstream integrations. If you build fully custom stacks with no standardisation, the library benefit is real but smaller, because you are maintaining more workflow variants. The answer there is not to abandon the approach but to standardise your stack first, then build the library.

The Enterprise plan at $369 per year for unlimited sites is the right entry point for any portfolio beyond 5 sites. The lifetime option at $799 removes the renewal decision permanently. Either way, the per-site cost at any meaningful scale is low enough that it should not be a line item in the client conversation at all.

Compare all three Krom Automation plans and see the full feature breakdown before making a decision.

Frequently Asked Questions

Does the Krom Automation free version support workflow export and import?

Yes. Export and import are available in the free version with no restrictions. The exported JSON file contains the complete workflow definition and can be imported to any site running Krom Automation, free or Pro.

Do I need a separate licence for each client site?

Pro features require an active licence per site. The Enterprise plan covers unlimited sites for $369 per year or $799 lifetime, making it the practical choice for any agency portfolio larger than 5 sites. The free version has no licence or site limits.

What happens to delays and scheduled actions after a workflow is imported?

Delay and scheduling configurations import correctly. However, scheduled triggers that use specific dates or times need to be reviewed on the new site, since a one-time scheduled date from the original site may already have passed. Recurring schedules (daily, weekly, monthly) import and activate without adjustment.

Can I automate across two separate WordPress sites, for example pushing a post from one to another?

Direct site-to-site automation requires an intermediate layer. The HTTP Request action can call the REST API of another WordPress site, and the incoming webhook receiver on the Pro plan can receive that call and trigger a workflow on the destination site. It is not point-and-click, but it is fully supported without any third-party service in the middle.

What is the difference between WordPress Multisite and managing separate installs for automation purposes?

On Multisite, each sub-site has its own workflow scope. Triggers fire per sub-site and do not cross sub-site boundaries by default.

Separate installs behave identically from an automation standpoint, with each site fully independent. Multisite only adds value for automation when you need shared user accounts or network-wide plugin configuration changes applied to all sub-sites simultaneously.

How do I handle clients who use different form plugins?

Maintain one workflow file per form plugin variant for each workflow type that uses a form trigger. The trigger node differs between Gravity Forms, WPForms, Fluent Forms and the others, but the action chain after the trigger is identical across variants. Build the action chain once, duplicate the workflow, and swap the trigger node for each form plugin version you support.

Is there a way to test a workflow after import before it goes live?

Yes. Krom Automation includes a workflow simulator that runs a dry-run with zero side effects.

No emails are sent, no records are created, and no external APIs are called. You can verify the complete execution path, including branching logic and merge tag resolution, before activating the workflow on a live client site.

A WordPress automation that fails silently is more dangerous than one that crashes with an error. A loud failure produces a log entry, a notification, something you can respond to. A silent failure produces nothing.

The workflow appears active, no alert fires, and the work it was supposed to do just doesn’t happen. This is the failure mode that leaves a WooCommerce order unconfirmed, a new member without a welcome email, or a course enrollment that never completes, sometimes for weeks.

Most articles about WordPress automation failures focus on the visible kind: the “automated update has failed to complete” message, the .maintenance file, the PHP memory limit error. Those are easy to write about because the site tells you something went wrong. The harder problem is the failure that gives you no signal at all. That’s what this article is about, and it’s an observability problem, not a configuration one.

We’ll cover why silent failures happen, how to detect them, how to build alerting that actually fires, and why partial failures are more operationally damaging than total ones. The framing throughout is for developers and agency owners managing automations across multiple sites, not single-site hobbyists.

See how Krom Automation handles execution logging and failure alerting

Why Silent Failure Is Worse Than a Crash

When a workflow crashes with an exception, the execution state is wrong but your awareness is correct. You know something failed. You can check the logs, find the step, and fix it.

When a workflow fails silently, both the execution state and your awareness are wrong simultaneously. You believe the automation is running. It isn’t.

The operational cost difference is significant. A loud failure detected within an hour costs you the time to diagnose and fix it.

A silent failure running undetected for 30 days costs you everything that workflow was supposed to do during that window: every welcome email that didn’t send, every Slack notification that didn’t fire, every contact that didn’t get added to your FluentCRM list. You don’t get those back.

A crash is a problem. A silent failure is a debt you don’t know you’re accumulating.

There’s also a compounding factor: silent failures erode trust in automation itself. When a team discovers that a workflow they relied on hasn’t been running for a month, the instinct is to go back to doing things manually. That’s the worst possible outcome, because manual processes don’t scale and they fail too, just more visibly.

The Most Common Causes of Silent Failure in WordPress

Understanding why automations fail silently is the first step toward detecting them. The causes generally fall into four categories.

WP-Cron Reliability on Shared Hosting

WordPress uses WP-Cron to schedule background tasks. WP-Cron is not a real cron job. It fires when a visitor loads a page, which means on low-traffic sites or during quiet periods, it can be hours late or miss entirely.

A workflow scheduled to run at 09:00 on shared hosting might run at 11:30, or not until the next day. No error is thrown. The job just sits in the queue.

This is the most common cause of silent delay failures. The automation isn’t broken, but its timing is completely unreliable, and nothing tells you that.

The fix is to disable WP-Cron in wp-config.php and configure a real server cron to hit /wp-cron.php every 60 seconds. Until that’s done, any workflow using delay scheduling is operating on a best-effort basis.

PHP Execution Limits

Shared hosting providers typically set PHP execution time between 30 and 60 seconds. A workflow running an HTTP request to a slow external API, followed by a database write and an email send, can exceed that limit mid-execution. The process dies, the remaining steps don’t run, and depending on how the workflow engine handles the interrupt, no failure record is written. From the outside, the workflow appears to have run.

Third-Party API Failures

Any workflow that touches an external service, whether that’s a Mailchimp subscriber add, a Google Sheets row write, or a Slack message, depends on that service being available and responsive. When an API returns a 500 error or a timeout, the outcome depends entirely on how the automation layer handles it. If it doesn’t retry and doesn’t log the failure, you get silence.

Conditional Branches That Route Incorrectly

A workflow with conditional branching can route every execution down the wrong path if a condition is misconfigured. Every trigger fires, every execution completes, the logs show green, and the actual outcome is wrong. This is the most insidious type of silent failure because the automation technically ran.

It just ran incorrectly. You’ll only catch it by checking outputs, not by checking whether executions completed.

Partial Failures Are More Damaging Than Total Failures

A workflow that always fails is easy to detect: the output is consistently missing. A workflow that fails 20% of the time is far harder, because 80% of executions produce the correct result.

That success rate looks acceptable in aggregate. The 20% failure rate doesn’t show up unless you’re looking at per-execution outcomes, not totals.

An 80% success rate on a critical workflow means 1 in 5 customers gets the wrong experience. That’s not a minor bug. That’s a systemic problem dressed as normal operation.

Partial failures also have a specific cause pattern. They tend to be triggered by data edge cases: a user with an unusual character in their name, an order with a product in a category the workflow wasn’t configured to handle, a form submission with an empty required field that the workflow expects to be populated. The fix isn’t the workflow itself, it’s the missing input validation before the workflow runs.

This is why per-execution logging matters more than aggregate dashboards. If you can only see “200 executions this week”, you can’t detect a 20% failure rate. If you can see each execution with its per-step result, you can spot the pattern immediately.

What Good Execution Logging Actually Looks Like

Most WordPress automation plugins offer some form of execution history. The question is what that history actually tells you. There’s a meaningful difference between these two logging levels:

Logging level	What you can detect	What you miss
Workflow-level only (pass/fail)	Total failures, complete workflow crashes	Partial step failures, branch routing errors, API errors that didn’t throw
Per-step audit trail	Which exact step failed, what data it received, what error it returned	Nothing that happened, every step is visible

Workflow-level logging is better than nothing. Per-step logging is what you need to diagnose a partial failure or a branch routing problem.

Krom Automation logs every step of every execution, so you can see the exact data each node received and what it returned. That’s the level of detail that makes silent failures visible.

The analytics dashboard shows total executions, active workflows, success rate, and failed execution count alongside an execution trend chart. The reports page adds date range filtering, per-workflow breakdown, and CSV export. Those two views together let you spot a declining success rate before the failure becomes a customer-facing problem. You can read more about how workflows are built and what data they capture in the Krom Automation overview documentation.

Setting Up Failure Alerting That Actually Fires

Detection through manual log review is not a monitoring strategy. For automation failures to be caught quickly, alerting needs to be automatic and immediate. Here’s the alerting hierarchy we recommend, ordered by how much difference each makes.

1. Email failure notifications on first failure, the minimum viable setup. Configure your automation layer to send an email when any workflow execution fails. The email should name the workflow, the trigger event, the step that failed, and the error message. A generic “something failed” email wastes diagnostic time.
2. Automatic retry with configurable backoff, a transient API error should not create a permanent failure. A retry schedule that attempts again at 5 minutes, 30 minutes, and 2 hours catches the majority of third-party service blips without intervention. Without retry, every API hiccup becomes a failed execution in your logs.
3. Success rate thresholds, not just failure counts, alerting only on failure count misses the partial failure pattern. If you had 100 executions last week and 20 this week, that’s not a failure alert, it’s a volume drop. Alert on success rate falling below a threshold, not just on failures appearing.
4. Messaging channel alerts for critical workflows, for workflows that touch revenue-critical processes, email alone is too slow. A Slack or Discord notification via the messaging integrations means the right person sees the failure within minutes, not the next time they check their inbox.

Krom Automation handles points one and two natively: failure notifications go out by email and the retry mechanism uses configurable backoff. For point four, you can build a secondary workflow that triggers on a failed execution and posts to Slack. That’s the kind of meta-automation most teams don’t think to build until after a significant failure has already happened.

The Observability Stack for WordPress Automation

Treating automation as an observability problem means asking: at any moment, do I know the current state of every workflow, and would I know within 15 minutes if that state changed? Most WordPress sites would answer no to both. Here’s what a complete observability stack looks like.

Layer	What to monitor	How to catch failure within 15 minutes
Execution health	Success rate per workflow over rolling 7 days	Alert when success rate drops below 90%
Queue health	Pending jobs older than 2x their expected interval	Alert if a scheduled workflow hasn’t fired within its window plus 10 minutes
API dependency health	Third-party service response times and error rates	HTTP request action logs will show consistent timeouts before a full outage
Data correctness	Output records in destination systems	Spot-check: query the destination (FluentCRM contact count, Google Sheets row count) and compare to expected trigger volume

The data correctness layer is the one nobody implements and the one that catches branch routing errors. If your WooCommerce Order Completed trigger should be firing roughly as often as new completed orders appear in WooCommerce, and it isn’t, something is wrong even if every execution shows as successful. Reconciling trigger volume against destination records is the only way to catch a correctly-executing but incorrectly-routing workflow.

Using the Workflow Simulator Before Production

The best time to catch a silent failure is before the workflow goes live. A dry-run simulator lets you fire a workflow against real or synthetic data without executing the actual actions, so you can verify that branch conditions route correctly, merge tags resolve to the expected values, and every step receives the data it needs.

Krom Automation’s workflow simulator runs a complete dry run with zero side effects. You see the exact data each node would receive and the path each branch would take, without sending a single email or writing a single database record. Running the simulator against edge-case inputs, not just the happy path, catches the conditional routing errors that cause partial failures in production.

The test cases worth running for any workflow are:

• The expected happy-path input that should produce the desired output
• An input where the primary condition evaluates false, to verify the No branch is configured correctly
• An input with missing or empty fields that the workflow uses in merge tags
• An input that represents a boundary case, such as a user with no assigned role, or an order with zero line items

Four test cases takes about 10 minutes. Discovering a branch routing error in production after 500 executions have silently gone to the wrong path takes considerably longer to diagnose and remediate.

What to Check When You Suspect a Silent Failure

If you suspect a workflow has been failing silently, work through these checks in order. Skipping ahead wastes time if an earlier issue is the actual cause.

1. Check execution volume against trigger volume. How many times did the trigger fire in the period you’re investigating? How many executions completed? A gap between those two numbers means some triggers didn’t produce executions at all, which points to a queue or WP-Cron problem.
2. Check per-step logs for the failing executions. If executions ran but outcomes are wrong, the per-step log will show which step received bad data or returned an error. Most silent failures are visible at this level.
3. Check the destination system, not just the workflow. If the workflow log shows success but the FluentCRM contact doesn’t exist, the issue is at the API layer. The HTTP request may have returned a 200 that contained an error body, which the workflow treated as a success.
4. Check WP-Cron queue depth. If scheduled workflows are queuing but not firing, WP-Cron is the problem. Check the queue using a plugin like WP Crontrol and verify events are processing, not accumulating.
5. Check PHP error logs for the relevant time window. A timeout or fatal error that killed a workflow process may not surface in the workflow logs at all, but it will appear in the server’s PHP error log.

Hidden Costs Nobody Mentions

Silent automation failures have costs that don’t appear in a post-mortem until someone does the arithmetic. For an agency managing 20 client sites, each running 5 to 10 automations, a 5% silent failure rate across all workflows means dozens of missed events per week. At an average manual task time of 8 minutes per event, that’s several hours of rework per week that nobody has budgeted for, because nobody knew it was needed.

There’s also a compounding liability for WooCommerce sites. An order fulfillment workflow that silently fails on 3% of orders means 3% of customers don’t receive their confirmation, their shipping notification, or their digital download. Those customers open support tickets.

Support tickets cost money to resolve, and they arrive without any context that automation was involved, so the connection to a workflow failure is rarely made. You can read more about the real cost structure of WordPress automation in our breakdown of what client automation costs per site.

For sites handling sensitive workflows, such as membership access provisioning or course enrollment, a silent failure has a direct revenue impact. A student whose LearnDash enrollment didn’t complete after payment will request a refund if they can’t access their course.

The workflow ran, the execution shows as complete, and the enrollment still didn’t happen. Without per-step logging, you have no way to explain what went wrong.

The workflows you never check are the ones with the highest silent failure rate. Confidence in automation you haven’t verified is not confidence, it’s exposure.

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 configuration interface. It’s worth knowing about if you’re already using Gutenberg as your primary editor and want audience engagement tools that work the same way.

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. For agencies managing multiple sites, it’s the fastest way to navigate a WordPress admin, and it’s the only command palette plugin with genuine WooCommerce order, product and customer management built in.

Our Verdict

Silent automation failure is an observability problem, and it doesn’t have an observability solution on most WordPress sites because most WordPress automation tooling wasn’t built with observability in mind. The result is a large class of failures that are actively invisible: no alert, no log entry, no customer complaint until the damage has been running for weeks.

Who needs to act on this immediately: any agency or developer running business-critical workflows on client sites, particularly anything touching WooCommerce orders, membership access, or email sequences. If you don’t have per-step execution logs and automatic failure alerting today, you are operating blind.

Who can take a more measured approach: single-site owners running simple, low-stakes automations where a missed execution is inconvenient but not damaging. Set up email failure notifications as a minimum, and check execution volume monthly.

What we would do: deploy Krom Automation for the per-step audit trail and built-in failure alerting, configure a real server cron instead of relying on WP-Cron, and build one meta-workflow that posts critical failures to Slack. That stack catches the vast majority of silent failures within 15 minutes of occurrence. The free version is available at the WordPress.org plugin directory with no trial period and no execution caps.

For teams ready to move beyond reactive debugging, the full feature comparison and Pro plan details are on the Krom Automation pricing page.

Frequently Asked Questions

How do I know if a WordPress workflow is failing silently if nothing appears in the logs?

Start by comparing trigger volume to execution count. If fewer executions completed than triggers fired, some events never reached the workflow queue, which points to a WP-Cron or queue processing problem. Then check the destination system directly: if expected records aren’t appearing in your CRM, email list, or database, the workflow may be executing but routing incorrectly.

Can a WordPress automation show as “completed” even when it failed?

Yes, in two scenarios. First, if a third-party API returns a 200 status with an error body, the automation layer may record a success even though the action didn’t complete.

Second, if a conditional branch routes an execution to a path that does nothing, the workflow completes with no output and no error. Per-step logging and destination-side reconciliation are the only reliable ways to catch both of these.

Does replacing WP-Cron with a real server cron actually fix silent failure?

It fixes the timing and reliability problem, not all silent failures. A real server cron ensures scheduled workflows fire on time and that background execution queues don’t stall.

It doesn’t fix API errors, misconfigured conditions, or PHP execution timeouts. It’s a necessary foundation, but not a complete solution.

What’s the minimum alerting setup for a production WordPress automation?

At minimum: email notification on first failure, and automatic retry on transient errors. That combination catches the majority of third-party API blips without manual intervention. For revenue-critical workflows, add a Slack or Discord alert via a secondary notification workflow so failures appear in real time rather than waiting for someone to check their email.

How often should I review automation execution reports?

Weekly for any automation touching revenue, access provisioning, or customer communication. Monthly is acceptable for low-stakes automations where a missed execution is recoverable.

Don’t wait for a customer complaint to initiate a review. By the time a customer reports a missing email or access problem, the failure has typically been running for days.