Saved authentication
Use an existing URL token, bearer token, Basic authentication or an API key in a custom header. Connection settings are stored encrypted.
API & report integration
Collect an HTTPS response or export link. Shape the data into a table your team understands, then make the chosen fields available through your own read-only API.
Use an existing URL token, bearer token, Basic authentication or an API key in a custom header. Connection settings are stored encrypted.
Keep dates fixed or choose a rolling preset such as month to date, previous month or the last 7 or 30 days, with an explicit time zone.
Configure JSON page-number, offset or cursor pagination. Gatherow checks the collection as a whole before replacing its source snapshot.
The link is only the beginning
Response detection handles structured data and supported downloadable files, including exports without a filename extension. When a response contains several lists, choose the record path deliberately.
For changing reports, choose full replacement or updates matched by explicit record keys. Then select a refresh schedule and check the collected results before saving.
data.ordersReview collected rows before connecting
Designed for report collection
A complete JSON GET response, a downloadable CSV report, a spreadsheet export or a paginated JSON endpoint with a defined cursor or page parameter.
You can combine collected reports with files and Google Sheets in the same table.
URLs must use public HTTPS. Private-network endpoints and direct SQL database connections are not supported. The connector does not send POST request bodies or write back to the service.
Collection is bounded by format, size, row and page limits. A partial failed collection does not replace the last valid source snapshot.
A little less copy. A lot more clarity.
Connect a source, choose the fields that matter, and see what comes together.