search a table
find rows by the words in them or by what they mean, on the canvas or from your own code.
A table's search box looks for the words you type and for rows that mean something close to them. You get one ranked list, not two modes to choose between.
search on the canvas
Type in the box above the table, headed Search (incl. semantic)…. The search runs over every row, not only the ones loaded, and matches against the row's contents. A search for "warm lamp" finds a row titled "amber light" even if the word lamp never appears. Press the × in the box to clear it.
While a search or filter is active the node shows No matching rows. when nothing fits, and Load more is hidden: results come back as one list.
filter
The funnel button next to the box opens Filter rows. Pick a column, an operator and a value, and the funnel shows the active filter, for example Status ≠ live. Clear filter removes it.
| operator | matches |
|---|---|
| = · ≠ | equal, not equal |
| contains | the text appears in the cell |
| > · < · ≥ · ≤ | greater or less than the value |
| is empty · not empty | the cell has no value, or has one |
A filter is one condition on one column. Combine a filter with a search to narrow a result: the search ranks, the filter cuts.
ask the keeper
The keeper pixie uses the same search. "Which rows are about packaging?" makes it run a query and answer from what comes back. See tables.
search from your own code
The Table API takes the same query: free text, filters and a sort, with a cursor for the next page. That makes a table a small headless CMS: your site queries it, your team edits it on the canvas, and changes show up in both. The endpoints, keys and examples are in the developer doc: Table API.
limits & good to know
- A query returns 50 rows by default and never more than 200 per page.
- Search and filter only read; they never change rows.
related
- tables — columns, rows and the keeper.
- derived columns — columns computed per row.
checked against the product · 2026-10-23