Send crawl data where your team already works
Structured captures only help if they land in the tools you already use. Connect Google Sheets or Airtable, download CSV, or POST batches to a webhook — same export record, same sync history.
Destinations your research stack already uses
Connect Google Sheets or Airtable once for the organisation, then attach exports at project, segment, or workflow scope. Columns follow your project schema — including capture URL, category, and timestamps.
Prefer a file or your own pipeline? Create a CSV export for download, or a webhook that receives signed JSON batches as new captures land.
One export model, four ways out
Google Sheets and Airtable keep rows appending as crawls run. CSV builds a downloadable artifact you can share or load elsewhere. Webhooks POST capture batches with optional Bearer auth and HMAC signatures.
Every destination is a first-class export: sync status, counts, and history live on the same Exports tab — not a one-off download that disappears.
From capture to spreadsheet without glue code
No Zapier tax for the common cases. Analysts open the sheet or Airtable base; ops teams wire a webhook into the CRM or warehouse they already run.
Sync when you need a catch-up, or let reconcile jobs keep destinations current as new captures arrive.
Connect Sheets or Airtable under Integrations, then add an export on any project — or ship CSV and webhooks with no OAuth required.
Try for freeGet data out of the crawl
Sheets, Airtable, CSV, or webhook — pick the destination your team already opens every morning.
