X User Info is a Step (action) in Users. Looks up an X user profile (authenticated account or by @username).
X User Info is a Step (action) in Users. Looks up an X user profile (authenticated account or by @username).
When the flow reaches this step, JOrchestrator executes X User Info 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.
X User Info 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 X User Info to a flow:
Common patterns on the canvas:
Leave Username empty for /users/me, or enter a handle without @.
Requires users.read scope. Outputs username, name, description, and profile image URL.
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 |
|---|---|---|---|---|---|
username | Username (optional) | payload-text | No | — | Leave empty for authenticated user — or enter handle without @ |
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 {{x_user_info.success}}.
| Field key | Type | Description |
|---|---|---|
success | boolean | Whether the operation completed successfully. |
userId | string | Text value from this node's output. |
username | string | Text value from this node's output. |
name | string | Display name of the record. |
description | string | Category or contact description text. |
profileImageUrl | string | Text value from this node's output. |
verified | boolean | Boolean flag from this node's output. |
message | string | Human-readable status, error, or result summary. |
Other steps in the same area of the palette:
block-user) — Userscreate-user) — Userswp-create-user) — Usersdelete-user) — Userswp-delete-user) — Users