Skip to content

Updating visuals

If you see any images containing outdated UI, please bear with us.

We are updating all content as quickly as possible to mirror our new UI.

Select

Use this action to retrieve rows from a Supabase table.

Add the action

  1. Create (or open) a workflow.
  2. Click + Add action.
  3. Select SupabaseSelect.
  4. Select the Supabase Connection you want to use.

Configure the action

  • Table — The table you want to retrieve rows from.

Columns

  • Columns (optional) — Pick which columns should be returned.
    • Leave it empty to return all columns.

Filters

  • Filters (optional) — Add one or more rules to restrict which rows are returned.

Sorting & pagination

  • Order by (optional) — Which column to sort by.
  • Direction (optional) — Ascending or descending.
  • Limit (optional) — Maximum number of rows to return.
  • Offset (optional) — Number of rows to skip (useful for pagination).

Advanced

  • Single row (optional) — Return a single object instead of an array. This returns an error if no row is found.
  • Maybe single (optional) — Return a single object or null. This does not return an error if no row is found.
  • Include count (optional) — Include the total matching row count in the response (Exact, Planned, or Estimated).

Result

The action returns the selected rows.

If you enable Include count, the result also includes a count.

Common pitfalls

You don’t get any results

Check:

  • Your filters (they might exclude everything).
  • Your Supabase Row Level Security rules (the current user might not be allowed to read those rows).

“Single row” errors when there is no match

Use Maybe single if “no match found” is a valid outcome for your flow.

CONTINUE LEARNING

For reusable, secure datasets (filters + sorting + access rules), use a Table View.

Views →