Get User is a Step (action) in Users. Retrieves a Joomla user by User ID, email, or username.
Get User is a Step (action) in Users. Retrieves a Joomla user by User ID, email, or username.
When the flow reaches this step, JOrchestrator executes Get 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.
Get 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 Get User to a flow:
Common patterns on the canvas:
Returns profile fields and group ids in the payload.
Password hash is never returned — only safe profile data for downstream steps.
The designer shows these tabs for this node:
| Tab | Purpose |
|---|---|
| Info | Plain-language description and output payload fields for downstream steps |
| General | Canvas label and read-only node ID |
| AI | Optional assistant to help draft settings from plain language |
| Design | Node-specific configuration fields |
These fields are managed by the designer or runtime — you do not type into them directly:
| Property key | Label | Type | Required | Visible when | Notes |
|---|---|---|---|---|---|
_nodeId | Node ID | node-id | No | — | — |
_payloadFields | Available Fields | payload-panel | No | — | — |
| Property key | Label | Type | Required | Visible when | Notes |
|---|---|---|---|---|---|
label | Label | text | No | — | Node label |
| Property key | Label | Type | Required | Visible when | Notes |
|---|---|---|---|---|---|
email | email | No | — | [email protected] or {{placeholder}} | |
username | Username | text | No | — | Login name or {{placeholder}} |
These fields can pull live options or values from the Joomla/WordPress site linked to the flow:
| Property key | Label | Type | Required | Visible when | Notes |
|---|
| userId | User ID | email-recipient | No | — | Numeric id, {{placeholder}}, or select Joomla user… Provide at least one way to find the user (they work as OR — any filled field can match):
• User ID — numeric id, pick from the your site user list, or {{placeholder}} • Email — account email address or {{placeholder}} • Username — login name or {{placeholder}}
If you fill more than one, your site tries them in order until a user is found. Password is never returned. Value kind: userId |
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.
After this step runs, later nodes can reference these fields using placeholders such as {{get_user.id}}.
| Field key | Type | Description |
|---|---|---|
id | string | Primary record identifier. |
username | string | Text value from this node's output. |
email | string | Text value from this node's output. |
name | string | Display name of the record. |
block | number | Whether the user account is blocked. |
sendEmail | number | Numeric value from this node's output. |
registerDate | string | Account registration date/time. |
lastvisitDate | string | Last site visit date/time. |
activation | string | Account activation token or status. |
groups | array | User group IDs assigned to the account. |
success | boolean | Whether the operation completed successfully. |
Other steps in the same area of the palette:
block-user) — Userscreate-user) — Userswp-create-user) — Usersdelete-user) — Userswp-delete-user) — Users