Supabase

Node catalog Actions

On this page

Read and write Supabase rows or call an RPC function.

Usage and specifics

Configure the project connection and table access. RLS policies and key permissions apply to operations. Configure trigger events before publishing.

Technical type : supabase. Runtime : nodulz.

Credentials and prerequisites

Create and configure the credential : supabase

Create credentials in your nodulz instance’s Credentials area, then select them on the node. Availability depends on ownership and sharing. See the credentials guide for access and rotation.

Parameters

Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.

Parameter	Type	Default	Values / limits
`credentialId`	`string`	`""`	-
`operation`	`enum`	`"select"`	`select`, `insert`, `update`, `upsert`, `delete`, `rpc`
`schema`	`string`	`"public"`	-
`table`	`string`	`""`	-
`columns`	`string`	`"*"`	-
`filters`	`string`	`"{}"`	-
`data`	`string`	`"{}"`	-
`limit`	`number`	`100`	-; ≥ 1, ≤ 10000
`onConflict`	`string`	`""`	-

Configuration help

operation Operation: Work with rows through the Supabase REST API, or call an exposed PostgreSQL function.
limit Maximum rows: Requested read limit, from 1 to 10,000. The Supabase server limit may be lower.

Initial configuration

Initial catalog configuration example, to adapt before running. Keep secrets in credentials.

json

{
  "credentialId": "",
  "operation": "select",
  "schema": "public",
  "table": "",
  "columns": "*",
  "filters": "{}",
  "data": "{}",
  "limit": 100,
  "onConflict": ""
}

Verification

Test with representative data. Check node output in the inspector and logs, then use editor mapping for downstream fields. A trigger test with a simulated payload does not validate external service delivery.