pin_finding
Pin a finding (a saved, titled view) to a dataset you own. Finding views use the rows.page query language in q: word or "two words" searches text columns; field:value, field:"a b", -field:value, field:* (not null), -field:* (null), field:foo* (prefix); field:>20, >=, <, <=, field:10..20, ISO dates (at:>2026-09-01); dot paths for nested JSON (payload.customer.country:NL); tags:urgent means the list contains it; combine with OR and parentheses. A q starting with SELECT, WITH or FROM runs as SQL against the table data. sort is comma-separated columns, - for descending (-price,name); cols picks and orders visible columns (a,b,c).
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| q | No | Filter in the rows.page query language | |
| sql | No | Optional SQL against the table `data` | |
| cols | No | Visible columns, e.g. id,price,country | |
| note | No | Why it matters, in a sentence or two | |
| sort | No | Sort, e.g. -price,name | |
| title | Yes | Short headline of the finding | |
| token | No | Dataset token (rpt_...) when not using an API key | |
| dataset | Yes | Dataset id | |
| version | No | Pin to this version instead of the latest | |
| row_count | No | Rows matching the view, if you know it |