Build WordPress workflows visually: posts, comments, users, and webhooks on one canvas. JOrchestrator is the workflow builder; the WordPress plugin is the runtime.
WordPress automation usually starts as a mu-plugin or a functions.php hook: save_post sends an email, comment_post pings Slack, a cron event republishes a page. It works until the next developer cannot find the snippet.
A WordPress workflow builder keeps those jobs visible. You drop a WordPress event, map the payload, and attach actions — update post, create page, approve comment, call an API — without deploying PHP for each request.
If the sentence starts with “when this WordPress hook fires…”, it belongs on the canvas:
Install the JOrchestrator WordPress plugin, link the domain, and activate the flow. Event nodes listen for core hooks such as save_post, comment_post, and transition_post_status. Action nodes call back through the same plugin.
Inbound webhooks cover the jobs WordPress cannot see — Stripe, a headless form, a mobile app. Hosted schedules cover the jobs wp-cron is bad at proving: retries, logs, and a timetable that does not depend on traffic.
Do not begin with a 40-node canvas. Ship one job, then clone the pattern.
These are the WordPress nodes behind the recipes. Open a node page when you want the hook or the action — not the tour.
The WordPress plugin executes flows. The workflow builder is the JOrchestrator canvas — triggers, logic, AI, and actions you design once and run on every linked site.
Not for jobs the palette already covers: posts, pages, comments, users, tags, media, webhooks, and HTTP. Keep PHP for true site-specific behaviour the nodes cannot express.
WordPress 5 and 6. The flow must be Active and the site linked in Domain Setup before hooks fire.
Yes. The designer is the same. Joomla-only and WordPress-only nodes sit in their own palette groups; shared nodes (webhook, email, AI, storage) work on both.
Claim a free canvas, link a WordPress site, and move the next hook onto a flow you can see.
Already have an account?