# Supabase - Workflow node | Docs - nodulz

Source: https://nodulz.com/docs/nodes/supabase

Language: en

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](/docs/credentials/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](/docs/credentials) 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

| Setting | Purpose and guidance |
| --- | --- |
| `operation`<br>Operation | Work with rows through the Supabase REST API, or call an exposed PostgreSQL function. |
| `limit`<br>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.

See also : [Expressions and data](/docs/expressions), [Executions](/docs/executions), [Node catalog](/docs/nodes).

## Explore further

- [Features - nodulz](https://nodulz.com/product/overview)
- [Node catalog - nodulz](https://nodulz.com/product/catalog)
- [MCP server - nodulz](https://nodulz.com/product/mcp)
- [Pricing - nodulz](https://nodulz.com/pricing)
- [Use cases and workflow automation - nodulz](https://nodulz.com/use-cases)
- [Choose what your workflows can do. - nodulz](https://nodulz.com/compare)
- [Documentation - nodulz](https://nodulz.com/docs)