Replace one-off Joomla plugins, helper files, and cron scripts with visual flows. JOrchestrator listens to native Joomla events, then creates articles, notifies people, and talks to the rest of your stack.
Most Joomla sites already automate something: a content plugin that emails the editor, a system plugin that syncs users, a CLI cron that republishes the homepage. That work is real Joomla automation — it just lives in PHP you have to maintain on every upgrade.
Joomla workflow automation is the same jobs on a canvas. A Joomla event starts the flow. Action nodes update the CMS. Logic and AI nodes decide what happens next. You keep Joomla. You stop shipping a new plugin for every request.
If a client asks for “when an article is saved, do X”, that is a flow, not an extension. Typical Joomla automation that teams move onto the canvas:
Install the JOrchestrator plugin, link the domain, and turn on Platform Events. A trigger node listens for a Joomla hook — Content After Save, user login, menu change, or an inbound webhook. Downstream nodes run against that same site.
You can also start from a hosted schedule instead of an event. That is how daily banners, stale-content audits, and overnight publishing jobs work without relying on Joomla’s CLI cron alone.
These three recipes are the shortest path from “we should automate Joomla” to a live flow. Each one links the exact nodes on the canvas.
These are the Joomla nodes behind the recipes above. Open a node page when you want the hook or the action — not the tour.
The Joomla plugin is the runtime. The product is a visual workflow builder: you design flows in the cloud canvas, and the plugin executes them on the linked site. You are not writing another system plugin for each job.
No. Native Joomla Workflow still owns editorial states. Use Trigger Workflow when a flow should hand a completed item into that process. JOrchestrator covers the work around it — events, integrations, AI, and schedules.
Joomla 4, 5, and 6. Platform Events must be enabled in System → JOrchestrator on the linked site before event triggers fire.
Yes. Paid plans include j-orchestrator-proxy tunnels, so the same flow can hit localhost, a private LAN, or production behind a firewall without opening inbound ports.
Open a free canvas, link a Joomla domain — production or localhost — and replace the plugin you were about to write.
Already have an account?