Apaxon Automation
Available nowFreeWhen this happens, do that.
Triggers and actions across every Apaxon plugin — and outward via webhooks — so the follow-up that always gets forgotten happens without anyone remembering it.
- Free forever
- No per-task pricing
- Runs on your own site
What it does.
Triggers from every plugin
A form submitted, a booking made, an invoice paid, a subscription lapsed. Because they share a foundation, the events are already there to listen for.
Actions with conditions
Tag a contact, assign a task, send an email, call a webhook — with branches, so one workflow handles the variations rather than four near-copies.
Delays and schedules
"Three days after the booking, ask how it went." A workflow that can wait is what turns automation into follow-up.
Webhooks both ways
Call anything with an HTTP endpoint, and accept inbound calls to trigger a workflow from a system that has no plugin.
The pricing difference
No charge per task.
Hosted automation tools charge per run, which makes the useful workflows — the ones that fire on every order — the expensive ones. This runs on your own server, so the only limit is what your hosting will do.
- Every run logged with its outcome, so a silent failure is visible
- Failed steps retry rather than abandoning the workflow
- No external service holding your credentials
Requirements
- Requires
- Apaxon Core, WordPress 6.5+, PHP 8.1+
- Workflows
- Unlimited
- Runs
- Unmetered
- Licence
- GPLv2 or later
Questions
Does it need WP-Cron?
Delayed steps do. A real system cron is recommended and the plugin tells you if WP-Cron is not firing — which is the usual cause of a workflow that never resumes.
What if a step fails?
It retries on a backoff, and the run is marked failed with the error if it exhausts them. Nothing fails silently.
Can it talk to Zapier or Make?
Yes, through webhooks in both directions.
Ready to power your WordPress website the smart way?
Start with Apaxon Core — free, GPL, and with nothing to cancel. Add the plugins you need when you need them.