Supabase
Databases & warehousesAPI keyConnection test available
Read and write Postgres tables through PostgREST, move Storage objects, and administer Auth users.
OCNORA ships 15 typed Supabase operations. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run.
Before you connect Supabase
- Authentication
- API key
- Credential
- the project API key, or {"api_key": "…"} / {"service_role_key": "…"}
- Connection test
- Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.
What you can do with Supabase
Operations, grouped by what they do to your data.
Update 1
Delete and cancel 3
Other operations 2
A sample Supabase workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Supabase trigger is needed.
- 2Get Auth Usersupabase.auth_get_userFetch one Auth user by id and return the full record, including user_metadata, app_metadata and the linked identities.
- 3Create Auth Usersupabase.auth_create_userCreate an Auth user directly, without the email or SMS round trip, and optionally mark the address or phone as already confirmed.
An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.
Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.
Operations 15
- Create Auth UserCreate an Auth user directly, without the email or SMS round trip, and optionally mark the address or phone as already confirmed.supabase.auth_create_user
- Delete Auth UserDelete an Auth user by id, either permanently or as a soft delete that obfuscates the record and keeps the row.supabase.auth_delete_user
- Get Auth UserFetch one Auth user by id and return the full record, including user_metadata, app_metadata and the linked identities.supabase.auth_get_user
- List Auth UsersList one page of the project's Auth users. Requires the service-role key, which is the only credential the admin endpoints accept.supabase.auth_list_users
- Delete RowsDelete every row a filter matches and return the deleted rows. At least one filter is required, because an unfiltered DELETE would empty the table.supabase.delete
- Insert RowsInsert one row or a batch of rows into a table and return the rows as the database stored them, including generated ids and defaults.supabase.insert
- Call Postgres FunctionCall a Postgres function exposed through PostgREST (POST /rest/v1/rpc/name) and return whatever it produces — a scalar, a row, or a set of rows.supabase.rpc
- Select RowsRead rows from a table or view through PostgREST, narrowing them with structured filters, a column list, an ordering and limit/offset paging.supabase.select
- Create Signed URLCreate a time-limited signed URL for a private Storage object so it can be emailed or handed to a browser without the project's API key.supabase.storage_create_signed_url
- Download Storage ObjectDownload an object from a Storage bucket as a base64 file payload that an upload or parse node downstream can consume directly.supabase.storage_download
- List Storage ObjectsList one page of objects in a Storage bucket, optionally under a folder prefix and filtered by a search term.supabase.storage_list
- Remove Storage ObjectsPermanently delete one or more objects from a Storage bucket and report which ones the API removed.supabase.storage_remove
- Upload Storage ObjectUpload a file to a Storage bucket, either from inline text or from an upstream node's base64 file payload.supabase.storage_upload
- Update RowsUpdate every row a filter matches and return the updated rows. At least one filter is required, because PostgREST accepts an unfiltered PATCH and would rewrite the whole table.supabase.update
- Upsert RowsInsert rows, merging into the existing row when a unique constraint collides (PostgREST's Prefer: resolution=merge-duplicates).supabase.upsert
Supabase questions
- How does OCNORA authenticate with Supabase?
- With a stored API key credential, shaped the project API key, or {"api_key": "…"} / {"service_role_key": "…"}. A connection test can check it when you add it.
- What can I automate with Supabase?
- 15 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Supabase operation I need is not listed?
- Where Supabase has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
- Are there templates that use Supabase?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Supabase calls controlled?
- Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.
More in Databases & warehouses
See your first Supabase workflow run.
Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.