Get Current User
bitly.get_user
ActionBusiness appsconnection required
Calls the Bitly API with the connection's credentials.
Retrieve the user the credential belongs to, including the default_group_guid the other nodes fall back to.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- OAuth 2.0
- Providers
- Bitly
- Secret shape
- {"access_token": "…"} — a Bitly generic access token, or {"client_id": "…", "client_secret": "…", "refresh_token": "…"}
- Config it needs
- group_guid, domain, organization_guid
- Resolved by
- config.connection_id, else node.connection_id
Configuration
This node takes no configuration beyond its connection.
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
login The Bitly login of the authenticated user. | string | — |
name The user's display name. | string | — |
is_active True when the account is active. | boolean | — |
created ISO-8601 timestamp of when the user was created. | string | — |
modified ISO-8601 timestamp of the last change to the user. | string | — |
is_sso_user True when the user signs in through SSO. | boolean | — |
emails The email addresses on the account. | array | — |
is_2fa_enabled True when two-factor auth is enabled. | boolean | — |
default_group_guid The group new Bitlinks land in. | string | — |
{
"created": "",
"default_group_guid": "",
"emails": [],
"is_2fa_enabled": false,
"is_active": false,
"is_sso_user": false,
"login": "",
"modified": "",
"name": ""
}See Get Current User run in a workflow.
In a technical demo we add the Bitly connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.