Short answer: Drop the "Supabase → Update Rows" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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 | Column name to filter by |
Operator filter_operator | options | Required | Operator. Options: Equals, Not equals, Greater than, Less than, In list |
Filter Value filter_value | string | Required | Filter Value. Example: 123 |
Update Data (JSON) data | string | Required | JSON object with columns to update |
{"table": "e.g. users","filter_column": "e.g. id","filter_operator": "{{trigger.filter_operator}}","filter_value": "e.g. 123","data": "{\"status\": \"active\", \"updated_at\": \"2025-01-15\"}"}
[{"id": 123,"status": "active","updated_at": "2025-01-15"}]
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.