Node reference

Create User for Joomla

Creates a Joomla user from a flow — registration webhook, CRM sync, or admin approval — instead of a user plugin.

Overview

Creates a Joomla user from a flow — registration webhook, CRM sync, or admin approval — instead of a user plugin.

When the flow reaches this step, JOrchestrator executes Create User against your linked site or an external integration, using the field values you set on General and Design. Downstream steps can read the output payload fields defined for this node.

Why use this node

Create User is a action step in the Users group. Action steps run in the middle or end of a flow. They perform work on your CMS, call external services, or transform data for the next step.

Typical reasons teams add Create User to a flow:

  • Provision Joomla users from a paid signup or CRM event
  • Set groups from payload fields after an If branch
  • Email credentials or a welcome path after the account exists

Example workflows

Common patterns on the canvas:

  1. Trigger or Webhook → upstream steps → Create User → Send Email or CMS update
  2. Scheduled trigger → Create User → Debug (while testing) → production action

How to set it up

Password supports {{placeholders}}; user groups from the list or empty for Registered (ID 2). Password is stored hashed.

Good to know

Use After Save user event flows for welcome email or provisioning without blocking registration.

Properties panel

The designer shows these tabs for this node:

TabPurpose
InfoPlain-language description and output payload fields for downstream steps
GeneralCanvas label and read-only node ID
AIOptional assistant to help draft settings from plain language
DesignNode-specific configuration fields

System (automatic — not edited by the user)

These fields are managed by the designer or runtime — you do not type into them directly:

Property keyLabelTypeRequiredVisible whenNotes
_nodeIdNode IDnode-idNo——
_payloadFieldsAvailable Fieldspayload-panelNo——

User-configured — General tab

Property keyLabelTypeRequiredVisible whenNotes
labelLabeltextNo—Node label

User-configured — Design tab

Property keyLabelTypeRequiredVisible whenNotes
usernameUsernametextYes—Login name or {{placeholder}}
emailEmailemailYes—[email protected]
passwordPasswordpayload-secret-textNo—Plain password or {{placeholder}} — stored hashed on save
nameFull NametextNo—Display name

CMS-backed (options from the linked site)

Property keyLabelTypeRequiredVisible whenNotes
groupsUser Groupsuser-groups-multiNo—Select groups — leave empty for Registered (ID 2)

CMS site configuration (not on this node's properties panel)

Credentials, API keys, mailers, SMTP, and integration defaults are configured in the CMS plugin under Node Configuration, not per step on this node. Link the flow to a domain before testing CMS-backed fields.

Output payload fields

After this step runs, later nodes can reference these fields using placeholders such as {{create_user.id}}.

Field keyTypeDescription
idstringPrimary record identifier.
usernamestringText value from this node's output.
emailstringText value from this node's output.
namestringDisplay name of the record.
groupsarrayUser group IDs assigned to the account.

Validation rules

  • Username (username) must be filled before the flow can be saved.
  • Email (email) must be filled before the flow can be saved.