List Auth Users
supabase.auth_list_users
ActionDatabases & warehousesconnection required
Calls the Supabase API with the connection's credentials.
List one page of the project's Auth users. Requires the service-role key, which is the only credential the admin endpoints accept.
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
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 |
|---|---|---|---|---|---|
page Which page of users to fetch, starting at 1. | number | No | — | ≥ 1 | — |
per_page How many users per page. The API defaults to 50 when this is unset. | number | No | — | ≥ 1 | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
items The user records on this page. | array | — |
count How many users this page returned. | number | — |
aud The audience the users belong to. | string | — |
{
"aud": "",
"count": 0,
"items": []
}Notes
- The Auth admin endpoints only answer to a service-role (sb_secret_…) key; an anon/publishable key gets 401 here.
See List Auth Users 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.