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. You can include data from related tables, filter rows, sort results, paginate, and optionally return a row count.

Add the action ​

  1. Create (or open) a workflow in the Interface tab or the Data & API tab.
  2. Click Add an action.
  3. Select Supabase → Select.
  4. Select the Supabase Connection you want to use.

Configure the action ​

Table ​

Pick the Supabase table you want to query.

Columns ​

Click Columns to choose which fields are returned.

  • Check the columns you want from the main table.
  • Leave everything selected to return all columns from the main table.

To include data from related tables, use the sections below the column list:

  • References — other tables linked through a foreign key on this table (for example, a category_id column that points to a categories table).
  • Referenced by — other tables that point to this table (for example, comments linked to a posts row).

For each relation you enable:

  1. Turn the relation on.
  2. Pick the columns you want from the related table.
  3. (Optional) Open the relation settings to set a Display name (alias) or change the Join type:
    • Left (Default) keeps rows even when the related record is missing.
    • Inner Only keeps rows that have a matching related record.

You can open nested relations to go deeper (for example, orders → customer → company). WeWeb prevents circular links so you cannot loop back to a table already in the path.

A foreign key column (like post_id) and its linked relation (like posts) are separate. You can return the ID only, expand the related row, or both.

Filters (optional) ​

Open the Filters section, then click Configure Filter.

From there you can:

  • Click Add condition to add a rule.
  • Click Add condition group to combine rules with And or Or logic.
  • Pick the column, operator, and value for each rule.
  • Toggle a rule off to keep it in the panel without applying it.

When you include related data in Columns, you can also filter on columns from those related tables. Use the scope list on the left side of the filter panel to switch between the main table and a linked table.

Common operators include equal, not equal, greater/less than, Like / iLike (pattern match), Is null/true/false, In list, array operators (Contains, Contained by, Overlaps), and Full-text search.

Sorting (optional) ​

Open the Sorting section, then click Configure Sort.

  • Click Add sort to choose a column and direction (Ascending or Descending).
  • Add multiple sort rules to control tie-breaking order.

If you included related data in Columns, you can sort by columns from those related tables using the scope list on the left.

Pagination (optional) ​

Open the Pagination section to limit how many rows are returned:

  • Limit — Maximum number of rows.
  • Offset — How many rows to skip (useful with Limit for pagination).

Advanced (optional) ​

Open the Advanced section for result shape options:

  • Single row — Return one object instead of an array. Returns an error if no row matches.
  • Maybe single — Return one object or null when no row matches (no error).
  • Count — Include a total row count in the response (Exact count, Planned count, Estimated count, or No count).

Maybe single is hidden when Single row is on.

Result ​

The action returns the selected rows as an array (unless you enabled Single row or Maybe single).

If you set Count to anything other than No count, the result also includes a count value.

Common pitfalls ​

You don't get any results ​

Check:

  • Your filters (they might exclude everything).
  • Your Join type on a relation (Inner removes rows without a linked record).
  • Your Supabase Row Level Security rules (the current user might not be allowed to read those rows).

Make sure you enabled the relation in Columns and selected the fields you need. Returning only the foreign key column (for example category_id) does not automatically include the related row.

"Single row" errors when there is no match ​

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

First include that relation in Columns. Then open Filters or Sorting and pick the related table from the scope list on the left.

CONTINUE LEARNING

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

Views →