Get User
wordpress.get_user
ActionBusiness appsconnection required
Calls the WordPress API with the connection's credentials.
Fetch one user by id. The literal id 'me' resolves to the user the connection authenticates as.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- Username & password
- Providers
- WordPress
- Secret shape
- {"username": "…", "password": "… the application password …"}
- Config it needs
- site_url
- Resolved by
- config.connection_id, else node.connection_id
Configuration
2 fields, 1 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 Id of the user to fetch, or 'me' for the connection's own user. | string | Yes | — | — | me |
context Response scope. 'view' returns rendered HTML only; 'edit' also returns the raw block markup (title.raw, content.raw) and needs edit rights on the item. | string | No | view | one of "view", "edit", "embed" | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"context": "view",
"user_id": "me"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
id WordPress id of the user. | number | — |
name Display name of the user. | string | — |
slug URL slug for the author archive. | string | — |
link Public author archive URL. | string | — |
roles Role slugs; only present when the response context is 'edit'. | array | — |
email Email address; only present when the context is 'edit'. | string | — |
{
"email": "",
"id": 0,
"link": "",
"name": "",
"roles": [],
"slug": ""
}Notes
- GET /wp/v2/users/<id>. Email and roles are only in the response when context=edit and the connection user may read them.
See Get User run in a workflow.
In a technical demo we add the WordPress connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.