ActionSupabaseUpdated September 2026

How do I delete rows from a Supabase table?

Short answer: You can delete rows in Supabase by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Supabase Delete Rows action to a workflow, map its 4 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Delete Rows in Supabase — start free All 7 Supabase actions

Delete Rows in Supabase — start free

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.

Triggered by

Apps that pair well as the trigger for Delete Rows.

Any of these apps can fire this action as part of a workflow.

Google Sheets → Supabase

2 Google Sheets triggers

HubSpot → Supabase

18 HubSpot triggers

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 run history shows the failed step with its input and the error message Supabase returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Delete Rows support batch operations?

Run Delete Rows inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Supabase's rate limits.

More actions