Create Auth User
supabase.auth_create_user
ActionDatabases & warehousesconnection required
Calls the Supabase API with the connection's credentials.
Create an Auth user directly, without the email or SMS round trip, and optionally mark the address or phone as already confirmed.
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
7 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 |
|---|---|---|---|---|---|
email Email address for the new user. Either this or a phone is required. | string | No | — | email format | — |
phone Phone number in E.164 form. Either this or an email is required. | string | No | — | — | +14155550123 |
password Initial password. Leave blank to create the user without one, so they must use a magic link or OAuth. | string | No | — | credential material | credential |
email_confirm Mark the email as already confirmed so no confirmation mail is needed. | boolean | No | false | — | — |
phone_confirm Mark the phone number as already confirmed. | boolean | No | false | — | — |
user_metadata Free-form profile data the user can read and edit (raw_user_meta_data). | object | No | — | — | — |
app_metadata Application-controlled data the user cannot edit, such as roles or plan. | object | No | — | — | — |
- At least one of email, phone must be set.
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"email_confirm": false,
"phone": "+14155550123",
"phone_confirm": false
}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 Create 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.