Update User is a Step (action) in Users. Updates a user by User ID or username lookup.
Update User is a Step (action) in Users. Updates a user by User ID or username lookup.
When the flow reaches this step, JOrchestrator executes Update 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.
Update 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 Update User to a flow:
Common patterns on the canvas:
Leave New password blank to keep current password. User groups: empty keeps assignments; otherwise selected groups replace them.
Super user (id 1) cannot be blocked or deleted via related nodes.
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 |
|---|---|---|---|---|---|
userId | User ID | payload-text | Yes | — | Numeric user id, or leave empty and set Username below |
username | Username (lookup) | text | No | — | Find user by login name if User ID is empty |
password | New password | payload-secret-text | No | — | Leave blank to keep current password |
name | Full Name | text | No | — | Leave blank to keep current |
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 |
|---|---|---|---|---|---|
email | email-recipient | No | — | Leave blank to keep current, type address, or select user… |
| Property key | Label | Type | Required | Visible when | Notes |
|---|---|---|---|---|---|
groups | User Groups | user-groups-multi | No | — | Leave empty to keep current; select groups to replace assignments |
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 {{update_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. |
password_changed | boolean | Whether the user password was updated. |
groups | array | User group IDs assigned to the account. |
userId) must be filled before the flow can be saved.Other steps in the same area of the palette:
block-user) — Userscreate-user) — Userswp-create-user) — Usersdelete-user) — Userswp-delete-user) — Users