Joomla & WordPressJoomla automation · WordPress workflow builder

Workflow automationfor Joomla and WordPress

Stop shipping plugins. 291+ nodes — webhooks, AI, cron, and LAN tunnels — on one visual canvas.

Check PHP on a Cron

Platforms
Joomla & WordPress
Nodes
291+ in the designer
Reach
Prod · LAN · localhost
Ops
Live execution

291+ nodesthe stack that ships

  • Joomla 4–6
  • WordPress 5–6
  • PHP security
  • Webhooks that bite
  • StripePayPal
  • OpenAIClaudeGemini
  • LAN tunnels
  • Hosted cron
  • AI node setup
  • Multi-domain ops
  • Real-time runs
  • Joomla 4–6
  • WordPress 5–6
  • PHP security
  • Webhooks that bite
  • StripePayPal
  • OpenAIClaudeGemini
  • LAN tunnels
  • Hosted cron
  • AI node setup
  • Multi-domain ops
  • Real-time runs

On a cron

Check the PHP runtime.
Every night, on every site.

Put PHP Security on a JOrchestrator cron. Each run reads the PHP version a linked Joomla or WordPress site is actually running and compares it with the releases that fix known vulnerabilities. Right now that is the 21 October 2026 releases — 8.5.12, 8.4.27, 8.3.36, and 8.2.35 — which fix CVE-2026-109618 and CVE-2026-109619. Leave the cron in place and the next advisory is checked the same way.

  • Reads the PHP version and SAPI the site is running. Nothing else to install.
  • Compares that runtime with the releases that fix known vulnerabilities, and marks PHP 8.1 and older as unsupported.
  • Hands patched, needs-patch, or unsupported to the next step.
  • Leave it on a JOrchestrator cron, then email or Slack only the sites that still need a patch.
Open the PHP Security node

How it works

Blank canvas.
Live workflow.

Three moves. No plugin graveyard. No devops theatre.

Drop the board

Triggers, actions, logic — wire them like a board, not a ticket queue.

Wire the world

Map payloads. Link domains. Tunnel localhost and LAN with j-orchestrator-proxy.

Hit activate

Watch every run light up — logs, retries, analytics — in real time.

jorchestrator.app/flow

Features

Every node.
One canvas.

Webhooks, CMS events, AI, cron, tunnels — the whole arsenal, wired visually.

The product

Wire it once. Ship it everywhere.

Drag triggers, actions, and logic onto a live canvas. 291+ nodes. No code. No plugin graveyard — one flow that runs on every linked site.

Catch every webhook

Stripe, PayPal, Zapier, custom events — SEF-friendly inbound URLs. Paid plans draft schemas from plain English.

Cron that proves it

Hosted timetable or CMS webcron. Logs, retries, charts. Missed jobs are optional — leave them behind.

  • PHP securityOngoing cron check of the PHP runtime on every linked site
  • CMS eventsJoomla + WordPress hooks that fire the canvas
  • AI · Generative VideoLLMs in AI · Veo & Nova Reel in Generative Video
  • Data logicTables, lists, merge, match, sleep
  • Cloud & mediaS3, GCS, Sheets, transcoder pipelines
  • MessagingEmail, Slack, Discord, HTTP, FTP
  • LAN tunnelsLocalhost to production — same flow

MCP tools for AI agents

Your flows,
as tools for any AI agent.

Add an MCP Trigger and a Joomla or WordPress flow becomes a tool that Claude, Cursor, or any other MCP client can discover and call. The agent sends the arguments you define, the flow runs on your own site, and the result goes straight back to the agent.

  • One flow is one tool: give it a name, a description, and typed arguments.
  • It runs on your CMS, so agents can publish articles, look up orders, or update users with the nodes you already use.
  • Set JSON or Set Response becomes the tool result. Failed runs come back as tool errors.
  • One endpoint per site, protected by a bearer token. Only active flows are listed.
Read the MCP Trigger guide

Secure LAN tunnels

Firewall?
We still get in.

Reach Joomla or WordPress on localhost, private LAN, or production behind a firewall with j-orchestrator-proxy — no public port forwarding. CLI for CI, or the built-in console for throughput and status.

LAN tunnel architecture: j-orchestrator-proxy on your network opens an outbound secure connection to JOrchestrator cloud. Cloud schedulers and webhooks send requests through the tunnel to your CMS without public port forwarding.

Your network

LAN / localhost

  • Joomla / WordPresslocalhost · LAN IP · firewall-protected prod
  • j-orchestrator-proxyCLI or console on your machine

No public ports opened

JOrchestrator cloud

Flows · scheduler · proxy

  • Flows & webhooksDesigner tests and inbound triggers
  • Scheduler & WebcronCron ticks and CMS jobs
  • jorchestrator-proxyCloud relay — no inbound to your LAN

Virtual hostname

abc12345.local.jorchestrator.app
  • Pure CLI for scripts and headless servers — or use console / connect --console for the web dashboard
  • Deploy on a LAN host or in Docker: single binary, mount the config
  • Localhost, private LAN, or production behind a firewall — no public port forwarding
  • HTTP, HTTPS, and SOCKS5 upstream proxy support for corporate egress
  • Stable virtual tunnel hostnames with live online/offline status in Domain Setup
  • Cloud flows, JOrchestrator Scheduler, and CMS Webcron reach your CMS securely

Included on Pro, Designer, and Agency plans (£19/month and above).

Enough proof.

Open a canvas. Ship the first flow today.

Why JOrchestrator

Agencies. Designers.
Developers who hate busywork.

Client fleets or a single savage stack. Same canvas. Same power.

Agencies

One fleet. One canvas.

Every client site — Joomla or WordPress — under the same orchestration layer.

Designers

Visual, not a ticket queue.

Complex automations that look like the product, not a backlog of custom plugins.

Developers

Localhost to production.

Tunnel the LAN, ship the flow, keep the receipts — without public port theatre.

Receipts, not vibes

Charts and logs that prove every run — success, retry, failure.

Locked down by default

Token auth, encrypted transport, unguessable webhook URLs.

Milliseconds, not meetings

CMS events fire the canvas the moment the content changes.

Web Scheduler

Last 24 hours · example.com

Active
20 jobs run20/20 successful

Web Scheduler Jobs

Cron with receipts

HTTP scheduling for Joomla and WordPress that proves every run — logs, retries, charts. Missed jobs are a choice you don't have to make.

  • Custom intervals from every five minutes to once a month
  • Automatic retry on failure with configurable policies
  • Detailed execution logs and performance charts
  • One Web Scheduler job per domain for optimal performance

Pricing

Start free.
Scale when it hurts not to.

More domains, tunnels, and AI-assisted setup when your workflows outgrow the free plan.

Starter

For individuals getting started

Free

1

Flows

1

Domains

—

Designer AI

1 Flow
1 Domain
Unlimited flow triggers

Not included

AI setup
Premium nodes
CMS Webcron
Scheduler
LAN tunnels

Pro

For individuals scaling up

£19/month

5

Flows

1

Domains

1M tokens

Designer AI

Up to 5 Flows
1 Domain
Unlimited flow triggers
AI-assisted trigger & node setup
1M designer AI tokens per month
CMS Webcron
JOrchestrator Scheduler
Local development tunnels

Not included

Premium nodes

AI tokens are for the flow designer only — not CMS runtime. Flow execution uses your own API accounts as configured in your CMS plugin settings (Joomla Node Configuration or WordPress JOrchestrator Settings).

Agency

For Teams and agencies

£149/month

∞

Flows

15

Domains

50M tokens

Designer AI

Unlimited Flows
Up to 15 Domains
Extra domains £12/month
Unlimited flow triggers
AI-assisted trigger & node setup
50M designer AI tokens per month
Premium flow nodes
Team members, roles & audit log
CMS Webcron
JOrchestrator Scheduler
Local development tunnels

AI tokens are for the flow designer only — not CMS runtime. Flow execution uses your own API accounts as configured in your CMS plugin settings (Joomla Node Configuration or WordPress JOrchestrator Settings).

Custom plugins were the tax you paid for automation. That tax is over.

One visual interface for agencies, freelancers, and in-house teams — ship CMS workflows without waiting on a developer for every request.

The agencies that win will orchestrate — not hand-code

Open a free canvas. Drop a trigger. Link a domain — production or localhost. Ship the workflow before lunch.

Already have an account?