Get Auth User
supabase.auth_get_user
ActionDatabases & warehousesconnection required
Calls the Supabase API with the connection's credentials.
Fetch one Auth user by id and return the full record, including user_metadata, app_metadata and the linked identities.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- Supabase
- Secret shape
- the project API key, or {"api_key": "…"} / {"service_role_key": "…"}
- Config it needs
- base_url, schema
- Resolved by
- config.connection_id, else node.connection_id
Configuration
1 field, 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 The user's UUID, as it appears in auth.users.id. | string | Yes | — | — | fbdf5a53-161e-4460-98ad-0e39408d8689 |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"user_id": "fbdf5a53-161e-4460-98ad-0e39408d8689"
}Output
One shape.
result
The provider's response object, as returned.
Extra keys beyond the ones listed can appear.
{}Notes
- Requires the service-role key; an anon/publishable key gets 401 here.
See Get Auth User run in a workflow.
In a technical demo we add the Supabase connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.