Rules that reflect your data
Match on up to four fields, remove an exact prefix or suffix, trim whitespace and choose case or type conversions. Blank matching IDs are handled explicitly.
The Gatherow toolkit
Choose the fields, define the relationships and check the result. Gatherow keeps the decisions visible from your first connection to your published API.
Choose a source, inspect detected field types and sample records, and keep the fields you need. For files and reports, you can set a worksheet, header row or record path when the format needs a little guidance.
Field selection stays with the source for future refreshes. You can return to Check data to review the full collected schema.
Explore supported sourcesReview types. Choose fields. Then connect.
Use Canvas or Guided steps to choose and reorder fields, rename columns and combine up to five sources. Click controls and keyboard alternatives support the same work as dragging.
Match records with explicit fields and cleanup rules. For repeated records, use Combine & summarize to sum, average, count or collect unique values. Each source is grouped independently before the results are combined.
Learn how matching works| Customer | Region | Orders | Total |
|---|---|---|---|
| Juniper Studio | North | 12 | €1,840 |
| Forma Supply | West | 8 | €960 |
| Daybreak Co. | North | 15 | €2,250 |
Match on up to four fields, remove an exact prefix or suffix, trim whitespace and choose case or type conversions. Blank matching IDs are handled explicitly.
Filter source rows before aggregation or results afterward. Split delimited field values into rows, choose a sort order and rename the output fields.
Optional AI drafting turns a request into a supported table or API configuration. Review the calculated preview, then explicitly apply the draft to continue editing.
Set response fields, saved filters, sorting and a default page size. Create a key with endpoint access and an expiry, then share it privately with the tool that needs your data.
Responses include pagination, freshness and a snapshot identifier. Use the snapshot across pages to detect changes instead of mixing versions.
Explore access controls{
"data": [{
"customer": "Juniper Studio",
"orders": 12,
"total": 1840
}],
"pagination": { ... },
"meta": { ... }
}Example data · fields chosen in your table
Made to work together
Owners manage access and keys. Editors work on data and APIs. Viewers inspect results. Personal drafts stay separate until saved.
Schedule supported remote sources, see collection status and keep the last valid snapshot when collection or rebuilding fails.
Explain a value shows the source evidence and calculation behind supported result cells. Table history records definitions for review and restoration.
A little less copy. A lot more clarity.
Connect a source, choose the fields that matter, and see what comes together.