Supabase Trigger

Node catalog Triggers

On this page

Receive Supabase row inserts, updates and deletes.

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_trigger. Runtime : nodulz.

Credentials and prerequisites

Supabase webhook secret (integration / supabase_webhook). Shared secret to authenticate Supabase Database Webhooks.

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
`rateLimitEnabled`	`boolean`	-	-
`rateLimitMax`	`number`	-	-; > 0
`rateLimitWindowMs`	`number`	-	-; > 0
`allowedIps`	`array`	-	-; max 256
`blockedIps`	`array`	-	-; max 256
`credentialId`	`string`	`""`	-
`schema`	`string`	`"public"`	-
`table`	`string`	`""`	-
`events`	`array`	`["INSERT","UPDATE","DELETE"]`	-; min 1
`testPayload`	`string`	`""`	-

Configuration help

events Events: Trigger only for selected events. Select at least one.

Initial configuration

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

json

{
  "credentialId": "",
  "schema": "public",
  "table": "",
  "events": [
    "INSERT",
    "UPDATE",
    "DELETE"
  ],
  "testPayload": ""
}

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.