Insert Rows

supabase.insert

ActionDatabases & warehousesconnection required

Calls the Supabase API with the connection's credentials.

Insert one row or a batch of rows into a table and return the rows as the database stored them, including generated ids and defaults.

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

3 fields, 2 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
table The table or view to act on, in the connection's schema.	string	Yes	—	—	orders
rows The row to insert as an object, or a list of objects for a batch insert. Column names must match the table; omitted columns take their defaults. An empty list is refused — there would be nothing to write.	array	Yes	—	≥ 1 characters; array of object	[{"customer_email":"ada@example.com","total":4200}]
schema Postgres schema for this call (sent as Accept-Profile / Content-Profile). Overrides the connection's schema; leave blank for the connection default.	string	No	—	—	—

Every value below is the contract’s own example or default — nothing invented.

{
  "rows": [
    {
      "customer_email": "ada@example.com",
      "total": 4200
    }
  ],
  "table": "orders"
}

One shape.

Field	Type	Example
table The table the call was made against.	string	—
items The rows PostgREST returned (Prefer: return=representation).	array	—
count How many rows were returned.	number	—

{
  "count": 0,
  "items": [],
  "table": ""
}

A service_role (or sb_secret_…) key has BYPASSRLS and skips every Row Level Security policy on the project; an anon/publishable key is filtered by them.

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.