To send an EDD license expiry reminder email, you have two options. The built-in Software Licensing extension sends one reminder at a configured interval before expiry. For a multi-step sequence, 30 days out, 7 days out, on the expiry date, and a post-expiry recovery message, you need Krom Automation Pro, which adds the EDD trigger set and the delay scheduling that makes a sequence possible.

EDD’s own reminder is fine for low-volume stores where a single nudge is enough. Most software sellers find that a single email converts a fraction of lapsing customers because the timing rarely lands when the buyer is ready to act. A four-message sequence covering the full renewal window lifts renewals without any extra manual work after the initial setup.

This guide covers both approaches, including how to configure EDD’s built-in system, how to build a full reminder sequence in Krom Automation Pro, where to add a personal renewal discount, and what to send after a license has already expired.

Browse the full Krom Automation feature list to see the complete EDD trigger and action set before diving into setup.

What EDD’s Built-In Reminder Actually Does

Easy Digital Downloads Software Licensing includes a single renewal reminder email. You enable it under Downloads > Settings > Emails > Renewal Reminder, set a send period in days or weeks before expiry, and write your template using EDD’s merge tags.

Available merge tags include the customer name, the license key, the product name, the expiry date, the renewal URL, and an unsubscribe URL. The renewal URL generates a one-click link that pre-fills the cart with the renewal product and optionally applies a discount.

The limitation is structural: one email, one timing. If that email lands while the customer is travelling, on deadline, or simply not ready to spend, there is no follow-up. The license lapses, and you have no automated way to reach them again unless you build it manually or use a second tool.

A single renewal email is not a renewal strategy. It is one shot at the moment the customer may be least prepared to act.

EDD’s Recurring Payments extension handles auto-renewing subscriptions separately. If a customer is on automatic billing, the Software Licensing reminder does not apply to them and should not be sent. The two systems operate independently, and mixing them up produces duplicate emails, which is the most common complaint in EDD support forums.

What Gets Sent and When: A Renewal Sequence That Converts

Before building anything, decide the sequence structure. The four-message cadence below is practical for most software sellers. Adjust the intervals based on your license term, but keep at least three touchpoints before expiry.

Message	Timing	Purpose	Discount?
Early reminder	30 days before expiry	Plant the renewal in mind, no pressure	No
Urgency reminder	7 days before expiry	Drive action while there is still time	Optional, 10 to 20%
Expiry-day message	Day of expiry	Last chance, direct CTA	Yes, your strongest offer
Post-expiry recovery	7 days after expiry	Win back lapsed customers before they move on	Yes, time-limited

The discount logic matters. Offering your best discount at day 30 trains customers to wait for it. Save the strongest incentive for the expiry-day and post-expiry messages, where it functions as a recovery tool rather than an early-bird reward.

Setting Up the Sequence in Krom Automation Pro

Krom Automation Pro includes the Easy Digital Downloads integration, which adds the license expiry trigger set to the visual workflow builder. The full list of EDD triggers and the setup walkthrough are in the Easy Digital Downloads integration documentation.

The general shape of each workflow is identical. The trigger fires when a license is approaching expiry, then a delay node holds execution until the right moment, then a Send Email action delivers the message. Repeat across four separate workflows, one per message in the sequence.

Here is what each workflow needs:

• Trigger: EDD License Expiring (from the Pro trigger library)
• Delay node: configured to the correct number of days before or after the trigger fires. See the delays and scheduling documentation for exact configuration options including minutes, hours, days, and weeks.
• Conditional branch: check whether the license is on auto-renewal. If yes, skip the email. This prevents sending manual renewal prompts to customers already billed automatically. See conditions and branching for how to set the Yes/No path.
• Send Email action: personalised with merge tags for the customer name, product name, expiry date, and renewal link

Merge tags let you pull live data from the trigger event directly into the email body. The customer’s first name, the exact license expiry date, the product they purchased, and a pre-built renewal URL all inject automatically. The merge tags documentation covers every available variable and the correct syntax.

The Post-Expiry Workflow

The post-expiry recovery email is the one most stores never send, and it is often the highest-converting message in the sequence. A customer whose license lapsed seven days ago is still familiar with your product.

They have not replaced it yet. A time-limited offer, framed as a one-time reinstatement discount, converts a meaningful slice of lapsed customers who ignored every pre-expiry message.

Build this as a separate workflow with the trigger set to fire on the expiry date and a delay of exactly 7 days. Use a conditional branch to check whether the license has since been renewed.

If yes, skip the email entirely. If no, deliver the recovery message with your strongest discount and a hard expiry date on the offer, something like “this offer expires in 48 hours”.

Adding a Personal Renewal Discount

EDD Software Licensing supports a renewal discount that auto-applies when a customer clicks the renewal link in their email. You create the discount under Downloads > Discounts, set it to apply to the renewal product, and paste the discount code into the renewal URL tag in your email template.

In a Krom Automation workflow, you can use the HTTP Request action to call the EDD REST API and generate a customer-specific coupon before the email fires. This is more work than a shared code, but it prevents coupon sharing and lets you track redemption per customer.

Whether the extra complexity is worth it depends on your volume. For stores with fewer than 500 annual renewals, a shared code with a short expiry window is sufficient.

The key rule: do not put the same discount in every email. Customers who receive the discount at the 30-day mark have no incentive to act before the expiry-day email. Staggering the offer, or withholding it until the urgency messages, produces better timing-to-conversion alignment.

Sending your best discount at 30 days does not accelerate renewals. It teaches customers to wait another 23 days.

Designing the Emails Themselves

Krom Automation Pro includes a visual email builder built on the Gutenberg block editor. You design renewal emails using blocks, with no HTML required and no external email tool to connect. The output is responsive and compatible with all major email clients.

Each message in the sequence should do one thing. Here is how to frame each:

• 30-day email: Helpful tone. Remind the customer what value they get from the license. Link to your changelog or recent updates. Renewal CTA, no pressure language.
• 7-day email: Practical tone. Tell them exactly when the license expires. List what stops working after expiry, support, updates, or both. Introduce the discount if you are offering one at this stage.
• Expiry-day email: Direct tone. The license has expired today or expires tonight. Best discount, single CTA, no distractions. Subject line should state the date.
• Post-expiry email: Recovery tone. Acknowledge the lapse without guilt-tripping. Offer reinstatement with a time-bounded discount. Make the path back as frictionless as possible.

Subject lines for renewal emails perform better when they include the product name and a date rather than generic urgency phrases. “Your [Product] license expires January 14” outperforms “Don’t miss out on your renewal” in open rate testing across SaaS email benchmarks, because the first tells the reader exactly why they are receiving the message.

Testing Before You Go Live

Krom Automation includes a workflow simulator that runs a complete dry-run execution with zero side effects. No emails are sent, no data is written, but every step is evaluated against real workflow logic so you can confirm the conditional branches, the delay values, and the merge tag output are all correct before a real license expiry event fires.

The workflow simulator documentation explains how to feed a test event through the system and read the per-step audit trail. Run the simulator on each of the four workflows before enabling them. A missed conditional branch on the auto-renewal check is the most common setup error, and it produces the duplicate-email problem customers report most often.

For more on testing automation workflows before they go live, the guide on how to test a WordPress automation before it goes live covers the full testing process including failure simulation.

A Note on WP-Cron Timing

Krom Automation runs scheduled actions via Action Scheduler, which itself depends on WordPress Cron. On low-traffic sites where no one visits for several hours, WP-Cron fires late. A delay set for 9:00 AM may fire at 11:30 AM if no request hits the site in that window.

For a license expiry sequence, this is usually acceptable. A few hours of drift on a 30-day or 7-day reminder does not meaningfully affect conversion. The expiry-day email is more sensitive.

If exact timing matters, configure a real server cron job to call wp-cron.php on a set schedule rather than relying on visitor-triggered execution. Most managed WordPress hosts offer this in their control panel.

Cost Comparison: Built-In EDD vs. Krom Automation Pro

Capability	EDD Built-In Reminder	Krom Automation Pro
Number of reminder emails	1	Unlimited, one workflow per message
Timing options	One fixed interval	Any combination of minutes, hours, days, weeks
Post-expiry recovery email	No	Yes
Auto-renewal skip logic	Manual configuration required	Conditional branch, built in 2 minutes
Per-customer personalisation	EDD merge tags only	EDD merge tags plus full Krom merge tag library
Visual email builder	No	Yes, Gutenberg block based
Execution logs per step	No	Yes, full audit trail
Cost (1 site, annual)	Included in EDD Software Licensing	Starts at $69/year (launch pricing)

If your store sells 50 or more licenses per year, the revenue difference between a one-email and a four-email renewal sequence likely covers the cost of Krom Automation Pro in the first month of operation. At a 20% renewal discount on a $99 product, one additional renewal per month pays for the annual plan twice over.

What About WooCommerce Subscriptions?

This guide covers EDD Software Licensing specifically. If you run WooCommerce with subscription products instead, the trigger set and sequence logic are almost identical, but the integration is different. The WooCommerce Subscriptions integration documentation covers the equivalent setup, and the companion post on automating WooCommerce subscription renewal reminder emails walks through a comparable sequence in that context.

MemberPress users dealing with a similar expiry and recovery challenge can also apply the same four-message structure using the MemberPress integration triggers for subscription expiry events.

Also from wpRigel

Pollify is wpRigel’s Gutenberg-native poll and survey plugin. Polls are built as real blocks inside the block editor, with no shortcodes to paste and no separate interface to learn. If you collect customer feedback or run product satisfaction surveys alongside your license sales, Pollify fits directly into the same WordPress workflow.

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 WordPress command palette with real WooCommerce order, product and customer commands built in, which makes it useful for stores managing high order or license volumes.

Our Verdict

EDD’s built-in renewal reminder is a reasonable starting point for a store with a small license base and low renewal volume. For anything beyond that, one email is not enough, and the setup cost of a four-workflow sequence in Krom Automation Pro is low relative to the revenue it recovers.

The post-expiry recovery email alone is worth the setup time. Most EDD stores never send one.

The customers who lapsed without renewing are still familiar with your product, still have the problem your product solves, and are reachable for 7 to 14 days after expiry before they start evaluating alternatives. A single automated message in that window, with a clear offer and a short deadline, will recover a meaningful number of those licenses every cycle.

If you run more than one EDD site, Krom Automation Pro plans cover 5 sites from $149 per year (launch pricing), which changes the per-site economics significantly compared to single-site tools. Lifetime plans start at $199 for one site and include every future update. The free plugin is available with no time limit or run cap, so you can install it and explore the workflow builder before committing to Pro.

Frequently Asked Questions

Can I send more than one EDD license expiry reminder email without a third-party plugin?

No. EDD Software Licensing supports a single reminder email at one configured interval. Sending multiple reminders at different intervals requires either a custom solution or a plugin like Krom Automation Pro that adds a delay-based sequence builder on top of EDD’s trigger events.

Will EDD send renewal reminders to customers on automatic subscriptions?

EDD Recurring Payments handles auto-billing separately from Software Licensing renewal reminders. Customers on automatic renewal do not need a manual renewal prompt, and sending one confuses them. In Krom Automation, a conditional branch checks the auto-renewal status before any email fires and skips the sequence for customers already set to renew automatically.

How do I stop customers from receiving duplicate renewal reminder emails?

Duplicates almost always come from two sources running simultaneously: EDD’s built-in reminder and a third-party workflow. Disable EDD’s built-in reminder under Downloads > Settings > Emails before activating your Krom Automation sequence. Also enable the “run once per entity” setting on each workflow to prevent the same license from triggering the same workflow twice.

Does the free version of Krom Automation support EDD triggers?

The EDD trigger set is a Pro feature. The free plugin includes 16 triggers covering WordPress users, posts, comments, media, and WooCommerce orders, but EDD license events require the Pro add-on. You can review the full comparison in the free vs Pro feature comparison.

Can I send the post-expiry recovery email through Mailchimp or another email platform instead of directly from WordPress?

Yes. Krom Automation Pro includes integrations with Mailchimp, ConvertKit, MailerLite, and ActiveCampaign, among others.

Instead of the Send Email action, you can trigger a sequence in your email platform when the EDD license expires. The Mailchimp integration documentation covers how to subscribe or tag a contact from a WordPress trigger event, which is the mechanism you would use to hand off to a Mailchimp automation.

How accurate is the expiry-day email timing on shared hosting?

On sites with steady traffic, WP-Cron fires within minutes of the scheduled time. On low-traffic sites, drift of 2 to 6 hours is common because WP-Cron only runs when a visitor request arrives.

For expiry-day emails where timing matters, configure a real server cron job to call wp-cron.php every 5 to 15 minutes. Most managed WordPress hosts provide this option in the hosting control panel without requiring server access.

You can automatically welcome new BuddyBoss members using Krom Automation, a visual workflow plugin for WordPress. The free version handles a single welcome email and a group add on registration.

A timed sequence across multiple days, a branded email design, and an incoming webhook from an external form require Pro. No code is needed for any of it.

BuddyBoss does not ship a built-in auto-welcome system. It fires the events. It stores the data.

Turning those events into a real onboarding experience requires a workflow layer on top. That is exactly what Krom Automation is built to do, and unlike SaaS automation tools, every execution log and API credential stays inside your WordPress database.

If privacy and data residency matter to your community, that distinction is worth noting. You can read more about the case for self-hosted automation in our post on self-hosted automation and GDPR.

This guide covers four specific things: the right trigger for BuddyBoss member activation, sending a welcome email with personalised merge tags, posting to the BuddyBoss activity feed, auto-adding the new member to a group, and how to prevent a workflow from firing twice on the same user. Browse the full feature list to see what else Krom Automation can do beyond member onboarding.

Quick Summary

Goal	Free or Pro?	Trigger used
Send a welcome email on registration	Free	User Registered
Add new member to a BuddyBoss group	Free (with BuddyBoss integration)	User Registered
Post to the BuddyBoss activity feed	Free (with BuddyBoss integration)	User Registered
Delay day-1 and day-2 follow-up messages	Pro (delay scheduling)	User Registered
Branded visual email template	Pro (visual email builder)	Any
Welcome via incoming webhook from external form	Pro (incoming webhook receiver)	Webhook

Does BuddyBoss Have a Built-In Auto-Welcome Feature?

No. BuddyBoss handles profile fields, groups, activity feeds and messaging. It does not include any workflow or automation layer.

When a new user registers, BuddyBoss fires a WordPress user registration event and stores the member data. What happens next is entirely up to you.

Some community owners try to handle this manually: a team member spots the new registration notification and sends a personal message. That approach breaks the moment you have more than a handful of new members per week. At 20 new members a month, manual welcome messages cost roughly 2 to 3 hours of admin time.

At 100 new members a month, the math becomes untenable. Automation is the only path that scales.

Which Trigger Should You Use for BuddyBoss Onboarding?

The correct trigger depends on your registration flow. There are two situations that require different answers.

• Standard WordPress registration with BuddyBoss: Use the User Registered trigger. This fires the moment the user record is created in WordPress. If your site has email verification disabled, this is the right choice.
• Email verification enabled: If BuddyBoss or a membership plugin requires the user to click a verification link before their account is active, trigger on User Role Changed instead. The account exists before verification, so User Registered fires too early. Role Changed fires when the account moves to an active state.
• WooCommerce or MemberPress checkout: A paid membership may be the point of registration. Trigger on the payment or subscription event rather than the user event, so the welcome sequence only fires for paying members. See the MemberPress integration docs for the exact trigger to use.

For most BuddyBoss communities without a paywall, User Registered is correct. You can see every available trigger in the free triggers reference.

Triggering a welcome email before the user has verified their account is not a minor timing issue. It trains new members to ignore your first message, because it arrives before they feel like members.

How to Build the Welcome Workflow, Step by Step

The full setup walkthrough lives in the BuddyBoss integration documentation, including exact field names and screenshots. The steps below explain the logic so you understand what you are building before you build it.

Step 1: Create a new workflow on the canvas

Open Krom Automation from the WordPress admin sidebar and click “New Workflow”. The drag-and-drop canvas opens on a blank state.

If you want a starting point, there are 20 free workflow templates included, and several cover user onboarding. You can also start from the first workflow tutorial which walks through the welcome email pattern in detail.

Step 2: Set the trigger

Drop a trigger node onto the canvas and select “User Registered”. If email verification is part of your flow, select “User Role Changed” and set the condition to match the role BuddyBoss assigns on activation.

The trigger node surfaces the available merge tags: {{user.display_name}}, {{user.email}}, {{user.login}}, and others. Read the merge tags documentation to see the full list and how to use them in action fields.

Step 3: Send the welcome email

Add a “Send Email” action node. Set the To field to {{user.email}}. Write the subject and body using merge tags so every email addresses the member by name.

A subject line like “Welcome to [Community Name], {{user.display_name}}” takes 30 seconds to configure and outperforms a generic “You have registered” notice by a measurable margin in open rates. If you are on Pro, the visual email builder replaces the plain text editor with a block-based designer that produces branded HTML emails.

Step 4: Post to the BuddyBoss activity feed

The BuddyBoss integration adds a “Create Activity Post” action. Drop it after the email node. Use merge tags to write something like “Welcome {{user.display_name}} to the community” and post it publicly to the member’s feed or to the site-wide stream.

This creates a visible social signal that other members can react to, which matters for community momentum. New members who see their name mentioned in the activity feed within minutes of joining are more likely to return within 48 hours.

Step 5: Add the member to a BuddyBoss group

The BuddyBoss integration also includes an “Add Member to Group” action. Specify the group ID you want new members to join. This works for a single default group.

If you want to assign different groups based on the user’s role, registration source or membership level, add a conditional branch first. The conditions and branching documentation covers how to build Yes/No logic into any workflow.

Step 6: Enable Run Once per entity

This is the loop protection step that almost every tutorial skips. Krom Automation includes a “Run Once per entity” setting at the workflow level. Enable it.

Without it, any event that re-fires the trigger, such as an admin updating the user profile, can re-execute the entire workflow and send the welcome email again. One setting, zero duplicate emails. You can find this in workflow settings alongside pause, notes and import/export controls.

Loop protection is not optional. A welcome email that arrives three times in ten minutes is not a welcome. It is a reason to unsubscribe.

How to Build a Multi-Day Welcome Sequence

A single email on day zero is a start. The research on community retention consistently shows that members who receive structured contact in the first 72 hours after joining are more likely to become active contributors. A three-step sequence covers the pattern most community operators use.

• Day 0, immediately: Welcome email with their name, a link to their profile, and an invitation to introduce themselves. Activity feed post. Group add.
• Day 1, 24 hours later: A short email pointing to the most active or most useful content in the community. One clear action only.
• Day 3, 72 hours later: A check-in asking if they have any questions and surfacing the support or help channel.

The delay nodes between each step are a Pro feature. You can set delays in minutes, hours, days or weeks. Drop a Delay node between your Day 0 actions and the Day 1 email, set it to 24 hours, and the workflow handles the timing automatically.

The full documentation for this is in delays and scheduling. Background execution via Action Scheduler means the delays run off page load, so a visitor hitting your site 23 hours after a member registered will not accidentally trigger the Day 1 email early.

On very low-traffic sites where WP-Cron does not fire reliably, delayed emails can arrive late. If your community runs on a shared host with sparse traffic, configure a real server cron to call wp-cron.php on a schedule. The Krom Automation documentation covers this in the installation guide.

What a Good BuddyBoss Welcome Email Actually Says

This is the part no competing tutorial covers. The automation infrastructure only matters if the message it delivers is worth reading. Most auto-welcome emails fail on content, not on timing or configuration.

A welcome email that works does three things in under 150 words:

• Confirms the decision was the right one. “You are now part of [X], a community of [specific type of people] doing [specific thing].”
• Gives one concrete next step. Not five options. One. “Start by introducing yourself in the Welcome group.”
• Sets an expectation. “You will hear from us on day one with a guide to the best content here.”

Use {{user.display_name}} in the opening line. Personalisation at the subject line level lifts open rates. Personalisation in the first sentence lifts click-through.

Both take less than a minute to add when merge tags are already available in the action field. See the merge tags reference if you want the full list of variables available on the User Registered trigger.

How to Test the Workflow Before It Goes Live

Krom Automation includes a workflow simulator that runs a dry execution against real data with zero side effects. No email is sent. No group add happens.

No activity post is created. The simulator shows you the exact path the workflow would take, which actions would fire, and what the merge tag values would resolve to for a specific user.

This is the correct way to verify a welcome sequence before exposing it to real new members. Our post on how to test a WordPress automation before it goes live walks through the full process.

What Does It Cost Compared to Alternatives?

This is the question most guides avoid. Here is an honest comparison across the tools people actually consider for BuddyBoss onboarding automation.

Tool	Year 1 cost (1 site)	Year 2 cost	Lifetime option	Per-task billing	Self-hosted
Krom Automation Pro (Basic)	$69/year (launch price)	$119/year	$199 once	No	Yes
Uncanny Automator	From $199/year (as of September 2026)	$199+/year	No	No	Yes
Zapier (Professional)	~$240/year (as of September 2026)	~$240+/year	No	Yes, with overages	No

Zapier’s per-task billing model means a busy BuddyBoss community with 500 new members a month and a 3-step sequence burns 1,500 tasks per month on welcome automation alone, before any other workflows run. At the Professional plan’s 750-task monthly cap, that community would need a higher tier from day one. Krom Automation charges nothing per execution at any plan tier.

If cost across multiple client sites matters, the Standard plan at $149/year covers 5 sites and the Enterprise plan at $299/year covers unlimited sites. Our post on how much WordPress automation costs per month breaks down the full picture across tools. All Pro plans carry a 14-day money-back guarantee.

A welcome sequence that fires 500 times a month is not expensive on a flat-fee plugin. On a per-task SaaS tool, it is a billing event that grows every time your community grows.

What the Free Version Can and Cannot Do

The free version of Krom Automation handles a practical welcome workflow without spending anything. Here is exactly where the line sits.

Free version covers:

• User Registered trigger firing on BuddyBoss registration
• Send Email action with full merge tag support
• BuddyBoss group add action
• BuddyBoss activity feed post action
• Run Once per entity to prevent duplicate executions
• Workflow simulator for dry-run testing
• Execution logs showing every step taken and every outcome

Pro is required for:

• Delay nodes for Day 1 and Day 3 follow-up emails
• Visual email builder for branded HTML templates
• Schedule trigger for recurring community digests
• Incoming webhook to trigger welcome flows from external registration forms
• Advanced conditional branching using richer trigger data

You can download the free plugin from the WordPress.org plugin directory and build the day-zero welcome sequence without a Pro licence. Upgrade when the multi-day sequence becomes the priority.

Also from wpRigel

Pollify is a poll, survey and quiz plugin built natively for the Gutenberg block editor. If you run a BuddyBoss community, embedding a poll directly in a page or post takes seconds because polls are real blocks, not shortcodes. It is a practical way to collect onboarding feedback or run member votes without installing a separate tool or pasting anything into a widget area.

Commandify adds a keyboard-first command palette to the WordPress admin. Press Cmd or Ctrl plus K and type what you need: navigate to a user, search a post, change a setting, or manage a WooCommerce order. For anyone managing a BuddyBoss community alongside a shop or course site, it is the fastest way to move around the admin without clicking through five menu levels.

FAQ

Can I trigger the welcome email only after the user activates their account, not before?

Yes. If your BuddyBoss setup uses email verification, use the User Role Changed trigger instead of User Registered.

Set it to fire when the user’s role changes to the active member role BuddyBoss assigns on activation. This ensures the welcome email arrives after the user has confirmed their address, not before.

How do I add new members to different BuddyBoss groups based on their registration source or role?

Add a conditional branch in the workflow between the trigger and the group add actions. Set the condition to check the user’s role, a registration field value, or any other property the trigger surfaces.

Each branch leads to a different “Add to Group” action. The branching documentation covers the full set of condition operators available.

Will the welcome workflow fire again if an admin edits the user’s profile later?

Not if Run Once per entity is enabled in workflow settings. That setting records the user ID on first execution and skips all future runs for the same user. Disable it only if you intentionally want the workflow to re-run, for example on a User Profile Updated trigger with a different purpose.

Does the BuddyBoss integration with Krom Automation work with BuddyBoss Pro as well as the free BuddyPress?

The triggers and actions in the BuddyBoss integration work with both BuddyBoss Pro and BuddyPress, since both use the same underlying WordPress hooks for user registration, group membership and activity feed events. Check the BuddyBoss integration documentation for any version-specific notes.

What happens if the welcome email fails to send?

Krom Automation logs every execution at the step level. If the Send Email action fails, the execution log records the failure with the reason.

You can configure failure notifications by email and set an automatic retry with configurable backoff. That means a transient mail server issue does not silently skip a new member’s welcome email.

Can I connect the welcome sequence to Mailchimp or FluentCRM at the same time?

Yes. Add an additional action node to the same workflow.

After the welcome email and group add, connect to Mailchimp to subscribe the user to an onboarding sequence, or to FluentCRM to create a contact and apply a tag. Multiple actions in a single workflow run in the order you connect them on the canvas.

The Verdict

If you run a BuddyBoss community and you are still manually welcoming new members, or relying on the generic WordPress registration email, you are leaving retention on the table. The free version of Krom Automation covers the day-zero essentials: a personalised welcome email, an activity feed post, and a group add, with loop protection so it never fires twice on the same user. That alone is worth the 20 minutes of setup.

Upgrade to Pro when the multi-day sequence becomes the priority. At $69 for the first year (launch price), the Basic plan costs less than a single hour of developer time and runs unlimited welcome workflows across one site with no per-execution fees.

See full pricing details and compare the plans before you decide. The free plugin is always available at no cost, with no trial period and no feature locked behind a signup wall.

When a MemberPress payment fails, the plugin can send a single notification email automatically. That one email recovers some members, but a single touch is rarely enough. Krom Automation, our free WordPress workflow plugin, lets you build a full recovery sequence triggered by that failed payment event, including a follow-up email 48 hours later, a Slack alert to your team, and a win-back offer if the member cancels.

The free version covers the core sequence. The Pro version adds the visual email builder and Slack integration for richer alerts.

The setup takes roughly 30 minutes end to end. The sections below walk through MemberPress configuration first, then the automation layer on top of it, then what to actually write in each message because none of the official docs cover that part.

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

What Does MemberPress Actually Do When a Payment Fails?

MemberPress handles failed payments differently depending on your gateway. With Stripe, the gateway itself retries the charge on a schedule you configure inside Stripe’s dashboard, typically 3 attempts over 7 to 14 days.

With PayPal, retry logic sits inside PayPal’s subscription settings. MemberPress does not control retry timing directly. It listens for the gateway’s webhook and reacts when a failure event arrives.

When that failure webhook lands, MemberPress can do three things automatically:

• Send a “failed transaction notice” email to the member, if the toggle is enabled in Settings
• Send the same notice to the admin email address
• Suspend or cancel the subscription depending on how many consecutive failures you allow in your gateway settings

That built-in email is a starting point, not a recovery strategy. It fires once, carries default MemberPress branding, and contains no logic for what happens if the member ignores it.

How Do I Enable the Failed Payment Email in MemberPress?

The setting is buried two levels deep. Navigate to MemberPress > Settings > Emails. Scroll to the “Failed Transaction Notice” row.

You will see two toggles: one for the member and one for the admin. Enable both.

Inside that same row, click “Edit” to open the template editor. MemberPress gives you a subject line field and a body field with a small set of merge parameters such as {member_name}, {membership_title}, and {account_url}.

The account URL parameter is important because it links the member directly to the page where they can update their card. Without it, a member who wants to fix the problem has to find that page themselves, and most will not.

A minimal subject line that performs well in practice: “Your [membership name] payment needs attention”. Keep the body under 120 words. State what happened in one sentence, give them the link to update their card in the next sentence, and close with a clear deadline so the message carries urgency.

Telling someone their payment failed is table stakes. Telling them exactly what to click and what happens if they do not act within 48 hours is what actually recovers the member.

Why Isn’t the MemberPress Failed Payment Email Sending?

This is the most common support question on this topic, and it almost always comes down to one of four causes. Work through them in this order, because the first fix resolves the problem in the majority of cases.

1. The toggle is off. MemberPress ships with the failed transaction notice disabled. Go to MemberPress > Settings > Emails and confirm both toggles are on. This takes 30 seconds to check.
2. WordPress is using wp_mail() without an SMTP relay. Shared hosting providers regularly blacklist PHP mail. Install an SMTP plugin such as WP Mail SMTP and connect it to a transactional mail service. Without this, emails either land in spam or never leave the server.
3. The transaction was not recorded as complete. MemberPress only fires the failed notice when a subscription renewal fails. A payment that never completed the initial checkout does not trigger the same hook. Check the transaction log under MemberPress > Transactions.
4. Site migration broke the gateway webhook URL. If you migrated the site and the domain changed, Stripe or PayPal may still be sending webhooks to the old URL. Log into your gateway and update the endpoint to the new domain. The MemberPress webhook URL follows the pattern yourdomain.com/?memberpress-listener=stripe.

If none of those apply, confirm the member’s email address is stored correctly under MemberPress > Members and test a manual email send using the WP Mail SMTP diagnostic tool.

What Should I Actually Write in the Failed Payment Email?

No official documentation covers this, which is why members slip away even when the email is technically sending. The goal of the first email is one action: get the member to click the account link and update their card. Everything else is noise.

A structure that converts reliably:

• Subject: “Your [Membership Name] payment didn’t go through”, plain language, no urgency theatrics on the first attempt
• Opening line: State the fact plainly. “We tried to renew your [Membership Name] subscription on [date] and the payment didn’t complete.”
• One sentence on consequence: “Your access will continue for the next 48 hours while we wait for you to update your details.”
• The link: A single, clear call to action pointing to the account page. “Update your payment method here.” No other links in the email.
• Closing: A low-pressure reassurance. “If you have questions, reply to this email and we will sort it out.”

The second email, sent 48 hours later if the payment is still unpaid, shifts tone slightly. Keep it short and raise the stakes honestly: access is about to suspend.

The third touch, if you build one, can include a discount or a personal note from the site owner. That third email is where Krom Automation earns its place, because you cannot time a manual email to fire 5 days after a specific member’s payment failure.

How Do I Build a Recovery Sequence With Krom Automation?

The MemberPress integration in Krom Automation exposes subscription and payment events as triggers. The failed payment trigger fires every time MemberPress records a failed renewal, and from that single trigger you can branch into a full sequence.

The free version of Krom Automation gives you the Send Email action, delay scheduling in minutes, hours, days or weeks, conditional branching with Yes and No paths, and merge tags to inject the member’s name and membership details into every message. That is enough to build a 3-touch recovery sequence without paying for anything.

Here is the workflow shape that recovers the most members in practice:

1. Trigger fires immediately: MemberPress failed payment event received
2. Action 1, instant: Send the first recovery email using the copy structure above
3. Delay: 48 hours
4. Conditional branch: Check whether the subscription is still in a failed state
5. Yes path (still unpaid): Send the second email with a firmer tone and a specific deadline
6. Delay: 72 more hours
7. Yes path (still unpaid): Send a win-back email with a recovery offer or a personal message
8. No path (payment recovered at any branch): Send a confirmation email and end the sequence

The delay scheduling documentation covers the exact options available and how to configure them on the canvas. The merge tags documentation shows which MemberPress fields you can inject into email subject lines and bodies.

A single email is a notification. A timed, conditional sequence is a recovery system. The difference in recovered revenue over 12 months is not marginal.

How Do I Send a Slack Alert When a Payment Fails?

Relying on an email to your admin address means you might not see a failed payment for hours. A Slack alert lands where your team already works.

The Krom Automation messaging integration covers Slack, Discord, Twilio, and Telegram. Slack alerts are a Pro feature.

The practical setup is a parallel branch on the same workflow: when the failed payment trigger fires, one branch sends the member email sequence and a second branch posts immediately to your Slack channel. The Slack message should carry the member’s name, the membership they hold, and the amount that failed.

A team that sees “Jane Smith, Pro Plan, $119 renewal failed” can make a personal follow-up call the same day. That human touch recovers members that automated emails miss.

If you run a high-volume membership site and want to see failure patterns over time, the Krom Automation analytics dashboard shows failure counts and execution trends. A workflow failing more than 10 percent of the time signals a configuration problem rather than a payment problem.

How Do I Build a Cancellation Win-Back Sequence?

Some members will not update their card in time and their subscription will cancel. That is not the end of the relationship. A win-back sequence, triggered when MemberPress records a cancellation following a failed payment, can recover 10 to 20 percent of those lapsed members over a 30-day window, based on industry benchmarks for membership sites.

The MemberPress integration trigger covers subscription cancellation events. Pair it with a 3-step win-back sequence:

• Day 1 after cancellation: A short email acknowledging the lapse, no pressure, just an open door. Include a direct re-subscribe link.
• Day 7: A value reminder email. What did they have access to? What are they missing? Keep it factual rather than emotional.
• Day 21: A time-limited offer. A discount coupon, a free month, or a content bundle. Make it specific and give it a hard expiry date.

The conditions and branching documentation shows how to stop the sequence automatically once the member re-subscribes, so you do not send a discount offer to someone who already paid.

If your membership site also runs on WooCommerce Subscriptions, the same pattern applies. See our guide on automating WooCommerce subscription renewal reminder emails for a parallel setup.

What Are the Real Limits of This Setup?

Honest constraints matter here. Three things can go wrong with this automation that the setup guides do not mention.

WP-Cron timing on low-traffic sites. Krom Automation uses Action Scheduler for background execution, which is the same queue system WooCommerce relies on. But Action Scheduler still depends on WordPress Cron firing. On a site that receives fewer than a few dozen visits per day, WP-Cron can run hours late.

A “48 hour delay” in the workflow may actually fire at 50 or 52 hours. For most membership sites this is acceptable. For high-stakes sequences where timing matters, configure a real server cron job to trigger wp-cron.php on a fixed schedule.

Gateway webhook failures are invisible to Krom Automation. If Stripe’s webhook to your site fails silently, MemberPress never sees the failed payment event, and the trigger never fires. Check your Stripe webhook dashboard monthly and confirm delivery success rates stay above 98 percent.

The free plugin does not include the visual email builder. The Send Email action in the free version sends plain HTML email. It works, and most recovery emails perform better in plain text anyway. The visual email builder is a Pro feature for teams that want branded, block-based email design matching their membership site’s look.

Cost Comparison: Manual Recovery vs. Automated Sequence

Approach	Setup time	Ongoing time per 10 failed payments	Annual cost	Recovery touches per member
MemberPress email only, manual admin follow-up	15 minutes	2 to 3 hours	Staff time only, approx. $50 to $120/month at $25/hr for a busy site	1 automated, 1 to 2 manual
Krom Automation free, 3-touch sequence	30 minutes	Under 10 minutes (review logs only)	$0	3 automated, timed and conditional
Krom Automation Pro, sequence plus Slack alerts	45 minutes	Under 10 minutes	Starts at $69/year for 1 site	3 automated, plus team Slack alert for manual follow-up
Zapier plus ActiveCampaign (external tools)	2 to 4 hours	Under 10 minutes	Zapier Professional approx. $240/year plus ActiveCampaign plan cost, as of September 2026	3 or more automated

The Zapier route works but moves your member data and execution logs off your server. If GDPR compliance matters to your membership business, self-hosted automation is a material difference. Our article on self-hosted automation and GDPR covers what actually transfers to third-party services and what does not.

Which Krom Automation Plan Do I Actually Need?

Feature	Free	Pro (from $69/year)
MemberPress failed payment trigger	Yes	Yes
Send Email action (plain HTML)	Yes	Yes
Delay scheduling (hours, days)	Yes	Yes
Conditional branching	Yes	Yes
Merge tags for member data	Yes	Yes
Execution logs and analytics dashboard	Yes	Yes
Slack / Discord / Twilio alert	No	Yes
Visual email builder (block-based)	No	Yes
Schedule trigger (daily digest of failures)	No	Yes
ActiveCampaign / FluentCRM / Mailchimp sync	No	Yes

For most membership sites running under 500 active members, the free version builds a complete recovery sequence. Pro becomes worth the $69/year once you want Slack alerts on failures, branded email templates, or CRM sync so your marketing list stays clean when a member lapses. If you run sites for multiple clients, the Standard plan at $149/year covers 5 site activations.

The free plugin covers every part of the recovery sequence. Pro earns its cost the first time a Slack alert lets someone on your team make a personal call that saves a $200/year membership.

Before You Build: Test the Workflow First

Never push a recovery sequence live without dry-running it. Krom Automation includes a workflow simulator that executes the entire flow with zero side effects.

No emails send, no delays fire, no CRM contacts update. You see exactly which branch would run and which merge tags resolve to which values.

The workflow simulator documentation covers how to load a test payload that mimics a MemberPress failed payment event. Run the simulator before you toggle the workflow to active, and run it again any time you edit a branch condition. Our article on testing WordPress automations before they go live explains the full testing approach for sequences like this one.

Also from wpRigel

Pollify is our Gutenberg native poll, survey and quiz plugin. Polls are real blocks built inside the editor, so there are no shortcodes to paste and no separate configuration screen to learn. It is the fastest way to add a membership satisfaction survey directly inside a post or page.

Commandify is a command palette for the WordPress admin. Press Cmd or Ctrl plus K to jump anywhere in the dashboard, search members and orders, and run admin actions without clicking through menus. It is the only WordPress command palette with real WooCommerce order, product and customer management built in, which makes it worth knowing about if you run a membership site with a commerce component.

Our Verdict: Who Should Act on This and Who Should Not

If you run a MemberPress site with recurring subscriptions and you have not built a multi-touch recovery sequence, you are leaving a recoverable percentage of your churned revenue on the table every month. The free Krom Automation plugin closes that gap in under an hour of setup, with no ongoing cost and no member data leaving your server.

If your membership site has fewer than 50 active recurring members, the built-in MemberPress email plus a manual admin notification is probably enough. The complexity of a 3-touch automation is not worth maintaining below that threshold. Above 50 recurring members, the math flips: even recovering 2 additional members per month at a $10/month membership price exceeds the cost of Krom Automation Pro in the first year.

Download the free Krom Automation plugin from the WordPress.org plugin directory and build the first workflow today. Upgrade to Pro only when you need Slack alerts or branded email templates. The step-by-step workflow builder guide walks through the canvas from a blank trigger to a published workflow if this is your first automation.

See all Krom Automation plans and pricing, including the lifetime options that start at $199 for a single site.

Frequently Asked Questions

Does MemberPress retry failed payments automatically?

MemberPress itself does not control retry timing. Retry logic lives inside your payment gateway. Stripe retries on a schedule you configure in the Stripe dashboard, typically 3 attempts over 7 to 14 days.

PayPal handles retries inside its own subscription settings. MemberPress listens for the gateway webhook and reacts when each failure or success event arrives.

Can I send the failed payment email to a custom address instead of the site admin?

The admin notice in MemberPress Settings > Emails sends to the address set under WordPress Settings > General. To route alerts to a different address, such as a billing team inbox, use a Krom Automation workflow with a separate Send Email action pointing to whatever address you choose. This also lets you send to multiple recipients from one trigger.

Will Krom Automation stop sending recovery emails once the member pays?

Yes, if you build the workflow with a conditional branch that checks subscription status before each follow-up email. The conditions and branching documentation shows how to add a Yes/No check so the sequence exits cleanly when the payment is recovered, without sending a discount offer to a member who has already updated their card.

How do I sync lapsed MemberPress members to my email marketing list automatically?

Add a CRM or email marketing action to the same workflow that handles the failed payment trigger. The ActiveCampaign integration, the FluentCRM integration, and the Mailchimp integration all support adding a tag or moving a contact to a different list when a trigger fires. Tag the member as “payment-lapsed” at the moment of failure so your marketing list reflects the real subscription state.

Why did my members lose access immediately after a failed payment instead of getting a grace period?

MemberPress does not have a built-in grace period setting in the way some membership plugins do. Access suspension is controlled by your gateway’s retry window and the subscription status MemberPress receives via webhook.

If your gateway cancels the subscription after the first failed attempt, MemberPress marks the subscription as cancelled immediately. Extend the grace period by configuring more retries inside your gateway dashboard before it marks the subscription as failed.

Can I use this setup across multiple MemberPress sites for client work?

Yes. Krom Automation Pro Standard covers 5 site activations at $149/year, and the Enterprise plan covers unlimited sites at $299/year.

The workflow you build on one site exports as a portable JSON file that you can import on any other site running Krom Automation. The workflow settings documentation covers the import and export process.

Yes, self-hosted automation is generally better for GDPR than cloud services like Zapier, but it does not make you automatically compliant. With Krom Automation, a WordPress-native workflow plugin, every execution log, credential and piece of personal data processed by a workflow stays inside your own database.

That removes Zapier or Make as a data processor under Article 28 of the GDPR, which is a meaningful reduction in third-party risk. The free plugin covers the core controls; Pro adds incoming webhooks and advanced integrations for teams with more complex pipelines.

Cloud automation platforms route your data through servers you do not control, often in the United States. That matters because Schrems II invalidated the EU-US Privacy Shield in 2020, and any transfer of EU personal data to a US processor requires either Standard Contractual Clauses or another lawful transfer mechanism. Your DPA with Zapier covers this on paper, but the underlying data still travels across the Atlantic and sits in infrastructure you cannot audit.

Self-hosting changes the structure of that risk. Your data stays on your server, in your jurisdiction, in your database.

You can choose an EU hosting provider, apply your own retention rules, and delete execution logs on a schedule that matches your privacy policy. None of that is possible when the data lives in someone else’s SaaS.

Browse the full Krom Automation feature list

What Changes When You Self-Host Automation

When you use Zapier or Make, those platforms become data processors under GDPR Article 28. You must sign a Data Processing Agreement with them, and they in turn rely on their own subprocessors, adding more links to the chain. Self-hosting removes that processor relationship entirely for the automation layer itself.

With Krom Automation installed on your WordPress site, the workflow engine runs inside your own application. Triggers fire, actions execute, and logs are written, all to your own database. No data leaves your server unless a specific action in the workflow sends it somewhere, such as an HTTP request to a third-party API.

That last point matters. Self-hosting the automation platform does not automatically self-host everything the automation touches.

If a workflow sends a contact’s email address to Mailchimp, Mailchimp is still a processor for that data. The Mailchimp integration documentation describes exactly what fields are transmitted, which is useful when documenting your Records of Processing Activities.

Self-hosting removes the automation platform as a processor. It does not remove the obligation to document every destination that personal data reaches inside your workflows.

Where Your Data Lives With Krom Automation

Krom Automation stores everything in 9 custom database tables inside your WordPress installation. This includes trigger event data, action parameters, execution logs with a full per-step audit trail, and any merge tag values captured at runtime. Your hosting provider is the only infrastructure party involved.

The analytics dashboard shows total executions, active workflows and failed execution counts. That same data is what you would reference in a GDPR audit or a Data Subject Access Request response, because it tells you exactly which workflows touched a given user’s data and when.

If you choose an EU-based hosting provider such as Hetzner, OVHcloud or Scaleway, the entire automation stack, including logs, sits inside the EU. That eliminates the Schrems II transfer question for the automation layer. No SCCs required, no transfer risk to document, no US cloud infrastructure in the processing chain for that component.

The GDPR Obligations Self-Hosting Does NOT Remove

This is the section that most self-hosting guides skip, and it is the one that gets teams into trouble. Self-hosting removes one processor relationship. It does not replace a lawful basis for processing, a retention policy, or a breach response plan.

The obligations that remain regardless of where your automation runs:

• Lawful basis: Every automated action that processes personal data needs a lawful basis under Article 6. “We have a workflow” is not one. Consent, legitimate interest or contract performance must be documented.
• Data Subject Access Requests (DSARs): If a contact requests their data, you must provide everything you hold, including anything captured in automation execution logs. Krom’s per-step audit trail makes this answerable, but you still need a process to handle the request within 30 days.
• Right to erasure: Deleting a contact from your CRM does not automatically purge their data from execution logs. You need a retention policy that covers your workflow history, and you need to enforce it.
• Data Protection Impact Assessments (DPIAs): Automated processing that is likely to result in high risk to individuals requires a DPIA under Article 35. Self-hosting does not change that obligation. If you automate credit scoring, health-related segmentation or systematic profiling, a DPIA is required.
• Breach notification: If your server is compromised and execution logs containing personal data are exposed, you have 72 hours to notify your supervisory authority. Self-hosting means the breach is yours to detect and report.
• Records of Processing Activities (RoPA): Article 30 requires a record of every processing activity, including automated ones. Each workflow that touches personal data should have an entry in your RoPA describing the purpose, the legal basis, the categories of data, and the recipients.

The biggest GDPR mistake with self-hosted automation is believing that moving data to your own server is a compliance strategy. It is a risk reduction step. The governance work still applies.

Does Krom Automation Require Pro for GDPR-Relevant Controls?

The free version of Krom Automation includes the controls most sites actually need for privacy-conscious automation. The execution log with a full per-step audit trail is free. Workflow import and export as portable JSON is free.

The run-once-per-entity setting, which prevents a workflow from processing the same user twice, is free. The workflow simulator for dry-run testing with zero side effects is free, which matters when you are testing a workflow that would otherwise write to a real user’s record.

Pro adds capabilities that become relevant as workflows grow in complexity:

• The incoming webhook receiver with HMAC-SHA256 signature verification and 9 security layers, for receiving data from external systems without exposing a generic endpoint. See the incoming webhook documentation for the signature verification setup.
• The schedule trigger, useful for running automated data retention or cleanup workflows on a daily or weekly cadence. The schedule trigger documentation covers interval options including one-time runs.
• Advanced conditional branching, so a workflow can route differently based on a user’s consent status or data category.
• 25 integrations with forms, CRMs, email platforms and membership plugins, each of which represents a potential data destination that needs to appear in your RoPA.

For most WordPress sites, the free plugin is the right starting point. The free vs Pro comparison lays out exactly which features sit at which tier.

Comparing Cloud Automation to Self-Hosted on the Dimensions That Matter for GDPR

Dimension	Cloud (Zapier, Make)	Self-Hosted (Krom Automation)
Where execution logs live	Vendor’s servers, typically US	Your own database
Article 28 processor relationship	Required, DPA with vendor needed	None for the automation layer
Schrems II transfer risk (automation layer)	Present if vendor uses US infrastructure	Eliminated with EU hosting
Subprocessor chain	Vendor plus their subprocessors	Only the services your workflows call
Credential storage	Vendor’s encrypted store	Your WordPress database
Retention control over logs	Subject to vendor’s retention policy	Fully configurable by you
DSAR response for automation data	Requires vendor cooperation	Direct database query, no third party
Breach ownership	Shared with vendor	Yours entirely
Lawful basis requirement	Still required	Still required
DPIA requirement for high-risk processing	Still required	Still required

The Schrems II Question, Answered Concisely

Schrems II applies to transfers of EU personal data to third countries, specifically where those countries lack an adequacy decision or where the transfer mechanism (such as SCCs) cannot be demonstrated to protect the data in practice. The US falls into a complicated category: the EU-US Data Privacy Framework restores some adequacy coverage, but it has faced legal challenges and its long-term status is uncertain.

When you use a cloud automation platform headquartered in the US, your workflow data, including the personal data of EU contacts, is processed on their infrastructure. Even with SCCs in place, the underlying legal risk is real, especially for organisations subject to regulatory scrutiny.

Self-hosting on EU infrastructure eliminates this transfer entirely for the automation layer. The data never leaves your server, so no transfer mechanism is needed and no adequacy question arises. That is a clean legal position, not just a practical convenience.

What Cloud Automation Genuinely Does Better

Honest trade-offs matter here. Cloud platforms like Zapier connect two external services with no WordPress involvement, which self-hosted WordPress automation cannot do natively. If your workflow connects Salesforce to HubSpot with no WordPress touchpoint, Krom Automation is not the right tool.

Cloud platforms also handle infrastructure. Updates, uptime monitoring, scaling under load, and backup are all the vendor’s problem. Self-hosting shifts that responsibility to you or your hosting provider.

On a shared host with poorly configured server cron, WP-Cron timing can be unreliable. Scheduled automation and delayed actions depend on WordPress Cron firing on schedule, which requires real server cron configuration on low-traffic sites. The delays and scheduling documentation explains how to configure this correctly.

Teams already running hundreds of Zapier workflows should factor in migration cost honestly. Moving existing automations to a new platform takes time, typically 30 minutes to 2 hours per complex workflow depending on how many steps and integrations are involved.

How Cloud Automation Pricing Compares Over Time

Scenario	Zapier Professional (as of September 2026)	Krom Automation Pro (Standard)
Cost in year 1, 1 site	~$240/year (750 tasks/month)	Starts at $69/year (launch pricing)
Cost in year 2, 1 site	~$240/year, recurring	$69/year, or $199 once (lifetime)
Cost at 5 sites	~$240/year per account (no multi-site)	$149/year covers 5 activations
Task or execution limits	750 tasks/month, overage charges apply	No per-execution billing at any tier
AI actions	Premium add-on tier required	Included free, bring your own API key
Execution data ownership	Vendor’s servers	Your server

Zapier’s per-task billing model means a high-traffic Black Friday campaign or a sudden registration spike costs more than the monthly plan suggests. How much Zapier can cost during Black Friday is a real calculation worth running before a busy period. Krom Automation has no execution caps at any tier, so a workflow that fires 10,000 times in a day costs the same as one that fires 10 times.

AI Actions and Privacy: What You Need to Know

Krom Automation includes three AI actions in the free version: AI Generate Text, AI Content Moderation, and AI Auto-Tag. These use the API key you supply, and the request goes directly from your server to the AI provider. wpRigel never sees the content, never charges per token, and does not sit in the middle of the request.

The providers supported are OpenAI (GPT-4o Mini, GPT-4o), Google Gemini (Gemini 2.0 Flash, Gemini 2.5 Flash Preview, Gemini 2.5 Pro Preview) and Groq (Llama 3.3 70B, Llama 3.1 8B). Each of these is a data processor for any personal data included in the prompt. If your AI workflow sends a customer’s name or email to an AI API, that provider needs to appear in your RoPA and your DPA list.

If your compliance position requires keeping AI inference entirely on-premise, you would need a locally hosted model, which Krom Automation’s HTTP Request action can reach but which requires separate infrastructure. That is outside the scope of the plugin itself, but the full actions reference covers the HTTP Request action parameters that make external API calls possible.

Bringing your own API key is not the same as keeping data on your server. Every AI action that processes personal data creates a new processor relationship that needs to be documented.

Setting Up Krom Automation for Privacy-Conscious Workflows

Installing Krom Automation takes the same path as any WordPress plugin. The installation documentation covers both the free and Pro setup. Once installed, the first practical step for a privacy-conscious deployment is reviewing which triggers capture personal data and where the corresponding actions send it.

A workflow that fires on User Registered and sends a welcome email stays entirely inside your server if you use the Send Email action. A workflow that fires on the same trigger and adds the user to Mailchimp creates a processor relationship with Mailchimp. The how Krom Automation works documentation explains the trigger-action model in full, which is the right starting point for mapping your processing activities.

For teams using form integrations as the entry point for personal data, the integration documentation for Gravity Forms, Contact Form 7 and WPForms each describe exactly which fields are available as trigger data, making it straightforward to document what personal data enters each workflow.

Also from wpRigel

Pollify is wpRigel’s Gutenberg-native poll, survey and quiz plugin. Polls are built directly inside the block editor as real blocks, with no shortcodes to paste and no separate configuration interface to learn. It is the natural companion if you collect audience feedback alongside automation.

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

Our Verdict

Self-hosted automation is genuinely better for GDPR than cloud services on the dimensions that matter most: data residency, processor relationships, credential storage and log retention control. Krom Automation delivers all of those advantages as a WordPress plugin that requires no cloud account, no subscription to a third-party automation service, and no per-execution billing.

Who should act on this: agencies managing client sites in regulated industries, SaaS founders whose user data must stay in the EU, and any team that has looked at their Zapier DPA and felt uncertain about what it actually covers. The free plugin is the right starting point for most sites, and a realistic look at automation costs usually makes the case for switching clear. You can download Krom Automation free from the WordPress.org plugin directory with no trial period and no feature caps.

Who should not switch yet: teams with hundreds of existing Zapier flows connecting external services that have no WordPress component. Migration has a real time cost, and if the automation does not touch WordPress, Krom Automation is not the right fit. Everyone else should run the numbers.

See Krom Automation pricing and compare plans

Frequently Asked Questions

Does self-hosting automation make me automatically GDPR-compliant?

No. Self-hosting removes the automation platform as a third-party processor, which is a meaningful reduction in risk.

But you still need a lawful basis for every processing activity, a retention policy covering your execution logs, a process for handling DSARs within 30 days, and a DPIA for any high-risk automated processing. Compliance is a governance question, not an infrastructure one.

Do I still need a Data Processing Agreement if I run automation on my own server?

You do not need a DPA with your automation platform if it is self-hosted, because there is no processor relationship for that layer. You will still need DPAs with any third-party services your workflows send data to, such as email marketing platforms, CRMs or AI providers. Every external destination your workflow reaches is a potential processor.

What happens to personal data in execution logs when I delete a contact?

Deleting a contact from your CRM or WordPress user table does not automatically remove their data from automation execution logs. You need a defined retention policy for your log data and a mechanism to enforce it.

Krom Automation stores logs in your own database, so you control deletion directly. The right approach is to set a log retention period in your privacy policy and run a scheduled workflow or database cleanup to match it.

Do I need a DPIA for automated data processing even if I self-host?

Yes, if the processing is likely to result in high risk to individuals. The DPIA requirement under Article 35 applies to the nature of the processing, not the infrastructure running it. Automated profiling, systematic monitoring of publicly accessible areas, and large-scale processing of special category data all trigger the DPIA obligation regardless of where the automation runs.

If my self-hosted automation runs in the EU, do Schrems II transfer rules still apply?

Not to the automation layer itself. If the automation and your server are both in the EU, no international transfer occurs for that component.

Schrems II transfer rules apply when data moves to a third country, so keeping both the site and the automation engine on EU infrastructure eliminates that obligation for the workflow platform. Any action that sends data to a US-based service creates a transfer that still needs a lawful mechanism.

Can I process EU customer data in automated workflows without consent?

Consent is one lawful basis under Article 6, but it is not the only one. Contract performance, legitimate interest and legal obligation are all valid alternatives depending on the purpose.

What you cannot do is process EU personal data in automated workflows without any documented lawful basis at all. The basis needs to be determined before the workflow runs, not after someone asks.

WordPress automation costs $0 to roughly $20 per month for most sites, and that range is driven almost entirely by one decision: self-hosted plugin or per-task SaaS. Krom Automation is a self-hosted option that is free forever in its base form, with a Pro licence starting at $69 per year (about $5.75 per month) and no per-task fees at any tier. Zapier’s Professional plan runs around $240 per year at the time of writing, billed for 750 tasks a month, with overage charges if you exceed that cap.

The gap between those two numbers is real, and it compounds. A small WooCommerce store running 2,000 automated actions a month pays nothing extra with a self-hosted plugin.

On a task-based SaaS, the same volume can push you into a higher tier before the year is out. Understanding what drives that cost is the only way to budget this honestly.

This article covers the full cost picture: free tools, Pro licences, SaaS fees, and the hidden costs that never appear on the pricing page. We include two worked examples so you can map the numbers to your own situation.

Browse the full Krom Automation feature list to see what the free version includes before you decide whether Pro is worth it.

What Drives WordPress Automation Costs?

There are three cost models in the WordPress automation space, and they behave very differently at scale.

• Self-hosted plugin, flat fee: You pay once per year (or once for a lifetime licence). Every workflow, every trigger, every execution is included. The cost does not change whether you run 100 automations a month or 100,000.
• Per-task SaaS: You pay for each action the tool executes. Zapier calls these tasks. At low volume the monthly fee looks modest. At high volume, or during a busy event like a product launch, costs spike without warning.
• Free plugin, no ceiling: Some self-hosted plugins offer a genuinely free tier with no run cap and no feature lock. Krom Automation’s free version includes 16 triggers, 21 actions, and full execution logging. There is no trial period and no artificial limit that forces an upgrade.

The choice between these three models is the most important budget decision you will make, not which specific features a tool offers.

What Does WordPress Automation Actually Cost? A Summary

Tool / Approach	Monthly Cost	Per-Task Fees	Lifetime Option
Krom Automation Free	$0	None	N/A (always free)
Krom Automation Pro (Basic, 1 site)	~$5.75/mo (billed $69/yr)	None	$199 one payment
Krom Automation Pro (Standard, 5 sites)	~$12.40/mo (billed $149/yr)	None	$399 one payment
Uncanny Automator (as of September 2026)	from ~$16.60/mo (billed $199/yr, 1 site)	None	Not available
Zapier Professional (as of September 2026)	~$20/mo (billed ~$240/yr, 750 tasks/mo)	Yes, overage charges apply	Not available

Per-task billing is not a pricing model. It is a variable cost with no ceiling, and it punishes success. A product launch that doubles your automation volume can double your bill with no warning.

The Free Version: What You Actually Get for $0

Krom Automation’s free plugin, available from the WordPress.org plugin directory, includes everything a small site needs to automate its core workflows. There is no trial expiry and no execution cap.

The free version covers:

• 16 triggers across users, posts, comments, media and WooCommerce orders
• 21 actions including send email, create or update posts, manage users, HTTP requests, and three AI actions
• 20 ready-made workflow templates so you are not starting from a blank canvas
• Visual drag-and-drop workflow builder on a ReactFlow canvas
• Conditional branching with Yes and No paths, delay scheduling, and merge tags
• Full execution logging with a per-step audit trail
• Analytics dashboard showing total executions, active workflows, and failure counts

AI actions are included in the free version with no paywall. You bring your own API key from OpenAI, Google Gemini or Groq, and you pay your AI provider directly at their standard rates. We never charge per AI call or mark up tokens.

For a single site running standard automations, such as sending a welcome email when a user registers or notifying your team when a form is submitted, the free version covers all of it without spending a cent.

When Does Pro Make Financial Sense?

The free version covers 16 triggers and 21 actions. Pro adds 80+ additional triggers, 60+ additional actions, 25 integrations with third-party tools, and 101 additional workflow templates. The question is not whether Pro has more features.

It does. The question is whether those extra features save more than the licence costs.

Pro-only features that tend to tip the decision:

• 25 integrations covering email marketing (Mailchimp, ConvertKit, MailerLite, ActiveCampaign), CRM (FluentCRM), LMS (LearnDash, TutorLMS), membership (MemberPress), messaging (Slack, Discord, Telegram), and data storage (Google Sheets, Google Calendar)
• Schedule trigger for hourly, daily, weekly or monthly workflows without a separate cron plugin. See the schedule trigger documentation for setup details.
• Incoming webhook receiver with a unique secret URL and HMAC-SHA256 signature support, so external services can push data into your WordPress workflows. The webhook receiver documentation covers the 9 security layers involved.
• Visual email builder for designing transactional emails with block-based formatting, documented in the visual email builder guide
• AI workflow generation: describe an automation in plain English and get a working workflow in seconds

If your site connects WordPress to an external CRM or email platform, Pro pays for itself in the first month if it replaces even one hour of manual data entry. At $69 per year for a single site, the threshold is low.

Read the full free vs. Pro feature comparison to see exactly what each tier includes before committing.

Worked Example 1: A Small WooCommerce Store

A store running on WooCommerce with roughly 200 orders a month might automate the following: order confirmation with a custom transactional email, a review request email three days after delivery, a Slack notification when a high-value order lands, and a Google Sheets row created for every completed order.

That is four workflows, running perhaps 800 to 1,000 automated actions per month total.

Approach	Year 1 Cost	Year 2 Cost	Notes
Krom Automation Free	$0	$0	Handles order triggers natively; Slack and Sheets require Pro
Krom Automation Pro (Basic, 1 site)	$69	$69	All four workflows covered; flat fee regardless of order volume
Zapier Professional (as of September 2026)	~$240	~$240+	750 tasks/mo cap; 1,000 actions/mo risks overage on busy months

The review request email workflow and the Google Sheets export are documented in detail. See the WooCommerce review request email guide and the Google Sheets order sync guide for exact setup steps.

Over two years, the difference between Krom Automation Pro and Zapier Professional is $342 for a single site running a modest order volume. That gap widens if your order count grows, because Pro’s cost stays fixed.

Worked Example 2: An Agency Managing 10 Client Sites

An agency typically needs automation on every client site: welcome emails, form notifications, CRM sync, and occasionally webhook connections to external tools. Running 10 sites on Zapier means either 10 separate accounts or one account sharing a task cap across all clients, which rarely works cleanly.

With Krom Automation, the Standard plan covers 5 site activations at $149 per year. Two Standard plans cover 10 sites for $298 per year, roughly $24.80 per month total. The Enterprise plan at $299 per year covers unlimited sites.

• 10 sites on Zapier Professional: approximately $2,400 per year if each site has its own account, or one shared account with a task cap that will almost certainly need upgrading
• 10 sites on Uncanny Automator (as of September 2026): plans from $199 per year for one site; multi-site pricing is separate and climbs quickly
• 10 sites on Krom Automation Enterprise: $299 per year for unlimited sites

The agency case is where flat per-site pricing breaks down for SaaS tools and where self-hosted licensing becomes a real financial advantage. A $299 per year Enterprise licence covers all current and future client sites with no renegotiation.

For agencies, the licensing model matters more than the feature list. A tool that charges per site forces a conversation with every new client. A flat unlimited licence removes that friction entirely.

The Hidden Costs No Pricing Page Mentions

The headline fee is never the full cost. These are the items that show up later.

• Migration time: Moving existing workflows from Zapier or Make to a new tool takes real hours. A simple five-step workflow might take 30 minutes to rebuild and test. Twenty workflows is easily two days of a developer’s time at $80 to $150 per hour.
• WP-Cron timing on low-traffic sites: Krom Automation uses Action Scheduler for background execution, which depends on WordPress Cron. On sites that receive very little traffic, WP-Cron fires late. Delayed executions are the symptom. A real server-side cron job (configured in your host’s cPanel or via SSH) is the fix, and it costs nothing to set up but does require knowing it exists.
• AI API costs: The AI actions in Krom Automation are free to use, but you pay your AI provider directly. OpenAI GPT-4o Mini costs roughly $0.15 per million input tokens at standard rates. For most WordPress sites running AI auto-tagging or content moderation, actual monthly API spend is under $2. Heavy text generation workflows cost more.
• Support tier mismatches: Krom Automation Pro includes support for the duration of your licence. If you buy an annual plan and have a critical issue in month 11, you are covered. Some competing tools limit support to 6 months or offer it only on higher tiers.
• Task overages on SaaS tools: A Black Friday sale that generates 3,000 orders in 48 hours means 3,000+ triggered automations. On a task-based tool with a 750-task monthly cap, that single event can generate overage charges larger than your typical monthly fee.

What the Free Version Cannot Do (Be Honest Here)

The free version is genuinely capable, but there are real limits. Knowing them upfront is more useful than discovering them after building workflows.

• No third-party integrations: Connecting to Mailchimp, FluentCRM, LearnDash, Slack or Google Sheets requires Pro. The free version’s HTTP Request action can reach any REST API, but you configure headers and payloads manually rather than using a purpose-built integration.
• No scheduled trigger: Running a workflow on a recurring schedule (daily digest, weekly report) requires Pro. The free version responds to events but cannot initiate them on a timer.
• No incoming webhook receiver: Receiving data from an external service requires Pro. If Stripe, Typeform or any other SaaS tool needs to push data into your WordPress site, that is a Pro feature.
• No visual email builder: The free Send Email action sends plain or basic HTML email. The block-based visual builder is Pro only.
• No AI workflow generation: Building a workflow from a plain-English description is Pro only. The free version includes AI actions (generate text, moderate content, auto-tag) but not AI-assisted workflow creation.

Before building your entire workflow library on the free version, check the full free triggers reference and full free actions reference so there are no surprises.

What Automation Saves Versus What It Costs

Every other cost breakdown in this category focuses on cost-in. This section looks at cost avoided, because that is the number that justifies the spend.

A small WooCommerce store handling review request emails manually spends roughly 2 minutes per order following up. At 200 orders a month, that is 400 minutes (6.7 hours) of someone’s time.

At a conservative internal rate of $25 per hour, that is $167 per month in labour for one workflow alone. Automating it with Krom Automation Pro costs $5.75 per month.

An agency managing onboarding emails, CRM sync and form notifications across 10 client sites might spend 3 to 5 hours per month on tasks that a working automation handles instantly. At $80 per hour, that is $240 to $400 per month in developer time. The Enterprise licence costs $24.90 per month.

The ROI case for automation is not subtle. The question is not whether to automate. It is which tool to use and how to avoid overpaying for the execution model.

The ROI calculation is never about the licence fee. It is about what you stop paying for the moment the workflows run themselves.

Which Integrations Are Worth the Pro Upgrade?

If any of the following integrations are relevant to your site, Pro is almost certainly worth the upgrade cost. Each one has full documentation covering triggers, actions and setup examples.

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

If none of those integrations apply to your site, the free version handles the vast majority of on-site automation needs. The free plugin is available directly from the WordPress.org plugin directory with no account required to get started.

Also from wpRigel

Pollify is wpRigel’s 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 configure. It ships with a free version and Pro plans from $79 per year.

Commandify is a command palette for the WordPress admin. Press Cmd or Ctrl + K to search everything, jump to any screen, and run admin actions without navigating menus. It is the only WordPress command palette with real WooCommerce order, product and customer commands built in.

Our Verdict: Who Should Pay and Who Should Not

If your site runs standard WordPress events and you need fewer than 16 triggers and 21 actions, download the free version and use it indefinitely. There is no pressure to upgrade and no feature that unlocks after a trial period. Start with the first workflow guide and have something running in under 20 minutes.

If your site connects to an email list, a CRM, an LMS, or any external tool via webhook, Pro at $69 per year is a straightforward decision. The cost is recovered in the first month if it eliminates even 45 minutes of manual work.

If you are an agency managing five or more client sites, the Standard plan at $149 per year or the Enterprise plan at $299 per year is the only model that scales without renegotiating costs for every new client. We would not run client workflows on a per-task SaaS tool at any price, because the billing is unpredictable and the data leaves your infrastructure.

Who should not act yet: teams already running hundreds of existing flows on an external automation platform. Migration is a real cost.

If that platform is working and the workflows are stable, the switching cost may outweigh the licence savings in year one. The maths changes significantly in year two when you stop paying annual SaaS renewal fees.

See current Krom Automation pricing and compare all three plans.

Frequently Asked Questions

Does the free version of Krom Automation have any run limits or expiry?

No. The free version is free forever with no execution cap, no workflow limit, and no trial period. The 16 triggers, 21 actions, and 20 templates remain available indefinitely without upgrading.

Do AI actions in Krom Automation cost extra per use?

Krom Automation never charges per AI call. You supply your own API key from OpenAI, Google Gemini or Groq, and you pay that provider directly at their published rates. For most sites, actual monthly AI API spend is under $2.

Is there a per-task or per-execution charge at any Pro tier?

No. Every Krom Automation plan, including the free version, runs unlimited executions with no per-task fee. The only difference between plans is the number of site activations.

What happens to my automations if I do not renew my Pro licence?

Workflows continue to run using whatever features existed in your last installed version. You lose access to updates and new Pro features after expiry, but existing workflows are not disabled. Lifetime plans include updates permanently with no renewal required.

Can Krom Automation replace Zapier for WordPress-to-WordPress workflows?

For workflows where both the trigger and the action touch your WordPress site, yes. Krom Automation is self-hosted and WordPress-native.

It is not designed for automations between two external services that have no WordPress involvement. For those cases, a dedicated SaaS tool is still the right choice.

Why does delay scheduling sometimes fire late on my site?

Krom Automation uses Action Scheduler for background execution, which relies on WordPress Cron. On low-traffic sites where no page request triggers WP-Cron for hours, delayed actions fire late. The fix is a real server-side cron job configured at your host.

It costs nothing to set up and resolves the timing issue permanently. See the delays and scheduling documentation for setup guidance.

The short answer: use a workflow simulator to run the automation against real trigger data without sending emails, creating users, or touching any live records. Krom Automation includes a built-in simulator in the free plugin, zero Pro upgrade required. You get a full step-by-step audit trail showing exactly what each action would have done, which lets you catch broken merge tags, wrong conditions, and misconfigured delays before a single real contact is affected.

Most automation plugins give you one testing method: trigger the event manually and hope the logs catch a failure. That works until it doesn’t.

A welcome email firing 200 times at registration because your “run once” setting was off is an expensive lesson. This guide covers every layer of pre-launch testing, from the simulator to execution logs to a structured checklist you can run in under 30 minutes.

If you want to understand how Krom Automation structures triggers and actions before diving into testing, the how Krom Automation works documentation is the right starting point. Then come back here for the testing layer on top.

Browse the full feature list to see what the free plugin includes before you start building.

What Does “Testing an Automation” Actually Mean?

Testing a WordPress automation is not the same as testing that your site loads. Site testing tools like PHPUnit, WP-CLI, and Cypress confirm that code runs correctly. They cannot tell you whether your business logic works: whether the right tag gets applied, whether the welcome email contains the right user’s name, or whether a coupon fires only for orders over a specific amount.

Automation testing has four distinct layers, and most site owners skip three of them:

• Simulator testing: a dry run that evaluates every step without executing side effects, so no emails send and no records change
• Step-level log review: reading the per-step audit trail after a real or simulated execution to confirm each action resolved correctly
• Run-once verification: confirming the workflow won’t fire twice for the same contact, order, or post
• Edge case testing: triggering the workflow with incomplete, unexpected, or boundary-condition data to see where it breaks

Skipping any of these is how a workflow that “works in testing” fails in production at 3am on a Friday.

How the Krom Automation Workflow Simulator Works

The workflow simulator is a dry-run mode built directly into the visual canvas. You open a workflow, launch the simulator, provide sample trigger data, and Krom Automation evaluates every node in sequence without executing any real action.

What that means in practice:

• No email is sent to any address
• No user is created or modified
• No post is published or updated
• No HTTP request fires to an external service
• No WooCommerce order or coupon is touched

The simulator still resolves every merge tag, evaluates every conditional branch, and calculates every delay. You see the full execution path, including which branch a Yes/No condition would take with your sample data. If a merge tag is broken, the simulator shows the unresolved output rather than a real email hiding the failure behind a blank field.

A workflow that “passed testing” because you checked the inbox, not the logs, is a workflow you haven’t actually tested.

The simulator is available in the free plugin. You do not need a Pro licence to run dry tests on any workflow you can build in the free tier.

How to Read Step-Level Execution Logs

After a real execution, or after triggering a workflow manually for a controlled test, Krom Automation writes a full per-step audit trail. Each log entry shows the action that ran, the data it received, whether it succeeded or failed, and the timestamp.

This matters because a workflow can succeed overall while individual steps silently degrade. An HTTP request action that returns a 200 status but an empty response body looks like a pass until you read the log and see the response contained an error message from the downstream API.

To get useful information from the logs, check four things for every step:

1. Status: success, failed, or skipped. A skipped step usually means a condition branch routed away from it, which may or may not be correct.
2. Resolved merge tag values: confirm the user’s name, email, and any dynamic field matched the test contact, not a placeholder or an empty string.
3. Output from external actions: for integrations like Mailchimp, FluentCRM, or Google Sheets, the log records the API response. A 401 or 403 response means your API credentials are wrong before the workflow goes anywhere near a real contact.
4. Delay resolution: if you have a delay node set to 3 days, confirm the scheduled execution timestamp in the log is actually 3 days out, not 3 minutes because a unit setting was wrong.

The delays and scheduling documentation covers exactly how delay nodes calculate their fire times, which is worth reading before your first real-world test with a delay node involved.

Why Run-Once Enforcement Is a Testing Variable, Not a Safety Net

Krom Automation includes run-once per entity enforcement, which prevents a workflow from executing more than once for the same user, post, or order. This is not a testing feature; it is a production safeguard. But it directly affects how you test.

If you trigger a workflow with a real test user during development and the run-once flag is set, that user’s next registration event, form submission, or order will not retrigger the workflow. Your test has consumed the trigger for that contact. You need either a fresh test user for each live test run or a clear understanding of when to reset the run-once flag before a second pass.

The workflow settings documentation covers run-once configuration, including when to enable it and when to leave it off during active development.

Run-once enforcement protects your contacts in production. During testing it silently blocks your second test run if you forget to account for it.

Testing Merge Tags Without Sending Real Emails

Merge tags pull live event data into action fields: the user’s first name, their email address, the order total, the post title. A merge tag that resolves correctly in the simulator but fails in production usually means the data path differs between your test trigger and the real trigger.

The fastest way to validate merge tags before going live:

• Run the simulator with sample data that includes edge cases: a user with no last name set, an order with no coupon, a post with a title containing special characters
• Check the simulator output for empty strings or unresolved tag placeholders rather than correct values
• For email actions, send a real test to a personal inbox using a test user, and read the rendered email rather than assuming the template is correct
• Review the merge tags documentation to confirm the exact syntax for any tag you are using, especially for WooCommerce order data which has more fields than user or post data

One merge tag error in a welcome email subject line means every new user gets a broken subject until you catch it. Five minutes in the simulator is cheaper.

Testing Conditional Branching

Conditional branches split a workflow into Yes and No paths based on data from the trigger. Testing one path is not testing the workflow. You need to verify both branches resolve to the correct next step, and that the condition itself evaluates correctly against your intended data.

Common branching failures during testing:

• A condition checking user role returns the wrong result because the comparison is case-sensitive and the role name in the database uses a different capitalisation than expected
• A numeric condition checking order total treats the value as a string, so “100” does not equal 100
• The No branch is set to “do nothing” but the intent was to send a different email, and nobody noticed during testing because only the Yes path was checked

Run the simulator at least twice for any workflow with a conditional branch: once with data that should take the Yes path and once with data that should take the No path. Confirm both execution paths in the simulator output before you set the workflow to active. The conditions and branching documentation covers the available comparison operators and the data types each condition supports.

The Pre-Launch Checklist: 8 Things to Verify Before Activating Any Workflow

Work through these in order. Items 1 through 4 catch the failures that happen immediately after activation. Items 5 through 8 catch the failures that surface a week later when you are not watching.

1. Simulator pass with edge-case data: run at least one simulation with incomplete or boundary data, not just your ideal test case
2. Merge tag resolution confirmed: every dynamic field in every action shows the expected value in the simulator output
3. Both branches of every condition verified: Yes path and No path have both been tested and both lead to the intended next step
4. Run-once setting matches your intent: if the workflow should fire every time (a notification, for example), run-once should be off; if it should fire only once per user, confirm it is on
5. Delay units checked: every delay node shows the correct unit, minutes versus hours versus days, not the default left unchanged from a copy-paste
6. API credentials validated for integrations: any action connecting to an external service (email marketing, CRM, messaging) has been tested with a real execution against a test contact to confirm the credentials work
7. Failure notification email set: Krom Automation can notify you by email when a workflow execution fails; confirm the address is set and points somewhere someone reads
8. Analytics baseline noted: record the current execution count before you activate the workflow, so you can see immediately whether it fires at the expected rate during the first 24 hours

Testing WooCommerce Automations Without Processing Real Payments

WooCommerce has a built-in test mode. With WooCommerce Payments or Stripe in test mode, you can place orders using Stripe’s test card numbers and generate real Order Created and Order Completed events without charging anyone. Krom Automation’s WooCommerce triggers fire on those test orders exactly as they would on real ones.

This matters for workflows like post-purchase email sequences, coupon generation, course access grants, and subscription automations. If you are building a subscription renewal reminder, the WooCommerce subscription renewal reminder guide walks through the full flow including how to verify the trigger fires at the right interval. For course access after purchase, the course access after WooCommerce purchase guide covers the specific trigger and action combination to test.

When testing WooCommerce automations, also verify:

• The trigger fires on “Order Completed” not just “Order Created” if your workflow depends on payment confirmation
• The coupon or access action resolves for the correct user, not a generic test account
• Any external sync (CRM tag, email list subscription) shows up in the destination platform within 60 seconds of the order completing

What Happens When an Automation Fails After Going Live?

Krom Automation logs every failed execution with a full per-step trace. The analytics dashboard shows a failed execution count alongside total executions, so a spike in failures is visible within the same session you are using to review other site metrics. You do not need to dig into log files.

Failed executions trigger an automatic retry with configurable backoff. If the failure was a transient API timeout, the retry usually resolves it. If the failure is persistent (wrong API key, deleted user, a downstream service returning an error), the step-level log shows the exact error message so you know what to fix rather than guessing.

The one honest constraint worth naming: delays depend on WordPress Cron. On a low-traffic site where no visitor arrives for several hours, WP-Cron fires late, and a delay set to “3 hours” may execute at hour 4 or 5.

If precise timing matters for your workflows, configure a real server cron job to trigger WP-Cron on a fixed interval, typically every 5 minutes. This is a WordPress platform constraint, not specific to Krom Automation, but it is relevant to any delayed action you are testing.

A failed execution with a clear log entry is a solved problem. A failed execution with no log is a production incident.

Comparing Testing Capabilities Across Automation Tools

What You Need to Test	Krom Automation (Free)	Krom Automation (Pro)	Uncanny Automator
Dry-run simulator with no side effects	Included	Included	Not available
Per-step execution logs	Included	Included	Available (paid tiers)
Run-once per entity enforcement	Included	Included	Available
Analytics dashboard with failure count	Included	Included	Limited on lower plans
Workflow import/export for staging-to-live transfer	JSON export included	JSON export included	Not available
Automatic retry on failure	Included	Included	Not available in standard tier

Uncanny Automator automation plans start at $199 per year for one site as of September 2026. Krom Automation Pro starts at $69 per year at current launch pricing. Both include per-step logging in their paid tiers, but only Krom Automation includes a true dry-run simulator at any tier.

Which Testing Method Applies to Which Situation

Situation	Best Testing Approach	Time Required
New workflow, never fired before	Simulator first, then one real test execution with a dummy contact	15 to 20 minutes
Existing workflow after changing a merge tag or condition	Simulator only, verify the changed node’s output	5 minutes
WooCommerce order workflow	WooCommerce test mode + real execution + log review	20 to 30 minutes
External integration (Mailchimp, FluentCRM, Slack)	Real execution against a test contact in the destination platform	10 to 15 minutes
Delayed workflow (hours or days)	Set delay to 1 minute temporarily, run real test, restore delay	5 minutes plus wait
Conditional branch workflow	Simulator run twice: once per branch path	10 minutes

Moving a Tested Workflow from Staging to Production

Krom Automation workflows export as portable JSON. Build and test on a staging site, export the workflow file, import it on the production site, and the full canvas, all nodes, conditions, delays, and action configurations, transfers exactly. You do not rebuild from scratch.

What does NOT transfer automatically and must be reconfigured on the production site:

• API credentials: keys for Mailchimp, FluentCRM, Slack, or any other integration are stored per-site and are not included in the exported JSON
• Run-once history: any users or orders that triggered the workflow on staging will not be flagged as “already run” on production, which is correct behaviour but worth knowing
• Failure notification email: confirm the address is set on the production site, not inherited from staging

The workflow import and export feature is available in the free plugin. There is no Pro requirement for transferring workflows between environments.

Also from wpRigel

Pollify is a Gutenberg-native poll, survey, and quiz plugin for WordPress. Polls are built directly inside the block editor as real blocks, so there are no shortcodes to paste and no separate configuration panel to navigate. It is a useful companion if your workflows include collecting audience feedback on a post-submission or post-purchase page.

Commandify is a command palette for the WordPress admin. Press Cmd or Ctrl plus K from anywhere in the dashboard to jump to any page, search posts, manage users, or run admin actions without touching the menu. It is the only WordPress command palette with real WooCommerce order, product, and customer commands built in, which makes it genuinely useful on busy store sites where you are switching between admin tasks constantly.

The Verdict: Who Should Test This Way, and Who Might Not Need To

If your automation touches user-facing output, which covers welcome emails, access grants, coupon codes, CRM tags, and anything a customer sees or experiences, then a simulator pass and a log review before activation is not optional. The cost of one wrong execution (a coupon emailed to 3,000 users who were never meant to receive it, for example) is orders of magnitude higher than 20 minutes of pre-launch testing.

If your automation is internal and reversible, say, a Slack notification when a new post publishes, a failed or duplicate execution is annoying but recoverable. You can afford to activate and monitor rather than simulate first. But you should still check the logs after the first real execution.

Our recommendation: run every new workflow through the simulator before activation, review the step-level logs after the first real execution, and set a failure notification email so you are not discovering problems through customer complaints. The free plugin includes all three of those capabilities. Download the free plugin from the WordPress.org plugin directory and run your first simulator test before you activate anything.

See Krom Automation pricing and compare all plans, starting at $69 per year at current launch pricing, with a 14-day money-back guarantee on every paid plan.

Frequently Asked Questions

Does the Krom Automation simulator work with WooCommerce triggers?

Yes. The simulator accepts sample data for any trigger including WooCommerce Order Created and Order Completed. You can test the full workflow path, including merge tags that pull order total, customer name, or product names, without placing a real order.

Can I test a workflow with a delay node without waiting hours for it to fire?

Yes. The standard approach is to set the delay to 1 minute temporarily, run a real test execution, confirm the log entry shows the correct scheduled timestamp, then restore the intended delay before activating the workflow.

What happens if an automation fires twice for the same user?

If run-once enforcement is enabled, Krom Automation blocks the second execution automatically and logs the prevention. If run-once is off, the workflow fires as many times as the trigger condition is met, which is the correct behaviour for notification workflows but wrong for onboarding sequences. Check the run-once setting for every new workflow before activation.

Do I need Pro to use the workflow simulator?

No. The simulator is included in the free plugin with no plan restriction. Pro adds features like AI workflow generation, the visual email builder, a schedule trigger, and the incoming webhook receiver, but testing via the simulator is available to all users.

How do I test a form automation, for example a Gravity Forms or WPForms workflow, without submitting real data?

Use the simulator with sample form submission data to validate the workflow path. For a real execution test, most form plugins include a preview or test submission mode that generates a real entry without requiring a public-facing form. The Gravity Forms integration documentation and the WPForms integration documentation both cover the exact trigger setup, which affects how sample data should be structured for a simulator run.

What should I check in the logs after the first real execution on a production site?

Confirm four things: the trigger fired for the correct contact and not an unintended user, every merge tag resolved to the correct value, any external integration returned a success response (not a 4xx or 5xx error), and any delay node logged the correct scheduled fire time. If all four pass, the workflow is behaving as designed.

You can receive webhooks in WordPress without Zapier using Krom Automation Pro‘s incoming webhook receiver. You get a unique secret URL per workflow, HMAC-SHA256 signature verification, and a field mapping system that pipes any payload value into a WordPress action.

The incoming webhook receiver is a Pro feature, so you need a paid plan. Free plans start at $69 a year or $199 as a one-time lifetime payment.

Most guides on this topic focus on sending data out of WordPress to Zapier or Make. That is the wrong direction if your problem is a third-party service pushing data to your site. Stripe needs to tell your site when a payment clears.

GitHub needs to tell your site when a pull request merges. Those services send POST requests to a URL you control, and your site needs to be listening at that URL, verifying the request is genuine, and acting on the data.

This guide covers exactly that: how to set up a secure inbound webhook endpoint in WordPress, how to map payload fields to merge tags, and how to wire the whole thing to real WordPress actions without a third-party automation service sitting in the middle. Browse the full feature list to see everything Krom Automation covers beyond webhooks.

What Is an Incoming Webhook and Why Does WordPress Struggle With It?

An incoming webhook is a POST request sent by an external service to a URL your application exposes. The external service initiates the call.

Your application receives it, parses the payload, verifies the signature, and acts on the data. This is the opposite of polling, where your app repeatedly asks an external service whether anything changed.

WordPress does not expose any built-in endpoint for this. Out of the box, if Stripe fires a payment_intent.succeeded event, there is nowhere on a WordPress site for that request to land.

You can build a custom REST endpoint in PHP, but that means writing and maintaining a request handler, signature verification logic, a retry queue, and logging. That is a meaningful amount of code for what is conceptually a simple operation.

The other common answer is Zapier: receive the webhook on Zapier’s servers, then have Zapier call a WordPress action via a plugin. That works, but it adds a third-party dependency, a per-task cost, and a data routing path that takes your webhook payload outside your server before it ever touches your site. For payment data or PII, that routing matters.

What the Krom Automation Incoming Webhook Receiver Actually Does

The incoming webhook receiver in Krom Automation Pro gives every workflow its own unique URL under your domain. That URL is a WordPress REST API endpoint registered under the krom-automation/v1 namespace. When an external service sends a POST request to it, Krom Automation receives the payload, runs 9 security checks, and fires the workflow if everything passes.

The security layer includes HMAC-SHA256 signature verification. You configure the shared secret inside the workflow settings. When a request arrives, Krom Automation recomputes the HMAC using the raw request body and your secret, then compares it against the signature header the sender included.

If they do not match, the request is rejected before any workflow logic runs. This is the same verification model Stripe, GitHub and Shopify all use on their outbound webhooks.

A webhook endpoint without signature verification is an open door. Any request that knows the URL can trigger your workflow. HMAC verification means only the service holding your shared secret can send valid requests.

Once the request passes verification, the payload fields are available as merge tags inside any action in the workflow. If Stripe sends a payload with a customer.email field, that value is accessible via a merge tag and can be passed into a Create User action, an Update Post Meta action, a Send Email action, or an HTTP Request to another service. The merge tags documentation covers the full syntax for accessing nested payload fields.

How to Set Up Your First Incoming Webhook Workflow

Setup follows four steps. Work through them in this order. Skipping to payload mapping before the URL is generated means you have nothing to give the external service to test against.

1. Create a new workflow on the visual canvas and set the trigger to Incoming Webhook. Krom Automation generates a unique secret URL immediately. Copy it. This is the URL you register in Stripe, GitHub, or whichever service is sending.
2. Configure HMAC verification in the trigger settings. Paste the shared secret your external service provides, or generate a secret here and paste it into the external service. Set the header name Krom Automation should read the signature from (for Stripe this is Stripe-Signature, for GitHub it is X-Hub-Signature-256).
3. Send a test payload from the external service’s dashboard. Most platforms, including Stripe and GitHub, have a “send test event” button in their webhook configuration screen. Krom Automation logs the incoming request in the execution history whether it succeeds or fails, so you can inspect the full payload structure.
4. Map payload fields to actions using merge tags. Once you have seen a real payload in the logs, you know exactly what fields exist and how they are nested. Use those field paths in your action configuration.

The step-by-step workflow builder guide covers the canvas interface in detail if this is your first workflow. The workflow simulator lets you run a dry test with zero side effects before you point a live Stripe account at your endpoint.

Stripe Webhook Example: Create a WordPress User on Payment

Stripe fires a payment_intent.succeeded event when a payment completes. The payload includes the customer’s email address, the amount, the currency, and a metadata object you can populate with anything you like when creating the payment intent on your frontend.

A practical workflow for a digital product site:

• Trigger: Incoming Webhook (Stripe endpoint, HMAC verified against your Stripe signing secret)
• Condition: Check that data.object.status equals succeeded before proceeding
• Action 1: Create User, with email pulled from the merge tag for data.object.receipt_email
• Action 2: Send Email to the new user with their login details, using the visual email builder to design the template
• Action 3: Update Post Meta on a licence post to mark it as active, with the user ID from the Create User step injected as the meta value

The whole workflow runs on your server. The Stripe payload never leaves your hosting environment.

If you have a MemberPress membership or Easy Digital Downloads setup, you would typically handle payment events through those plugins’ own triggers rather than raw Stripe webhooks. But for a custom or headless payment flow, the incoming webhook receiver is the right tool.

GitHub Webhook Example: Trigger a WordPress Action on Pull Request Merge

GitHub fires a pull_request event when a PR is opened, updated, or merged. The payload includes the repository name, the PR title, the author, and an action field that tells you whether this is an open, synchronize, or closed event. When action is closed and pull_request.merged is true, the PR was merged.

A practical workflow for a development team that uses WordPress as an internal dashboard:

• Trigger: Incoming Webhook (GitHub endpoint, HMAC verified against your GitHub webhook secret)
• Condition: Branch on action equals closed AND pull_request.merged equals true
• Action: Create Post with the PR title as the post title, the author and repository as meta fields, and status set to Published in a custom post type you use for deployment tracking

You can extend this with a Slack notification using the Slack integration, so your team gets a message in your deployment channel every time a merge lands. Conditions and branching are covered in the conditions and branching documentation if you need to handle multiple event types from the same endpoint.

The most useful webhook workflows are the boring ones: a payment clears, a user record appears. No manual step, no CSV import, no “did that actually run?” in the execution log.

What Gets Logged and What Happens When a Webhook Fails

Every incoming webhook request creates an execution record. The log shows the full raw payload, which step succeeded, which step failed, and the error message if one was thrown. For debugging a misconfigured payload mapping or a signature mismatch, the execution log is the first place to look, not your server’s error log.

Failed executions trigger an email notification to the address you configure in Krom Automation settings. The retry system uses configurable backoff, so a temporary failure on your side does not silently drop the event. The analytics dashboard shows total executions, success rate, and a trend chart, so a spike in failures across your webhook workflows is visible without digging through individual logs.

One real constraint worth naming: Krom Automation uses Action Scheduler for background execution. On very low-traffic sites where nothing visits for hours at a time, WP-Cron fires late, which means delayed actions in a workflow may not run on schedule. The incoming webhook itself receives and logs the payload immediately when the request arrives.

Delays you add to subsequent actions in the workflow are what depend on cron timing. If you are running a high-volume webhook integration, configure a real server cron to trigger WP-Cron on a fixed interval, typically every minute.

Incoming Webhook vs. HTTP Request Action: What Is the Difference?

Krom Automation has two webhook-related features and they serve opposite directions. Understanding which one you need saves time.

Feature	Direction	When to use it	Plan required
Incoming Webhook Receiver	External service sends data TO your WordPress site	Stripe payment events, GitHub pushes, Shopify order hooks, any third-party push notification	Pro
HTTP Request Action	Your WordPress site sends data TO an external service	Posting form data to a CRM, calling a custom API, triggering a remote build	Free

The HTTP Request action supports GET, POST, PUT, PATCH and DELETE with JSON response parsing and is available in the free plugin. If you want to send form submission data to an external endpoint when someone fills in a Gravity Forms or WPForms form, the HTTP Request action covers that without a Pro plan.

What Does This Cost Compared to Routing Through Zapier?

The cost comparison changes significantly depending on volume. Zapier’s Professional plan runs around $240 a year billed annually for 750 tasks a month, as of September 2026, and it uses per-task billing.

A single webhook that triggers three actions counts as three tasks. At 500 payment webhooks a month with three actions each, that is 1,500 tasks, which pushes you past the 750-task limit on the base plan.

Scenario	Krom Automation Pro (1 site, annual)	Zapier Professional (annual)
500 webhook events/month, 3 actions each	$69/year, no task limit	~$240/year, requires plan upgrade above 750 tasks/month
2,000 webhook events/month, 3 actions each	$69/year, no task limit	Higher tier required, task billing increases cost
Data routing	Stays on your server	Passes through Zapier’s servers
Signature verification	Built in, HMAC-SHA256	Requires manual webhook step configuration
Lifetime option	$199 one payment	Not available

Krom Automation Pro has no per-task billing at any tier. Every plan includes every Pro feature and all 25 integrations. The only variable between plans is the number of sites: 1 site on Basic, 5 sites on Standard, and unlimited sites on Enterprise.

For an agency running webhook integrations across multiple client sites, the Standard plan at $149 a year covers all 5 sites with no additional per-site or per-execution cost. See full pricing details.

Per-task billing turns a high-volume webhook integration into an unpredictable monthly expense. A flat annual plan does not.

What Krom Automation Does Not Cover

Being honest about limits is more useful than overselling. Krom Automation is WordPress-native.

At least one end of every workflow, the trigger or the action, needs to touch your WordPress site. If you need to receive a webhook from Stripe and forward the data to HubSpot with no WordPress involvement at all, a general-purpose automation platform is the better tool for that specific flow.

The incoming webhook receiver does not currently support XML payloads natively. Most modern services send JSON, but some legacy systems, particularly SOAP-based APIs, send XML. If your external service sends XML, you would need a middleware step to convert it before it reaches Krom Automation.

Testing on a local development site requires a publicly accessible URL. Your local localhost:8080 address is not reachable by Stripe or GitHub. Tools like ngrok or Expose can tunnel a public URL to your local server for testing.

Once the workflow is working locally, move it to a staging or production environment before pointing a live Stripe account at it. The workflow simulator handles some of this by letting you run logic dry without a real incoming request, but you still need a public URL for end-to-end testing with the external service.

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 configure. Pro adds NPS voting, CSV and PDF export, IP blocking, and enriched analytics.

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

Frequently Asked Questions

Does receiving webhooks in WordPress require writing custom PHP?

Not with Krom Automation Pro. The incoming webhook receiver creates a REST endpoint automatically when you add the trigger to a workflow.

You configure the shared secret and header name in the workflow settings, and the signature verification runs without any code. Custom PHP is only needed if you build the endpoint from scratch without a plugin.

Can I use one webhook URL to receive multiple event types from Stripe?

Yes. Krom Automation receives the full raw payload regardless of event type. Use a condition node in your workflow to branch on the type field in the Stripe payload.

Point the Yes path at one set of actions for payment_intent.succeeded and the No path at a different set for customer.subscription.deleted. The conditions and branching documentation shows how to set up multi-path logic.

Is the incoming webhook URL permanent, or does it change?

The URL is tied to the workflow and does not change unless you delete and recreate the workflow. You can safely register it in Stripe, GitHub or any external service and leave it there. If you duplicate a workflow, the duplicate gets its own unique URL.

What happens if Stripe retries a webhook my site already processed?

Krom Automation logs every execution. The “run once per entity” enforcement prevents the same trigger event from executing a workflow more than once for the same entity. For webhook payloads, you can also add a condition that checks a post meta or user meta field before allowing the workflow to proceed, so a duplicate Stripe retry does not create a second user or a second licence record.

Can I receive webhooks on the free version of Krom Automation?

The incoming webhook receiver is a Pro feature. The free version includes an HTTP Request action for sending data outbound, 16 triggers for native WordPress events, and 21 actions.

The free vs Pro comparison lists exactly what is available at each tier. The free plugin is available on the WordPress.org plugin directory with no trial period and no run caps.

How do I test a webhook workflow before pointing a live service at it?

Use the workflow simulator for dry runs with zero side effects. For end-to-end testing with the actual external service, you need a publicly accessible URL.

On a local site, tools like ngrok create a temporary tunnel. Most services including Stripe also let you send test events from their dashboard, which is the safest way to verify the signature check is working before you go live.

Krom Automation Pro starts at $69 a year or $199 as a one-time lifetime payment, with a 14-day money-back guarantee on every plan. Compare all three plans to find the right fit for your site count.

WooCommerce Subscriptions does not send renewal reminder emails by default. You need a plugin to build that sequence, and Krom Automation is one concrete way to do it: the free version covers payment failed and renewal event triggers, while the Pro plan adds the schedule trigger and visual email builder you need for a full multi-step dunning sequence. Most sites can cover all four sequences described here for $69 a year.

The four sequences worth automating are: a trial ending reminder sent a few days before the trial converts, a renewal reminder sent before the charge date, a payment failed dunning sequence that retries the message across several days, and a cancellation win-back email sent after a subscription is cancelled. Each one targets a different moment in the subscription lifecycle and each one recovers revenue that would otherwise be lost silently.

This guide covers the setup for all four, explains what the free plugin can and cannot do, and is honest about one real constraint: delay-based timing depends on WP-Cron, which can fire late on low-traffic sites. Browse the full feature list before deciding which plan fits your situation.

Does WooCommerce Subscriptions Send Renewal Reminder Emails by Default?

No. WooCommerce Subscriptions handles the actual renewal charge and sends a receipt after it succeeds, but it does not send a reminder before the renewal date.

It also does not send a multi-step sequence when payment fails. Those gaps are where most subscription revenue quietly disappears.

You have three options to fill those gaps: the official WooCommerce Email Reminders extension, a purpose-built plugin such as the one on WordPress.org, or a workflow automation plugin like Krom Automation. The automation route gives you the most control over timing, branching logic, and what happens after each email, without locking you into a single email template editor.

Which Krom Automation Plan Do You Actually Need?

Sequence	Free plugin	Pro required	Why
Payment failed dunning (same-day email)	Yes	No	Order Created / Order Status triggers fire immediately on failure
Payment failed follow-up on day 3 and day 7	No	Yes	Requires the delay node beyond the free delay units, or the Schedule trigger
Renewal reminder X days before charge	No	Yes	Requires the Schedule trigger or WooCommerce Subscriptions Pro triggers
Trial ending reminder	No	Yes	Requires WooCommerce Subscriptions Pro trigger from the integration
Cancellation win-back email	Yes	No	Subscription Cancelled trigger fires in the free plugin
Branded HTML email template	No	Yes	Visual email builder is a Pro exclusive feature

The short version: the free plugin handles same-day payment failed emails and cancellation win-back. Every timed sequence that fires before an event, or that spreads a dunning sequence across multiple days, needs Pro. The full free versus Pro comparison lists every trigger and action by tier.

A payment failed email sent once, on the day of failure, recovers some revenue. A three-touch sequence sent on day one, day three and day seven recovers significantly more, and the difference between those two outcomes is a single Pro plan.

How to Set Up a Renewal Reminder Email

The WooCommerce Subscriptions integration in Krom Automation exposes subscription-specific triggers that the base WooCommerce triggers do not. The WooCommerce Subscriptions integration documentation covers the full list of available triggers, the merge tags each one exposes, and worked automation examples.

For a renewal reminder, the typical setup is:

1. Open Krom Automation in your WordPress admin and create a new workflow on the canvas.
2. Set the trigger to Subscription Before Renewal and configure the lead time, for example 7 days before the renewal date.
3. Add a Send Email action and use merge tags to pull in the customer’s name, renewal date, renewal amount and a direct link to their account page. The merge tags documentation lists every variable available per trigger.
4. Enable Run Once per Entity in workflow settings to prevent the same subscriber from receiving the email twice if the trigger fires more than once for the same renewal cycle.
5. Use the workflow simulator to dry-run the sequence before activating it. The simulator executes the logic with zero side effects, so no real emails are sent during testing.

If you want a second reminder at 3 days out, duplicate the workflow and change the lead time to 3. Two separate workflows is simpler to manage than one workflow with branching on the same trigger, and execution logs stay cleaner.

How to Build a Payment Failed Dunning Sequence

Payment failed dunning is the sequence most subscription businesses underinvest in. A single email on the day of failure is a starting point, not a strategy. Industry data consistently shows that a three-touch sequence recovers between two and four times the revenue of a single email, because card failures are often temporary: a card was replaced, a limit was briefly hit, a bank flagged the charge as unusual.

Here is the sequence structure we recommend building first:

• Day 0 (immediate): A plain-text email explaining the charge failed, with a direct link to update the payment method. Keep this one short. Urgency without panic.
• Day 3: A follow-up referencing the original failure. Mention that access will be affected if payment is not updated. Include the same payment update link.
• Day 7: A final notice. Be direct. Tell the subscriber what happens next (suspension or cancellation) and give them a clear path back. A discount coupon here is optional but effective.

In Krom Automation, the trigger for day 0 is Order Status Changed filtered to a failed payment status. Days 3 and 7 use the delay and scheduling node to hold the workflow and release the next email at the right time. The conditions and branching documentation shows how to add a Yes/No check after each delay: if the customer has already updated their payment method, skip the next email rather than sending a dunning message to someone who already fixed the problem.

Sending a day-seven dunning email to a subscriber who paid on day two is not a small mistake. It is the kind of mistake that gets a cancellation instead of a renewal. The branching check costs 30 seconds to add and prevents it entirely.

How to Set Up a Trial Ending Reminder

A trial ending reminder is the highest-leverage email in any subscription business. A subscriber who is surprised by a charge after a trial often disputes it or cancels immediately. A subscriber who saw the email three days before the trial ended, understood what they were about to be charged, and had a chance to review their account, is far more likely to stay.

The setup in Krom Automation follows the same pattern as the renewal reminder: the trigger is Subscription Trial Ending from the WooCommerce Subscriptions integration, the lead time is typically 3 days, and the email uses merge tags to show the exact amount, the trial end date, and a link to manage the subscription. A second email on the final day of the trial is optional but worth testing: open rates on “your trial ends today” emails are consistently higher than on “your trial ends in 3 days” emails.

The visual email builder in Pro lets you design these emails with a block-based editor powered by Gutenberg, so the trial reminder can include a summary of what the subscriber used during the trial, a link to the pricing page, and a branded footer, all without writing a single line of HTML.

How to Build a Cancellation Win-Back Email

A cancellation win-back email is the one sequence most WooCommerce stores skip entirely, which is why it tends to work. When a subscriber cancels, the default response from WooCommerce is silence. A single email sent 24 to 48 hours after cancellation, acknowledging the cancellation and offering a concrete reason to return, such as a discount, a feature they may not have tried, or a simpler plan, recovers a measurable percentage of churned subscribers.

In Krom Automation, the trigger is Subscription Cancelled from the WooCommerce Subscriptions integration. Add a delay of 24 hours before the email action so the message does not feel like a panic response. Use the Create Coupon action before the email action to generate a unique coupon code per subscriber, inject the code into the email body via a merge tag, and set the coupon to expire in 7 days to create urgency without a permanent discount.

• Trigger: Subscription Cancelled
• Delay: 24 hours
• Action 1: Create Coupon (unique per subscriber, 7-day expiry)
• Action 2: Send Email with coupon code merge tag and a resubscribe link
• Run Once per Entity: Enabled, so a subscriber who cancels and resubscribes multiple times only receives one win-back email per cancellation event

What Merge Tags Are Available for Subscription Emails?

Merge tags are the mechanism for injecting live subscription data into email subject lines and bodies. Without them, every email is generic. With them, the email shows the subscriber’s name, the exact renewal amount, the next billing date, the subscription product name, and a direct account link, all pulled from the event data at the moment the workflow fires.

The full list of merge tags available per trigger is documented in the merge tags reference. For WooCommerce Subscriptions triggers specifically, the integration documentation lists the subscription-specific variables alongside the standard order and user variables. The most useful ones for renewal emails are the renewal amount, renewal date, subscription product name, and the customer account URL.

Why Are My Subscription Renewal Reminder Emails Not Sending?

There are three common failure modes, and they are worth checking in this order because the first two are far more common than the third.

1. WP-Cron is not firing reliably. Krom Automation uses Action Scheduler for background execution, which itself depends on WP-Cron. On a low-traffic site where no visitor arrives for several hours, WP-Cron does not fire, and delayed actions queue up rather than execute. The fix is a real server cron job that hits wp-cron.php every five minutes. This is a hosting configuration change, not a plugin setting.
2. The workflow is not active. A workflow saved as a draft does not execute. Check the workflow status in the Krom Automation canvas view and confirm the toggle shows active.
3. Your transactional email is going to spam. Krom Automation’s Send Email action uses wp_mail(), which routes through whatever mail configuration your server uses. Without SPF, DKIM and a dedicated sending domain or an SMTP plugin, these emails frequently land in spam. The plugin sends the email correctly; the delivery problem is upstream. Use an SMTP plugin such as WP Mail SMTP alongside Krom Automation.

The execution log in Krom Automation shows the status of every workflow run, including failed steps with error details. If an email action shows as failed, the log tells you why. That is the fastest diagnostic tool available, faster than checking email headers or guessing at configuration issues.

What Does This Cost Compared to Other Options?

Option	Year 1 cost	Year 2 cost	Run limits	Lifetime plan
Krom Automation Pro (1 site)	$69	$69	None	Yes, from $199
Krom Automation Pro (5 sites)	$149	$149	None	Yes, from $399
Uncanny Automator (1 site, as of September 2026)	From $199	From $199	None listed	No
Zapier Professional (as of September 2026)	~$240	~$240	750 tasks/month, overage charges apply	No

The Zapier figure assumes the Professional plan billed annually and 750 tasks per month. A subscription business sending renewal reminders, payment failed emails and win-back emails across a few hundred active subscribers will hit that task limit faster than the billing page suggests.

Krom Automation has no per-execution billing at any tier. See the full pricing breakdown including what each plan covers across multiple sites.

Zapier’s task-based billing sounds reasonable until a Black Friday promotion doubles your subscriber base for two months. Krom Automation runs on your server and costs the same whether you send 500 emails or 50,000.

The One Thing Other Guides Do Not Cover: Deliverability

Every other guide on this topic ends at “turn it on.” None of them address whether the emails actually reach the inbox. Subscription reminder emails are transactional, which means they are expected and therefore unlikely to be marked as spam by recipients, but they still fail at the server level if your WordPress installation is not configured for reliable sending.

Three things to verify before your first sequence goes live:

• SPF and DKIM records must be configured for your sending domain. Your hosting provider or DNS documentation explains how. Without them, many mail servers will silently discard your emails.
• Use an SMTP plugin to route email through a dedicated sending service such as Postmark, SendGrid or Amazon SES. The default PHP mail function on most WordPress hosts has poor deliverability and no bounce handling.
• Check the execution log in Krom Automation after the first few sends. A successful log entry means the plugin dispatched the email correctly. If recipients are not seeing it, the problem is between your server and their inbox, not in the workflow itself.

If you are also sending subscription confirmation emails or syncing subscriber data to an email marketing platform, the Mailchimp integration and FluentCRM integration let you tag and segment subscribers from the same workflow that sends the renewal reminder, so your marketing list stays accurate without a separate sync step.

Also from wpRigel

Pollify is our Gutenberg-native poll and survey 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 useful for subscription businesses that want to collect feedback from churned subscribers or run NPS surveys from existing ones.

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 includes real WooCommerce order, product and customer commands, which makes it genuinely useful on a subscription store where you are opening individual orders and subscriber records throughout the day.

Frequently Asked Questions

Does WooCommerce Subscriptions send any emails automatically?

It sends a receipt after a successful renewal charge and a payment failed notice on the day of failure. It does not send reminders before the renewal date, multi-step dunning sequences, trial ending notices, or cancellation win-back emails. Those require a plugin.

Can I send a reminder only to subscribers on manual renewal, not automatic renewal?

Yes. The WooCommerce Subscriptions integration in Krom Automation exposes separate triggers for manual and automatic renewal events.

Build one workflow for each and apply it only to the relevant trigger. Manual renewal subscribers need more urgency in the email copy because the charge does not happen automatically.

How many days before renewal should I send the reminder?

For annual subscriptions, 14 days and 3 days is a common cadence. For monthly subscriptions, 3 days and 1 day tends to perform better because a 14-day lead time on a monthly charge feels early and is easy to ignore. Test both and check open rates in your email sending tool.

Will the workflow fire again if a subscriber’s payment fails and then succeeds on retry?

The dunning workflow fires on the failed payment trigger. A successful retry fires a separate order status event. Enable the Run Once per Entity setting and add a branching condition after each delay to check whether the order status has changed before sending the next email.

That prevents a subscriber from receiving day-three and day-seven dunning emails after they already fixed the issue. The workflow settings documentation covers the Run Once option in detail.

Do I need WooCommerce Subscriptions itself, or does Krom Automation add subscription functionality?

You need WooCommerce Subscriptions installed and active. Krom Automation reads the events that WooCommerce Subscriptions generates and acts on them. It does not create subscription functionality itself.

Can I log subscription-related workflow executions to a spreadsheet for reporting?

Yes. Add a Google Sheets action to any workflow and it will write a row on each execution.

The Google Sheets integration documentation covers the setup. This is useful for tracking how many dunning emails were sent in a given month and cross-referencing with recovery rates in your subscription platform.

The Verdict

If your WooCommerce subscription store is not sending renewal reminders, trial ending notices or a payment failed sequence, you are losing revenue every month to problems that are entirely fixable. The free version of Krom Automation handles the cancellation win-back sequence today. A Pro plan at $69 a year unlocks the timing and email builder features that make the full four-sequence setup possible.

Start with the free plugin to get the cancellation win-back live and verify that WP-Cron is firing reliably on your host. Then upgrade to Pro for the scheduled renewal reminder and the multi-step dunning sequence.

Download the free plugin from the WordPress.org plugin directory and build the first workflow before the end of the day. Compare plans and pricing when you are ready to add the full sequence.

You can sync WooCommerce customers to FluentCRM in two ways: using FluentCRM’s built-in WooCommerce integration for real-time contact creation at checkout, or using Krom Automation Pro to add tagging workflows, conditional branching, and historical data imports. The native integration is free and covers the basics. Krom Automation Pro is where you build logic around what those customers bought, how much they spent, and what happens next.

This guide covers both paths honestly, including what each one does not do and where things break in practice. If you have been staring at FluentCRM wondering why yesterday’s orders have not appeared as contacts, the troubleshooting section is where to start.

Browse the full Krom Automation feature list to see every WooCommerce trigger and FluentCRM action available before you read on.

Quick Summary

What you want to do	Native FluentCRM (free)	Krom Automation Pro
Create a contact when a customer checks out	Yes	Yes
Add an opt-in checkbox at checkout	Yes	Not required
Tag contacts by product purchased	Basic, via automations	Yes, with conditional branching
Import historical WooCommerce customers	Yes, one-time bulk import tool	Via workflow + HTTP Request action
React to subscription renewals and cancellations	Limited	Yes, via WooCommerce Subscriptions triggers
Branch logic on order total or product category	No	Yes
Send to Slack or Google Sheets on purchase	No	Yes, in the same workflow
Execution logs per step	No	Yes

Does FluentCRM Sync WooCommerce Customers Automatically?

Yes, but only for new customers going forward once the integration is enabled. Inside FluentCRM, go to FluentCRM Settings > Integrations > WooCommerce and toggle the integration on. From that point, every completed order creates or updates a contact record automatically, with no third-party plugin required.

What the native integration does at checkout:

• Creates a FluentCRM contact using the billing email address
• Maps billing first name, last name, phone, and address fields to the contact record
• Assigns the contact to any lists or tags you configure in the integration settings
• Optionally shows an opt-in checkbox so the customer actively consents before being added

The opt-in checkbox question matters for GDPR compliance. If you operate in the EU or sell to EU customers, auto-adding every buyer to your CRM without explicit consent sits in a legal grey area. FluentCRM’s opt-in checkbox is the safest route.

The alternative argument, that a purchase relationship constitutes a legitimate interest for transactional email, applies narrowly and should not be treated as blanket permission for marketing. Consult your own legal counsel rather than treating plugin documentation as compliance advice.

How Do I Import Historical WooCommerce Customers?

FluentCRM includes a one-time bulk import tool under Contacts > Import > WooCommerce. It pulls existing customers from your order history and creates contact records in bulk. You can filter by order status, so you can import only customers with completed orders and skip refunded or cancelled ones.

Run this import once after enabling the native integration. After that, new orders are handled automatically. There is no need to re-run the import unless you want to catch customers who checked out as guests during a period before the integration was active.

Guest checkout is the most common reason historical customers are missing. FluentCRM links contacts by email address. If a guest placed an order before FluentCRM was installed, the import tool will still pick them up as long as they provided an email at checkout and their order status matches your filter.

Why Aren’t My WooCommerce Customers Showing Up in FluentCRM?

This is the question nobody else answers directly. Here are the four real causes, in order of how often we see them:

1. The integration was not active when the order completed. FluentCRM only syncs orders that complete after the integration is switched on. Orders that completed before that date need the bulk import described above.
2. The order status was not “Completed”. The native integration triggers on order completion by default. An order stuck in “Processing” does not create a contact until it reaches the status you have configured.
3. A plugin conflict is blocking the WooCommerce hook. Some payment gateways and fulfilment plugins fire their own hooks in a sequence that can interrupt FluentCRM’s listener. Deactivate other plugins in a staging environment to isolate the conflict.
4. The contact already exists under a different email. If the customer used a different email for a previous order, FluentCRM treats it as a new contact rather than merging. Check by searching the billing email directly in the Contacts view.

A sync that looks broken is usually a timing problem, not a data problem. Check the order status and the date the integration went live before digging into hooks.

How Do I Tag WooCommerce Customers by Product Purchased?

This is where the native integration starts to show its limits and where Krom Automation Pro earns its place. FluentCRM’s native WooCommerce integration lets you assign a single set of global tags to every buyer. If you want different tags for different products, you need FluentCRM’s own automation builder or a workflow plugin.

With Krom Automation Pro, the setup looks like this:

1. Open the visual workflow builder and add an Order Completed trigger from WooCommerce.
2. Add a Condition node and set the condition to check which product ID appears in the order.
3. On the Yes branch, add the FluentCRM action to add a specific tag to the contact.
4. On the No branch, add a second condition to check for a different product, or let the workflow end.

You can stack as many condition branches as you need. An agency running 20 WooCommerce stores will build this once, export it as a portable JSON file, and import it to each new site in under a minute. The workflow import and export documentation covers exactly how that works.

The FluentCRM actions available in Krom Automation Pro include adding contacts to lists, adding tags, removing tags, and updating contact fields. The full reference is in the FluentCRM integration documentation.

What About WooCommerce Subscriptions?

WooCommerce Subscriptions renewals, cancellations, and payment failures are not handled by FluentCRM’s native WooCommerce integration in any meaningful depth. This is the gap that pushes people toward WP Fusion or Make.com, neither of which is self-hosted.

Krom Automation Pro includes a dedicated WooCommerce Subscriptions integration with triggers for renewal payments, cancellations, subscription pauses, and trial expirations. You connect those triggers directly to FluentCRM actions in the same workflow. No external service, no webhook middleman, no per-task billing.

A practical example: when a subscription is cancelled, a workflow removes the “Active Subscriber” tag in FluentCRM, revokes course access in LearnDash (if applicable), and sends a win-back email 3 days later using a delay node. All three steps run from a single workflow, self-hosted on your own server, with full per-step execution logs.

Subscription lifecycle events, renewal, cancellation, trial expiry, are where most native CRM integrations quietly give up. That is exactly where a workflow layer earns its cost.

Building a Full Purchase-to-CRM Workflow in Krom Automation

A complete post-purchase FluentCRM workflow in Krom Automation Pro looks like this, ordered by what has the most impact:

1. Trigger: Order Completed (WooCommerce). Fires once per order, enforced by the run-once setting so a customer who places two orders in quick succession does not create duplicate executions.
2. Action: Add or Update Contact (FluentCRM). Creates the contact if they do not exist, or updates the record if they do. Merge tags pull the billing name, email, phone, and address directly from the order.
3. Action: Add to List (FluentCRM). Adds the contact to your post-purchase nurture list.
4. Condition: Check product ID. Branches the workflow based on what was purchased.
5. Action: Add Tag (FluentCRM). Applies a product-specific tag on the matching branch.
6. Delay: 3 days. Waits before the next action.
7. Action: Send Email. Delivers a follow-up email. If you are using the Pro visual email builder, this is a fully branded block-based email, not a plain-text message.

The merge tags documentation shows every dynamic variable available inside action fields, including order total, product names, customer first name, and billing city. Those variables work in email subject lines, email bodies, and any HTTP Request payloads you add later.

You can also add a Google Sheets logging step in the same workflow if you want a spreadsheet record of every purchase alongside your CRM data. The guide to sending WooCommerce orders to Google Sheets shows that setup end to end.

Does Krom Automation Replace FluentCRM’s Native Integration?

No, and we would not recommend treating it that way. The native FluentCRM WooCommerce integration is fast, lightweight, and handles the checkout-to-contact creation step with no overhead. Keep it active.

Krom Automation Pro sits on top of the native integration and handles the logic layer: conditional tagging, subscription events, multi-step sequences, and connections to other tools in the same workflow. The two work alongside each other rather than competing.

If your only requirement is creating a contact in FluentCRM when someone buys, enable the native integration and stop there. If you need product-specific tags, subscription lifecycle handling, or purchase events that also update a Google Sheet, notify a Slack channel, or grant course access, that is where Krom Automation Pro adds value.

Scenario	Right tool	Time to set up
Create FluentCRM contact at checkout	Native FluentCRM integration	Under 5 minutes
Import existing customer history	Native FluentCRM bulk import	Under 10 minutes
Tag contacts by product purchased	Krom Automation Pro	15 to 30 minutes
Handle subscription renewals and cancellations	Krom Automation Pro	20 to 40 minutes
Multi-step post-purchase sequence	Krom Automation Pro	30 to 60 minutes
Cross-tool workflow (CRM + Slack + Sheets)	Krom Automation Pro	45 to 90 minutes

A Honest Look at the Limits

Krom Automation Pro runs workflows via Action Scheduler in the background, so nothing executes during page loads and it will not slow down checkout. However, delays in workflows depend on WordPress Cron.

On very low-traffic sites where no page is visited for several hours, WP-Cron fires late. If a 3-day delay needs to be precise, configure a real server cron job rather than relying on WP-Cron alone.

AI actions in Krom Automation require you to supply your own API key. wpRigel never charges per AI call and never marks up tokens.

You pay your AI provider directly at standard rates. That is a deliberate choice that keeps costs predictable at scale, but it does mean one extra setup step.

If you want to test a workflow before it touches live customer data, the workflow simulator runs a dry-run with zero side effects. Use it before enabling any new workflow on a production store.

Every workflow that runs on live customer data should pass a simulator test first. A misfired tag on 3,000 contacts is not a quick fix.

What Krom Automation Pro Costs

The free version of Krom Automation is available on the WordPress.org plugin directory and includes the WooCommerce Order Created and Order Completed triggers, plus 21 built-in actions. FluentCRM-specific actions are a Pro feature.

Pro plans start at $69 a year for a single site, or $199 for a lifetime licence. Agency plans covering 5 sites cost $149 a year or $399 lifetime.

The comparison against the tools ranking above this article is worth spelling out: at the time of writing, Uncanny Automator’s automation plans start at $199 a year for one site. Krom Automation Pro covers the same site for $69 a year, includes every Pro feature and all 25 integrations on every plan, and carries no per-task billing at any tier.

Every Pro plan includes a 14-day money-back guarantee. See the full pricing breakdown before deciding which plan fits your site count.

Also from wpRigel

Pollify is wpRigel’s Gutenberg-native poll, survey and quiz plugin. Polls are built directly inside the block editor as real blocks, with no shortcodes to paste and no separate interface to learn. It is the right tool when you want reader feedback that lives inside the content rather than embedded from an external service.

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

Frequently Asked Questions

Do I need FluentCRM Pro to sync WooCommerce customers?

No. The native WooCommerce integration that creates contacts at checkout is included in the free version of FluentCRM. FluentCRM Pro adds advanced automation sequences, email series, and reporting, but the basic sync works without it.

Can I sync WooCommerce customers to FluentCRM without any third-party plugin?

Yes, for new customers going forward. Enable the native WooCommerce integration inside FluentCRM Settings, and every completed order creates a contact automatically. For conditional tagging, subscription events, and multi-step workflows, a plugin like Krom Automation Pro adds the logic layer that the native integration does not include.

Does Krom Automation Pro require a Krom Automation free plugin as well?

Yes. Krom Automation Pro is an add-on that requires the free plugin installed and active alongside it. The Pro installation guide walks through both steps.

Will the FluentCRM sync break during high-traffic events like Black Friday?

The native FluentCRM integration runs synchronously at checkout. Krom Automation runs workflows via Action Scheduler in the background, so the checkout process itself is not affected. The article on whether Black Friday traffic breaks WordPress automations covers this in more detail, including what to check on shared hosting before a sale event.

How do I tag FluentCRM contacts differently based on what product they bought?

Use a Condition node in Krom Automation Pro after the Order Completed trigger. Set the condition to check the product ID in the order, then apply a different FluentCRM tag on each branch. The conditions and branching documentation shows the exact node configuration.

Can I also tag Black Friday customers separately in FluentCRM?

Yes. Add a second condition to your purchase workflow that checks the order date or a specific coupon code, then applies a Black Friday tag on the matching branch. The guide to tagging Black Friday customers in FluentCRM covers this exact use case with step-by-step instructions.

Our Verdict

Enable FluentCRM’s native WooCommerce integration today. It takes under 5 minutes, it is free, and it handles the majority of what most stores need. Run the bulk import once to bring in historical customers, configure the opt-in checkbox if you have EU customers, and you are done with the basics.

Add Krom Automation Pro when your tagging logic becomes more complex than “every buyer gets the same tag”, when you are selling subscriptions, or when you want purchase events to flow into other tools in the same workflow. At $69 a year for a single site, it costs less than two hours of developer time and pays for itself the first time it prevents a manually missed tag from breaking a post-purchase sequence.

If you are running client sites, the 5-site plan at $149 a year is the one to consider. Build the workflow template once, export it, and import it across every client store. Download the free plugin from the WordPress.org plugin directory to start, and upgrade when the conditional logic is ready.

Compare all Krom Automation Pro plans and pick the right site count.