Appearance
WhatsApp DirectStart a Project
Centralized WordPress Automation
v2.0.1 Beta 2Scheduled + Event-DrivenProvider-Based Architecture

One automation system for the workflows your site actually runs.

Build scheduled and event-driven WordPress workflows around posts, users, custom content types, JetAppointments, WooCommerce and site data—then run them through a real execution engine with conditions, queues, retries, logs, health monitoring and portable definitions.

WordPress 6.2+PHP 7.4+Queue or direct processingWP-CLI system cron runner
Automation Builder
Adaptive wizardDraft preview

Step 1: Setup

Choose the object, how the workflow starts and how scheduled work should run.

Appointments
Upcoming appointment reminder
Appointments
JetAppointments · appointment
ScheduledRun from WordPress Cron, System Cron or Action Scheduler.
Triggered by an eventRun when an event occurs for the selected object.
BackendSystem / Server Cron
Workflow timingServer managed
RunnerWP-CLI command

Step 2: Conditions

Run only when the right object, state and timing rules are true.

Optional
Match ALL of the following groups
Grouped ALL / ANY logic
Group 1Match ALL conditions in this group
Appointment Status
is
pending
×
Appointment Start
is within
2 hours
×
Automation Has Never Run for Object
is
true
×

Step 3: Actions

Actions execute sequentially in the order shown.

4 actions
1
Send Branded EmailClient reminder using automation email branding and dynamic tokens
communication
2
Create Nelx NotificationLocal notification provider when Nelx Notification System is available
communication
3
Update Appointment FieldWrite reminder state back to the appointment context
data
4
Write Log EntryRecord the workflow outcome for operations and diagnostics
automation

Step 4: Execution & Review

Choose runtime behavior, then save as Draft, Active or Paused.

Ready to review
ProcessingQueue
PriorityNormal
Attempts3
Batch size20
Appointments→System Cron→3 conditions→4 sequential actions→Draft
Interactive: click through the builder steps and switch between scheduled and event-driven setup.
Event-driven workflowsRespond to real WordPress events
Three scheduling backendsWP-Cron, server cron & Action Scheduler
Queue + execution engineRetries, workers, recovery & guards
Portable definitionsImport, export, revisions & migration
Provider-based automation catalogue

Automate the objects already inside WordPress.

Beta 2 discovers the providers and resources available on the site, so the same builder can adapt to different data models instead of hardcoding one site's post types, CCT slugs or local IDs.

Posts & CPTs

Creation, updates, publishing, status, meta, terms, authors and featured images.

Users

Registration, profile changes, roles, login/logout, password resets, capabilities and meta.

Taxonomies

Term creation, changes, hierarchy, meta and object counts.

JetEngine CCT

Create, update and delete CCT items with field-aware conditions and changes.

JetAppointments

Status, payments, provider/service changes, reschedules, slots and appointment fields.

WooCommerce Orders

Order lifecycle, payment, totals, products, coupons, customer context and order actions.

WooCommerce Customers

Customer creation, updates, order counts, spend, fields and meta.

Site Options

React to option changes and update site-level values where appropriate.

Triggers · Conditions · Actions

Build logic that goes beyond “run this every day.”

The runtime understands object fields, trigger context, execution history and date-aware rules, then sequences data changes, communications and automation-control actions in order.

Rich event triggers

Listen for changes that matter instead of polling everything.

Post PublishedUser RegisteredCCT Field ChangedAppointment RescheduledPayment CompletedRole Changed

Grouped conditions

Combine ALL / ANY logic inside groups and across groups, with provider-aware resources and dynamic values.

Fields & MetaRequest ContextTerms & RelationshipsExecution CountAlready Run?Pending Job?

Time-based conditions

Build reminder, expiry and status workflows around date fields instead of custom cron PHP.

Compare to TodayX Days Before / AfterCompare Two DatesSequence RemindersOlder / Newer ThanStatus Checks

Communication actions

Send branded emails, webhooks and local Nelx notifications from the same workflow.

Branded EmailWebhookNelx NotificationWoo Order Email

Data mutation

Update the current object or move data across supported fields and resources.

Set / ClearAppend / PrependIncrement / DecrementCopy / CalculateAdjust DateTerms / Status / Meta

Automation control

Control the workflow itself when a business process needs more than one straight-line action.

Delay / WaitRun Another AutomationSet / Clear StateStop SuccessfullyStop With FailureWrite Log
Scheduling

Choose who owns the clock.

Use native WordPress scheduling when it fits, Action Scheduler when available, or move timing ownership to the server with a generated WP-CLI command.

Flexible schedule types

Recurring intervals, daily, weekly, monthly, multiple times daily, one-time schedules and five-field cron expressions.

WordPress timezone-aware

Internal schedules are calculated against the WordPress/site timezone rather than assuming UTC for business-clock rules.

Server cron stays server-owned

System Cron automations store no WordPress-side execution schedule; copy the generated command into crontab and define timing there.

WordPress CronInternal scheduler
System / Server CronServer owns timing
Action SchedulerWhen available
Recurring interval
Daily at a time
Weekly on selected days
Monthly / last day
Multiple times daily
One-time execution
Cron expression (advanced)
wp nelx-automation run --automation='automation-uuid' --path='/path/to/wordpress'
Runtime HealthHealthy
Queue depth12
Workers2
Success98.7%
Incidents0
AutomationStatusTryLast event
Appointment ReminderCompleted1 / 32 sec ago
Quote ExpiryQueued0 / 3waiting
Order Follow-upCompleted1 / 318 sec ago
Ticket ReminderRunning1 / 3now
Execution & observability

Automation you can operate—not just hope is running.

Beta 2 carries execution state through runs, jobs and individual action attempts, with recovery, metrics and structured logging around the worker system.

Queue or direct processing

Choose per automation, set priorities, batch sizes and maximum attempts, and recheck conditions immediately before execution.

Runtime guards & recovery

Concurrent-worker limits, worker leases, memory guard, database failure thresholds, circuit-breaker cooldowns and recovery services protect the runtime.

Inspect what happened

Run History, trigger snapshots, job status, action results, relevant logs, queue inspection, runtime health, metrics and incidents are built into the admin experience.

Communication layer

Branded email belongs inside the automation system.

Beta 2 includes its own generic email-branding compiler and sender, so workflow emails can share one visual system without depending on JetFormBuilder templates.

Email branding

Logo/media controls, layout styles, typography, buttons, message boxes, footer content and social icons feed the same compiler used by email actions and previews.

Dynamic workflow tokens

Resolve values from the current object, related provider data and automation context rather than hardcoded site-specific placeholders.

Local Nelx notifications

When Nelx Notification System is available, automations can create notifications through the local integration instead of a same-site REST call.

Example workflow

Quote expiry sequence

1
Find matching quote recordsTime-based conditions evaluate the expiry field
CCT
2
Send branded reminderDynamic quote/client data inserted into the message
Email
3
Create in-app notificationOptional local Nelx Notification action
Notify
4
Update workflow statePrevent duplicate reminder behavior using execution policy/state
State
Portability & migration

Move workflows without carrying one site's hardcoded IDs with them.

Automation definitions are designed to be portable: providers and resources can be analyzed, mapped and reviewed before a Draft is created on the destination site.

Import / Export JSON

Export portable definitions and dependency requirements without shipping runtime history, worker data, local paths or secret values.

  • Provider compatibility analysis
  • Resource mapping review
  • Draft-first import safety

Automation Revisions

Saved automation versions can be browsed, compared and restored without destroying the existing history.

  • Revision history
  • Definition comparison
  • Restore earlier workflow state

Legacy Workflow Migration

Beta 2 includes adapters that detect supported Nelx legacy workflows and propose new Automation Drafts without modifying the source workflow.

  • Nelx Notification Cron
  • Nelx Support Tickets automation
  • Nelx Quote / Invoice automation
  • Nelx JetAppointments automation
Development status

A real beta—not a finished public release.

Nelx Automation System is actively being built and tested. The page is live now so the direction and capability of the product are visible while the final release work continues.

BETA · IN DEVELOPMENTNelx Automation System
2.0.1

Current package: Beta 2. Public release timing, final pricing tiers and licensing details are not yet announced.

What beta-2 already demonstrates

  • A provider-driven architecture that adapts to posts, users, CCTs, appointments, WooCommerce and site data.
  • Scheduled and event-driven automations built through the same guided workflow.
  • Grouped conditions, dynamic values, sequential actions and time-aware workflow logic.
  • A production-oriented execution layer with queueing, retries, recovery, logs, metrics and runtime health.
  • Portability, revision history and safe migration tooling for supported legacy Nelx workflows.
FAQs

Before the public release.

Is Nelx Automation System available as a finished product now?
No. The current product package is v2.0.1 Beta 2 and development is still active. This page describes capabilities already represented in that beta, not a claim that the final public release is complete.
Can it run both scheduled and event-driven workflows?
Yes. An automation can start from a schedule or a provider event. Scheduled workflows can use WordPress Cron, System/Server Cron, or Action Scheduler when available.
What can it automate in Beta 2?
Built-in providers cover Posts/Custom Post Types, Users, Taxonomies, Site Options, JetEngine CCT, JetAppointments, WooCommerce Orders and WooCommerce Customers. Available triggers, conditions, fields and actions adapt to the selected provider/object.
Does it replace the older Nelx automation plugins?
That is the architectural direction. Beta 2 already contains migration adapters for Nelx Notification Cron, Support Tickets automation, Quote/Invoice automation and JetAppointments automation. Migration creates reviewable Drafts and leaves the source workflow untouched.
Does it depend on Nelx Notification System?
No for core automation. If Nelx Notification System is installed and available, the action catalogue adds a local “Create Nelx Notification” action.
Being built by Nelx Studio

Centralize the workflows that keep WordPress moving.

Nelx Automation System is being built for sites that have outgrown scattered cron snippets and one-off automation plugins.