JustFlows

Official plugin · Automation

Elsa Workflows.

Run Elsa Workflows 3 from your Justflows site: design in Elsa Studio inside the admin, then start workflows from comments, forms, your own plugins, or by hand.

Elsa Workflows is built and maintained by the Justflows team. It connects your site to an Elsa server you run, gives every site its own Elsa tenant, and keeps the server credentials on the server, so the browser never sees them.

Documentation Developer referenceComing soon to Admin → Marketplace (beta)
Version
v0.1.0
Price
Free
License
GPL-2.0-or-later
Requires
Justflows 0.4.1 or later
Status
Coming soon (beta)

Credentials stay on the server

API keys, tokens, and OAuth secrets are stored server-side. Staff see whether one is stored, never its value.

Studio in your admin

Design and publish workflows in Elsa Studio without leaving Justflows, and without a second sign-in.

A tenant for every site

Sites share one Elsa server or get a dedicated one per workspace, and each only sees its own workflows.

Starts from anywhere

Comments, form submissions, other plugins, and the admin can all start a workflow, within each site's limits.

Everything Elsa Workflows does

Every feature below ships in the free plugin. Each one links to its page in the documentation.

One connection

Connect the main site to an Elsa Workflows 3 server once.

  • API key, bearer token, or OAuth client credentials
  • Test before saving, and save only when Elsa answers
  • Credentials are write-only: leave a field empty to keep the stored one
Read more

Shared pool or dedicated server

Decide per workspace which Elsa server its sites use.

  • Every site gets its own Elsa tenant on a shared server
  • A dedicated server per workspace, set on the Platform
  • Subsites never see the server address or credentials
Read more

Elsa Studio

The Elsa Studio designer, embedded in the admin for this site's tenant.

  • Signed in with your Justflows session when the connection uses an API key
  • Full width for large workflows
  • The API key never reaches the browser
Read more

Start workflows

Operators start any published workflow from the admin.

  • Optional JSON input and a correlation id
  • Confirmation before every start
  • Input is sent to Elsa and never stored in Justflows
Read more

Executions

Follow what your workflows did, without opening Elsa.

  • Filter by running, finished, or faulted
  • Status, correlation id, times, and incidents for each run
  • Credentials in incident messages are redacted
Read more

Comment workflows

Run a workflow when someone comments on a page or post.

  • Chosen in the Workflow section of the content editor
  • Pending and approved comments start it; spam and trash do not
  • Elsa is called after the comment is saved, so visitors never wait
Read more

Form submissions

Forms starts Elsa when a visitor sends a form.

  • One workflow per form, or an Elsa event every workflow can listen for
  • Field values arrive as workflow input
  • Forms keeps working when Elsa is not connected
Read more

Plugin SDK

Start workflows from your own plugin, for the current site.

  • Trigger an event, dispatch a workflow, or run one and wait
  • Hooks and webhook events after every successful start
  • Your plugin never handles the Elsa credentials
Read more

Staff access

Four capabilities and two ready-made roles.

  • Elsa operators view and start workflows
  • Elsa viewers can look, but not start or change anything
  • Only administrators change the connection
Read more

Plan limits

Platforms decide which sites use Elsa, and how much.

  • Workflow starts per month for each website
  • Turn Elsa off for a website
  • Shared pool and dedicated server as workspace features, also from a subscription plan
Read more

Locked-down calls

Every call to Elsa is checked before it leaves your server.

  • HTTPS only, with private and metadata addresses refused
  • Errors become fixed categories, so no secret reaches a log
  • An audit log of connection changes and workflow starts
Read more

Health checks

Know when Elsa stops answering.

  • A connection check every five minutes, per site
  • Definitions and running and faulted executions counted twice an hour
  • An Elsa connection check in Diagnostics
Read more

Built for developers

Start Elsa workflows from your own plugin, react when they start, or script the Elsa admin.

const elsa = globalThis[Symbol.for("justflows.elsa-workflows.sdk")];
await elsa?.triggerElsaEvent({ eventName: "acme.booking.confirmed", correlationId: bookingId, input: { bookingId } });
// → { ok: true, instanceIds: [ … ], correlationId }

Good to know

Elsa Workflows is in beta and listed as coming soon, so expect changes before 1.0. It connects to an Elsa server you run; Justflows does not host Elsa for you yet.

See the known limits