BigQuery external tables
Query deliveries in place or load them on arrival.
Managed Services deliver each feed into your bucket on schedule. On self-service plans, a small Cloud Run function on the webhook does the same.
Managed Import.io Managed Services → gs://your-bucket/importio/…
Self-service Extractor webhook → Cloud Run function → gs://your-bucket/importio/latest.ndjsonAny public page, rendered, through managed proxies
Rendering, proxy routing, captcha handling, extraction
Built, run and QA’d under an SLA
Managed delivery into your GCS bucket, ready for BigQuery.
Also connects via webhooks.
Query deliveries in place or load them on arrival.
Training and evaluation data staged where your pipelines read.
Grant bucket access instead of copying files around.
Yes. Managed Services deliver directly into BigQuery as well.
Your Managed Services team. They agree destination, format, schedule and schema with you, then build, run, monitor and QA the feed under an SLA.
Amazon S3, Google Cloud Storage, Azure Blob Storage, SFTP, Snowflake, BigQuery, API, email and Slack alerts. Aperture delivers into the same destinations.
Every time a crawl run finishes successfully. Import.io POSTs to your URL with the extractor ID, total URL count and links to the run’s JSON, CSV and Excel outputs. You can view a sample payload in the extractor’s settings.
Webhooks accept custom headers. Add a shared-secret header in the extractor’s webhook settings and reject any request that doesn’t carry it.
Every run delivered into your bucket, on schedule.
Setup 10 minManagedManaged delivery into your Azure storage account.
Set up at onboardingS3 / SFTPManagedFiles on your server, for systems that read from a drop folder.
Setup 10 minManagedEndpointNDJSON loads natively; managed delivery lands it for you.
Setup 10 min