Short answer: Drop the "Supabase → Select 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 |
Columns select | string | Optional | Comma-separated column names. Use * for all columns. |
Filter (query param) filter | string | Optional | PostgREST filter, e.g. 'status=eq.active' or 'age=gt.18' |
Order By order | string | Optional | Column to sort by with direction, e.g. 'created_at.desc' |
Limit limit | string | Optional | Maximum number of rows to return |
{"table": "e.g. users","select": "* or id,name,email","filter": "e.g. status=eq.active","order": "e.g. created_at.desc","limit": "100"}
[{"id": 1,"name": "John Doe","email": "john@example.com","created_at": "2025-01-15T12:00:00Z"}]
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.