Get User

box.get_user

ActionFiles & storageconnection required

Calls the Box API with the connection's credentials.

Read a Box user's profile; 'me' returns the account the connection authenticates as, which is also what the connection test calls.

Connection

Required: Yes — the node will not save without one
Auth type: OAuth 2.0
Providers: Box
Secret shape: {"client_id": "…", "client_secret": "…", "box_subject_type": "enterprise|user", "box_subject_id": "…"} for a server-authentication app, or {"client_id": "…", "client_secret": "…", "refresh_token": "…"} for OAuth2
Resolved by: config.connection_id, else node.connection_id

2 fields, none required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

Field	Type	Required	Default	Constraints	Example
user_id The Box user id to read, or 'me' for the connected account.	string	No	me	—	—
fields Comma-separated list of extra attributes to return, such as 'space_used,role'.	string	No	—	—	—

Every value below is the contract’s own example or default — nothing invented.

{
  "user_id": "me"
}

One shape.

Field	Type	Example
id The Box user id.	string	—
type Always 'user'.	string	user
name The user's display name.	string	—
login The user's email address / login.	string	—
status Whether the account is active or inactive.	string	—

{
  "id": "",
  "login": "",
  "name": "",
  "status": "",
  "type": "user"
}

Uploads go to upload.box.com and everything else to api.box.com; the nodes pick the right host for you.
Use a Box server-authentication (Client Credentials) app for anything unattended: its credential can be exchanged for a token indefinitely. A plain OAuth2 refresh token is spent by its first use, so that connection needs re-authorising.
The root folder always has the id '0'.

In a technical demo we add the Box connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.