Get User
jira.get_user
ActionBusiness appsconnection required
Calls the Jira Cloud REST API with the connection's email and API token.
Read one Jira user by Atlassian accountId.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- Username & password
- Providers
- Jira
- Secret shape
- {"email", "api_token"}
- Config it needs
- domain
- 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 |
|---|---|---|---|---|---|
account_id The user's Atlassian accountId — find it with jira.search_users. | string | Yes | — | — | — |
expand Comma-separated expansions, e.g. 'groups,applicationRoles'. | string | No | — | — | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
accountId The user's Atlassian accountId. | string | — |
displayName The user's display name. | string | — |
emailAddress The user's email, when their profile shares it. | string | — |
active False for a deactivated account. | boolean | — |
accountType 'atlassian', 'app' or 'customer'. | string | — |
timeZone The user's time zone, e.g. 'Europe/London'. | string | — |
{
"accountId": "",
"accountType": "",
"active": false,
"displayName": "",
"emailAddress": "",
"timeZone": ""
}See Get User run in a workflow.
In a technical demo we add the Jira connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.