70 triggers, 37 actions, no per-task fees — from $149/year.
WordPress Workflow Automation Built Into Your CRM — Not Rented From Zapier
Auto Form CRM ships a visual automation engine with 70 triggers, 37 actions, a real job queue, and a true dry-run mode. Build the sequence once, test it against a real contact without sending anything, and watch every run logged and inspectable on your server.
- WordPress-native
- No per-task fees
- No contact caps
- Your server, your data
- Every feature, every tier
WooCommerce Recovery
woo_cart_abandoned
Cart Abandoned
Trigger · fires after 60 min of inactivity
Wait 60 minutes
Resume state persisted to database
Generate WC Coupon
10% off · expires in 48h · single use
Send Email
“You left something behind” + coupon
Order placed within 24h?
If/Else · checks order history
Yes
Add Tag
Recovered
No
Send Email
Stronger offer · 15%
127
Runs
91.3%
Success rate
2m ago
Last run
Most WordPress Stores Rent Their Automation From Three Different Vendors
You know the stack. A WordPress CRM that ships eight triggers and calls it automation. Zapier on top to fill the gaps, billed per task as your volume grows. A SaaS marketing automation platform priced per contact for the sequences your CRM can't run. None of them talk to each other natively. Each one breaks when WooCommerce updates. Each one stores customer data on someone else's server.
By the time you've stitched together a workflow that catches a cart abandonment, waits 60 minutes, generates a coupon, emails it, waits 24 hours, checks if the customer came back, and tags them accordingly — you've touched four tools, three subscriptions, and two customer databases.
Most CRMs treat automation as the thing you graduate to when you pay them more. Auto Form CRM treats it as the engine that should ship with the contact database, because that's where the data already lives.
The workflow engine runs inside your WordPress install, talks to WooCommerce directly, and never sends your customer data to a fourth-party automation tool you have to pay per task forever.
Four Things You Won't Find in Any Other WordPress CRM's Workflow Engine
A real job queue, not a synchronous PHP loop
When a workflow fires, the trigger enqueues a background job through Action Scheduler — the same battle-tested queue WooCommerce itself uses to process millions of jobs across millions of stores. The customer’s checkout completes instantly. The workflow processes in the background. Slow webhooks and email server blips never hold up the request that triggered them. Most WordPress automation tools run everything inline, blocking the originating request for as long as the workflow takes. Auto Form CRM doesn’t.
70 triggers and 37 actions, all in core
Most WordPress CRMs ship 10 to 20 triggers and lock the rest behind add-ons or higher tiers. Auto Form CRM ships 70 triggers across Contact, Deal, Task, Meeting, Email, List, WooCommerce, Checkout Funnel, and Email Capture events. 37 actions covering tags, fields, lists, deals, tasks, meetings, email, SMS, webhooks, and native WooCommerce coupons. Every trigger and every action is available in the Personal tier at $149 a year. No upsells, no add-on plugins, no enterprise tier required.
Race-safe per-contact re-entry control
Three policies per workflow. Allow always — the same contact can enter every time the trigger fires. Once per contact — exactly once, ever, enforced by a database-level unique constraint as an insert lock. Once per N days — a configurable cooldown from 1 to 3,650 days. Most CRM plugins check-then-write, which means high-traffic sites can get duplicate runs they never see coming. Auto Form CRM can’t. The database enforces the gate, not the application logic.
True dry-run test mode
Click Test. Pick a real contact, deal, task, or meeting. Run it. The engine walks the entire workflow against that record — every condition evaluated, every action validated, every step gets a green check or red X with a clear message. Nothing actually happens. No emails send. No tags get added. No webhooks fire. No coupon gets created in WooCommerce. The record stays exactly as you found it. You see what would happen in production, with zero side effects, before you flip the switch.
Every Event on Your WordPress Site Is Ready to Automate
Most WordPress CRMs ship a handful of triggers and stretch the word automation thin. Auto Form CRM ships 70, counted straight from the source. Here's the full surface.
Contact
Created, Updated, Tag Added, Tag Removed, Status Changed, Deleted, Owner Changed, Custom Field Changed, Form Submitted. The Custom Field Changed trigger watches any field you’ve defined.
Deal
Created, Updated, Stage Changed, Won, Lost, Deleted, Value Changed. Tie your sales pipeline to automated owner notifications, task creation, and follow-up sequences without writing a single line of code.
Task
Created, Completed, Overdue, Updated, Status Changed, Assigned, Reopened, Deleted. For operations teams running their work from the CRM instead of a separate project tool.
Meeting
Scheduled, Rescheduled, Cancelled, Completed, No-Show. Tie native meeting scheduler events into reminder sequences and no-show follow-ups.
Opened, Link Clicked, Bounced, Unsubscribed, Sent, plus six campaign-level events. Open and click events drive behavioral segmentation. Bounce and unsubscribe events drive list hygiene.
List
Contact Added, Contact Removed, List Created, Updated, Deleted. The plumbing for cross-workflow list orchestration.
WooCommerce
Order Placed, Status Changed, Completed, Refunded, Customer Created, Cart Abandoned, Cart Recovered, Repeat Purchase, Spending Threshold, Customer Inactive, Customer Score Changed, Lifecycle Stage Changed. Twelve native events firing from the same install — no webhooks to maintain, no API rate limits, no sync delays.
Checkout Funnel
Any Funnel Step Reached, Cart Viewed, Email Captured, Checkout Started, Checkout Validated, Order Placed, Step Abandoned. Drive automation off the exact moment a shopper drops off — not the next-day cron sweep most tools settle for.
Email Capture
Cart Gate Submitted, Checkout Reveal, Exit Intent, Back-in-Stock Request, Post-Purchase Signup, Back-in-Stock Available. Every email capture surface fires its own trigger, so the welcome flow knows which moment caught the customer.
If something happens on your WordPress site, there's a trigger for it. If something doesn't, the Custom Field Changed trigger plus an If/Else condition covers almost any gap.
A Builder That Catches Your Mistakes Before Your Customers Do
Drag a trigger onto the canvas. Drop actions underneath. Connect them. Save. That's the happy path. The interesting part is what happens when you make a mistake.
Live validation, errors that block save, warnings that nudge
Every change is checked instantly. The Issues to Fix panel surfaces two kinds of problems: red errors that block save (orphan nodes, missing trigger config, unconfigured actions, more than one trigger, circular references) and amber warnings that nudge you toward best practice (workflow should have an end node, condition node missing a Yes or No path). You can’t ship a broken workflow by accident. The Save button stays disabled until errors are gone.
Branches that can actually merge
If/Else nodes split your path. Two branches can converge back onto a shared downstream action — the engine uses a visited-set graph traversal, so that downstream node executes exactly once, no matter which branch reaches it first. Most visual builders force you to duplicate the same action on every branch. This one doesn’t.
Three logic nodes that do real work
If/Else Branch checks a field against an operator: equals, not equals, contains, not contains, is empty, is not empty, greater than, less than, has tag, not has tag. Wait/Delay pauses the workflow for minutes, hours, days, or weeks — the resume state is persisted to the database and the schedule lives in WordPress cron, so waits survive server restarts. End Workflow stops a branch cleanly.
Sensible safety limits
Up to 50 actions per workflow at save time. A 200-node-per-execution runtime guard. Recursion depth capped at 5 for any synchronous nesting. A misconfigured workflow can’t take your site down.
Feel How the Builder Works — Right Here
This is a simplified live demo of the drag-and-drop canvas. Drag steps on, connect them, and hit Run Workflow to watch it execute. The real builder adds 70 triggers, 37 actions, live validation, and dry-run testing on top.
Drag onto the canvas
Triggers
Contact Created
When a new contact is added
Form Submitted
When a form is filled out
Deal Moved
When a deal changes stage
Actions
Send Email
Send an email to the contact
Add Tag
Add a tag to the contact
Create Task
Create a follow-up task
Notify Team
Send a Slack/email notification
Timing
Wait 1 Day
Pause for 1 day
Wait 3 Days
Pause for 3 days
Wait 1 Week
Pause for 7 days
Conditions
If Email Opened
Branch if email was opened
Drag steps from the panel
Start by dragging a trigger, then add actions
Test Against a Real Contact. Send Nothing. See Everything.
Most automation tools give you two choices: trust the builder and hope it works, or set up a dummy contact and pray you remember to delete the test tag afterward. Auto Form CRM gives you a third option.
Click Test. Pick a real contact, deal, task, or meeting. Run it. The engine walks the entire workflow against that record — every condition evaluated, every action validated, every step gets a green check or a red X with a clear message about why.
Nothing actually happens. No emails send. No tags get added. No webhooks fire. No coupon gets created in WooCommerce. The record stays exactly as you found it. Test runs are also exempt from the once-per-contact re-entry gate, so a dry-run never uses up a slot.
You see what would happen in production, with zero side effects, before you flip the switch.
Test Run — WooCommerce Recovery
Tested against: Sarah Mitchell
6 of 6 steps validated
Trigger matched — Cart Abandoned
Context resolved for Sarah Mitchell
Wait 60 minutes
Would schedule resume (skipped in test mode)
Generate WC Coupon
Would execute in production (skipped in test mode)
Send Email
Would execute in production (skipped in test mode)
If/Else — order placed within 24h?
Evaluated: No path taken
Send Email — stronger offer
Would execute in production (skipped in test mode)
Zero side effects: no emails sent, no tags added, no webhooks fired, no coupons created. Record unchanged.
Overall status
Succeeded, partially executed, or failed — with the full execution time.
Actions performed count
X of Y, with the exact node-by-node checklist underneath.
Per-action verdict
Green check or red X on each action, with the exact message — “Would execute in production (skipped in test mode)” on the actions that would have fired, real validation errors on the ones that wouldn’t.
Branch path taken
Which side of every If/Else condition the test followed, so you can verify the path matches your intent.
If you ship automation that touches paying customers, this is the difference between launching with confidence and launching with crossed fingers.
The Plumbing Most WordPress CRMs Don't Talk About
Automation looks the same in screenshots. It runs very differently in production. Here's what's under the hood.
A real Action Scheduler job queue
Action Scheduler is the queue WooCommerce uses internally to process millions of background jobs across millions of stores. Auto Form CRM vendors it inside the plugin, registers a trigger handler, and lets it manage retries, concurrency, and persistence. When a customer's order fires a workflow, the request returns immediately. The workflow runs in the background. Older WordPress automation tools run everything inline — a slow webhook or a failing email server holds up the originating request. Auto Form CRM doesn't.
Fresh installs default to queued execution. Existing sites stay on synchronous execution after upgrade to preserve current behavior. A single setting switches between them — both paths are first-class and tested.
Automatic retries with exponential backoff
Webhooks time out. Email servers blip. SMS providers throttle. Auto Form CRM retries the actions that fail because of transient infrastructure issues, on schedules tuned to the failure mode:
Local database actions (Add Tag, Update Field, Change Status) don't retry — they either succeed instantly or fail loudly. Every retry attempt is logged with its count, so you can always see what happened on attempt 1, attempt 2, attempt 3.
Race-safe re-entry via insert-as-gate
The once-per-contact gate uses a database-level unique constraint on workflow_id + contact_id as an insert lock. Even if your site fires the same trigger ten times in the same millisecond, exactly one execution gets through. The other nine hit the constraint and skip cleanly. The database guarantees it, not the application logic.
Loop protection that actually protects
When an action like Add Tag or Change Status runs, it writes through the repository layer directly. It does not re-emit the trigger events other workflows listen to. A workflow that adds a tag won’t kick off a chain of other workflows listening for tag additions. On top of that, the engine enforces a recursion depth limit of 5 for any synchronous nesting within a single request. Infinite loops aren’t a polite request. They’re structurally impossible.
Persisted waits that survive restarts
Schedule a 7-day wait inside a sequence. Restart the server. Deploy new code. Switch hosting providers. The wait still resumes on time, because the resume state lives in your database and the schedule lives in WordPress cron. Server uptime doesn’t dictate workflow continuity.
WP-Cron health monitoring
If your site disables WP-Cron and you’re running queued workflows, the plugin flags the conflict in an admin notice on plugin pages. Silent stalls don’t eat your automation behind your back.
Eight You'll Use Most. Twenty-Nine More When You Need Them.
Send Email
A one-off transactional or marketing email, configured directly on the action. Subject, body, and recipient resolved from the contact. Failed sends auto-retry on a 5m / 30m / 2h schedule.
Send Campaign Email
Send a saved campaign template, inheriting the campaign’s from-name, from-email, and subject overrides. Full suppression checks run automatically — unsubscribed, bounced, and automation-blocked contacts are skipped without you having to remember.
Add Tag / Remove Tag
Tag a contact based on behavior. Writes directly to the contact record without re-triggering other workflows, so you can use tags as flags without worrying about cascading runs.
Update Field
Set or overwrite any standard or custom field on the contact. Pair with a Custom Field Changed trigger on a separate workflow if you actually want a chained effect.
Send Webhook
POST a structured JSON payload to any URL: contact and deal objects, event metadata, plus a custom data map. Custom headers supported with a security blocklist on sensitive ones, 5-second timeout, automatic retries on failure.
Generate WooCommerce Coupon
Creates a real native WC_Coupon — not a fake code in a database table somewhere. Configure discount type, amount, expiry, usage limits, min and max cart, individual-use, free-shipping, product and category restrictions. The code is generated, stored on the contact, ready to drop into a Send Email action.
Send SMS
Twilio-powered. Configure your Twilio credentials in plugin settings once. The action formats numbers to E.164, retries on transient failures, and fails gracefully if a contact has no phone.
Create Task, Create Deal, Schedule Meeting
Operational actions that turn customer behavior into real work assignments. New high-value order? Auto-create a task for your owner. Cart abandoned at $500+? Open a deal in your pipeline. Form submitted? Schedule a meeting.
Plus 29 more, across Contact, Task, Deal, Meeting, Notification, and Activity categories
Every action is documented in the builder with inline help.
I Built This Because Every Other CRM Forced Me Into Zapier
I ran an online store before I built CRM software. Every CRM I tried did the same thing.
The cheap ones shipped eight triggers and called it automation. The moment I needed anything custom — a webhook to a third-party tool, a coupon code generated and emailed, a wait that survived a server restart — I was forced into Zapier or Make. Per-task billing. Customer data passing through a fourth-party server. Rate limits during peak traffic. Sequences breaking the moment my WordPress install hiccupped.
The expensive ones — HubSpot, ActiveCampaign, Klaviyo — had the engine. They also had per-contact pricing that punished me for growing, and they held my customer data on their cloud. Cancel the subscription and lose the automation history I'd built up over years.
The WordPress-native CRMs were closer. But every one I evaluated ran workflows synchronously inline, had no retry on failed actions, no real re-entry control, no dry-run that actually did nothing. Their builders looked nice in marketing screenshots and broke quietly in production.
So I built the engine I always wanted.
70 triggers covering every real event on a WordPress site. A queue that doesn't choke under load. Retries on the actions that genuinely fail. A dry-run that actually does nothing. A history view that tells me what happened on run number 847 instead of "check the logs."
Nothing here is novel engineering. Action Scheduler is what WooCommerce uses. Unique-key insert-as-gate is a 30-year-old database pattern. Exponential backoff is from the 1980s. The novel thing is that none of this was in the WordPress CRMs I evaluated. So I built it.
Ali
Founder of Auto Form CRM
Install Klaviyo-Tier Automations With One Click
You don't need to build automations from scratch. Auto Form CRM ships 16 pre-built workflow templates, ready to clone as drafts you can customize before activating. Nothing goes live automatically — every template is a starting point.
Abandoned Cart Recovery
Re-engage shoppers who left items in cart with configurable wait times, real WooCommerce coupons, and recovery tracking.
Welcome New Customer
First-order onboarding sequence — brand intro, product education, and a thank-you coupon timed for the next purchase window.
Win-Back Inactive Customer
Re-activate customers who haven’t ordered in a configurable window. Progressive incentive escalation if early emails don’t convert.
VIP Customer Notification
Flag accounts that cross your spending threshold so your team can give them human attention — a personal email, a private discount, a phone call.
Repeat Purchase Reward
Automatic loyalty reward when a customer places their second or subsequent order. Real WC coupon, real recovery tracking.
Back in Stock Auto-Notify
Email every waiting customer the moment a tracked product returns to stock. One per customer per product, no spam.
Post-Purchase Follow-Up
Review request, cross-sell suggestion, or care-content sequence after order completion. Timed against actual delivery windows.
High-value order alerts, refund follow-up, spending threshold rewards, cart-recovered thank-yous, checkout funnel recovery, coupon gating, post-capture nurture, and back-in-stock workflows.
Honest note: the current template library is WooCommerce-heavy because that's where most of our store-owner users live. Templates for pure-CRM sales flows are on the roadmap.
Every Run Logged. Every Payload Inspectable.
When something goes wrong with automation, "it worked in testing" doesn't help anyone. The Execution History modal shows you the last 100 runs of any workflow, with the data you need to actually debug.
Execution History — WooCommerce Recovery
127
Runs
91.3%
Success
4
Failed
119
Contacts
- #1284Sarah MitchellSuccess2m ago
- #1283Daniel ReyesSuccess41m ago
- #1282Mia TanakaFailed2h ago
Trigger data
{ "event": "woo_cart_abandoned", "cart_total": 184.50, "contact_id": 8231 }Send Email failed after 3 retries: SMTP connection timed out (attempt 3 of 3)
- #1281Liam O’ConnorPartial5h ago
- #1280Ava LaurentSuccess9h ago
Per-run status
Green check for success, amber bang for partial, red X for failed. Visible at a glance across the full history.
Trigger payload
The exact JSON that fired the workflow — visible inline in the expanded detail, copy-pasteable when you need to ask support a question or reproduce locally.
Error detail
When a run fails, the actual error message surfaces in the detail panel. No more “something went wrong, check the logs.”
Aggregate stats on every workflow card
Runs, success rate, failed count, contacts processed, last run timestamp — visible on every workflow row in the list view, so you spot issues without opening anything.
Manual retention control
Workflow logs aren't auto-purged. They stay until you decide to clean them — purge older than a chosen date from Settings, with a 30-day minimum to avoid accidents.
The Workflow Engine That Actually Talks to Your Store
Twelve WooCommerce triggers, plus seven checkout funnel triggers and six email capture triggers — all firing from live events on the same WordPress install. No webhooks to maintain, no API rate limits, no sync delays.
A customer abandons their cart. The plugin detects it on the next cron sweep (default: 60 minutes of inactivity, configurable) and fires the Cart Abandoned trigger. Your workflow sends a recovery sequence, generates a real WC_Coupon, emails the code, waits 24 hours, checks if they came back, and either tags them as recovered or escalates with a stronger incentive. All in one place. No Zapier zaps. No middleware to maintain.
If you sell on WooCommerce, the full picture is on the WooCommerce CRM page — that's where the funnel analytics, email capture, customer scoring, and lifecycle stages live. Workflows are the engine that ties it all together.
What's Not Here Yet. Because Honesty Converts.
Auto Form CRM tells you what the product doesn't do, instead of letting you discover it on day three. Here's the current honest list of gaps.
AND/OR grouped conditions in one node
Today, multi-condition logic is built by nesting If/Else nodes. It works, but it’s visually heavier than a single grouped condition would be. Grouped AND/OR is the top item on the next development block.
Wait until a specific date or time of day
Current waits are relative — X minutes, hours, days, or weeks. “Send next Tuesday at 9am” requires a workaround today. Time-of-day scheduling is the second item on the next block.
Workflow export and import between sites
You can clone workflows within a site, but you can’t yet move them between sites. On the roadmap.
User-configurable retry schedules
The current backoff timings are fixed in code and tuned to real-world failure modes. User-configurable retries are coming.
Loops, parallel-join, sub-workflows, goal-based exits, A/B split
Advanced flow primitives that some marketing automation platforms ship. Branch convergence already works. Orchestrated parallelism and looping are bigger architectural projects on the longer roadmap.
Pre-built templates for pure-CRM sales flows
Today’s template library is WooCommerce-heavy because that’s where most of our store-owner users live. Templates for non-store sales pipelines — lead nurture, onboarding, renewals — are on the roadmap.
None of these are blockers for the 95% of automation people actually build. But if any of them is critical for your use case, here's the honest list now rather than after you've bought.
How Auto Form CRM's Workflow Engine Stacks Up
| Auto Form CRM | Zapier | FluentCRM | HubSpot / ActiveCampaign | |
|---|---|---|---|---|
| Pricing model | Flat, from $149/yr | Per-task tiers | Per-contact tiers | Per-contact tiers |
| Trigger count | 70 | Thousands via API | ~15 | 100+ |
| Real job queue | Action Scheduler | Cloud queue | Inline / cron | Cloud queue |
| Exponential backoff retries | Limited | |||
| Race-safe re-entry control | Partial | |||
| True dry-run testing | Partial | |||
| WooCommerce triggers | 12 native | Via API | ~6 | Via integration |
| Data on your server | ||||
| Per-task fees | None | $20–800/mo | None | None |
Auto Form CRM vs Zapier and Make
Zapier and Make are excellent at connecting third-party tools. They’re also expensive at scale, charge per task, live outside your site, and mean your customer data passes through a fourth-party server before reaching wherever it’s going. Auto Form CRM workflows run inside your WordPress, with no per-task fees, no contact caps, and no data leaving your install for anything except the actions you explicitly point outward — webhooks, email sends, SMS.
Auto Form CRM vs FluentCRM and Groundhogg
The closest WordPress-native comparables. Both are respected products. Both ship smaller trigger surfaces (typically 10 to 20 triggers vs 70), simpler visual builders, and neither ships an Action Scheduler-backed queue with automatic retries and race-safe re-entry control built in. If you’ve outgrown a simpler WordPress automation tool, this is where the engineering shows.
Auto Form CRM vs HubSpot, ActiveCampaign, Klaviyo
SaaS marketing automation platforms with broader feature sets and per-contact pricing that scales with your list. They’re powerful. They also charge you more every month as your business grows, and your customer data lives on their servers. Auto Form CRM is a flat one-time-per-year price for the engine, hosted on your infrastructure, owned by you.
Honest framing: if you need a 200-person sales team running enterprise attribution, those tools are still the right answer. If you're a founder, a small team, or a single operator who wants real automation without watching the per-contact meter — this is built for you.
Unlimited workflows, unlimited runs, unlimited contacts — for $149 a year.
Built for Operators, Not Marketing Departments
WordPress agencies running workflows for clients
The Agency tier covers 50 sites at $499 a year. Build standardized automation templates once. Deploy them across every client install. Bill for workflow setup as a service line. No per-task fees compounding across client volume.
WooCommerce store owners scaling past $100K
You’ve outgrown the free abandoned-cart plugin. You’re hitting the Klaviyo or Privy subscription wall and dreading your monthly tool bill. You need real cart recovery, real customer scoring workflows, real lifecycle automation — without the per-contact meter.
Service businesses running on follow-up
Roofers, plumbers, electricians, lawyers, consultants — anyone whose business runs on a sequence of follow-up touches. Lead in, task created, follow-up email scheduled, status updated, SMS reminder sent, deal advanced. Every step automated, every step logged, every step inspectable.
Course creators and coaches
Tag students by program. Trigger nurture sequences based on enrollment status. Auto-create tasks for high-value prospects. Schedule meetings off form submissions. Run your business and your community from one WordPress install.
Solo founders and small teams
You don’t have a marketing ops hire. You don’t have time to learn three tools. You need automation that ships with the CRM, runs on the same install, and doesn’t require Zapier glue between every step.
Stores burned by automation that broke checkout
Read-only on your storefront. Append-only DOM. Real native WC_Coupon objects. Queue-based execution that never holds up an order. If a marketing automation tool ever broke your checkout, this is built for you.
The Questions Buyers Actually Ask
Yes. No cap on the number of workflows you can create. No cap on the number of runs per month. Limited only by your database and server capacity, which for any standard WordPress install is far beyond what a small or mid-sized business needs.
No, especially with queued execution enabled. The Action Scheduler job queue runs workflow logic in the background, so the request that triggered the workflow (a form submit, a checkout, an order update) returns instantly. Synchronous execution is also available for sites that prefer it.
Yes. Twelve native WooCommerce triggers, seven checkout funnel triggers, six email capture triggers — all firing from live events on the same WordPress install. No webhooks to maintain, no API sync, no rate limits. Generate Coupon actions create real WC_Coupon objects that work with every checkout extension you already have.
Bigger trigger surface (70 vs roughly 15), real Action Scheduler-backed queue with exponential backoff retries on webhooks/email/SMS, race-safe per-contact re-entry control enforced at the database level, true dry-run test mode that runs the full graph with zero side effects, branch convergence that doesn’t force action duplication, and 12 native WooCommerce triggers including checkout funnel events that most competitors don’t ship.
No. The visual drag-and-drop builder is designed for non-developers. The 16 pre-built templates install as drafts you can customize before publishing. Live validation catches mistakes before save. A developer is only useful if you want to build custom webhook integrations or extend the engine via hooks.
Failed actions on webhooks, email, and SMS auto-retry with exponential backoff (webhooks at 1m/5m/30m, email at 5m/30m/2h, SMS at 5m/30m). After the final retry, the failure is logged in execution history with the attempt count and the exact error message. Local database actions (tags, fields, statuses) don’t retry — they either succeed instantly or fail loudly with a clear error.
Yes. Click Test, pick a real contact, deal, task, or meeting, and the engine walks the entire workflow against that record with zero side effects. No emails send. No tags get added. No webhooks fire. No coupon gets created. You see a node-by-node verdict for every action, which If/Else branch the test followed, and the exact reason for any skipped step.
Configurable per workflow. Allow Always — yes, every trigger fires. Once Per Contact — exactly once, ever, enforced by a database-level unique constraint. Once Per N Days — re-entry after a cooldown you set (1 to 3,650 days). The once-per-contact gate is race-safe, so even high-traffic sites can’t get duplicate runs from simultaneous trigger events.
Yes, via Twilio. Configure your Twilio credentials in plugin settings once. The Send SMS action formats numbers to E.164, retries on transient failures, and fails gracefully if a contact has no phone number. Twilio is the gateway — Auto Form CRM does not bundle SMS sending costs.
Five honest gaps: AND/OR grouped conditions inside one node (nest If/Else nodes today), wait until a specific date or time of day (relative waits only), workflow export/import between sites, user-configurable retry schedules, and advanced flow primitives like loop nodes, parallel-join, sub-workflows, goal-based exits, and A/B split. Branch convergence already works. The first two items are top priority for the next development block.
No, unless you explicitly send it out via webhook or third-party action. The workflow engine runs entirely on your WordPress install, against your database. Send SMS uses Twilio (your account, your credentials). Generate Coupon creates native WC_Coupon objects in your WooCommerce database. Everything else stays on your server.
The Workflow Engine Plugs Into Everything Else
Every other module in Auto Form CRM is wired up as a workflow trigger or action target. Here's how the engine connects to the rest of the platform.
Contact Management
Workflows trigger off every contact event: created, updated, tagged, status changed, custom field changed.
Learn more→WooCommerce CRM
12 native WooCommerce triggers, 7 checkout funnel triggers, 6 email capture triggers driving automation off real store events.
Learn more→Email Campaigns
Send Campaign Email action inherits saved campaign templates, sender identities, and full suppression checks.
Learn more→Deal Pipeline
7 deal triggers cover the full sales cycle for fully automated pipeline progression.
Learn more→Task Management
8 task triggers and 6 task actions for operations teams that run their work directly from the CRM.
Learn more→Meeting Scheduling
5 meeting triggers covering scheduled, rescheduled, cancelled, completed, no-show for reminder sequences.
Learn more→Custom Fields
Custom Field Changed trigger watches any custom field. Update Field action sets any value.
Learn more→Tags
Add Tag and Remove Tag actions write through the repository layer — no cascading triggers, no infinite loops.
Learn more→Integrations
Send Webhook action POSTs structured JSON to any URL. Twilio powers SMS. Mailgun, Postmark, Sendgrid handle email.
Learn more→Stop Paying Per Task. Start Owning Your Automation.
One plugin price. Unlimited workflows. Unlimited contacts. Unlimited runs. The Action Scheduler queue, the exponential backoff retries, the dry-run testing, the execution history, the 16 templates, the 70 triggers, the 37 actions — all included, all yours.
Install in minutes. Cancel anytime — though your workflows will stay either way, because they live in your WordPress database where they always did.
Read the DocsBuilt by Amora Digital (KVK 99536811) in the Netherlands. Made for WordPress. Designed by someone who ran an online store and wished there was a better way.