Delete Rows: Supabase action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Table Name table	string	Required	Table Name. Example: users
Filter Column filter_column	string	Required	Filter Column. Example: id
Operator filter_operator	options	Required	Operator. Options: Equals, Not equals, Greater than, In list
Filter Value filter_value	string	Required	Filter Value. Example: 123

Sample request

{
  "table": "e.g. users",
  "filter_column": "e.g. id",
  "filter_operator": "{{trigger.filter_operator}}",
  "filter_value": "e.g. 123"
}

Returns

[
  {
    "id": 123,
    "name": "John Doe"
  }
]

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Delete Rows.

What does the Delete Rows action do in Supabase?

Deletes rows from a Supabase table that match a filter (eq, neq, gt, in, like, etc.). PostgREST requires at least one filter, so empty filters are rejected as a safety guard.

What inputs does Delete Rows require?

Required: Table Name, Filter Column, Operator, Filter Value. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Supabase returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Delete Rows support batch operations?

Yes. Run Delete Rows inside a Loop node to process arrays. Tiny Command handles Supabase's rate limits automatically so you don't have to throttle manually.

More actions