Branching workflows
Route rows by retailer, category or price change to different destinations.
Add Make’s custom webhook as the Import.io extractor’s webhook URL and every successful run starts your scenario.
Trigger Webhooks → Custom webhook
Next HTTP → Make a request → GET the run’s JSON link from the payload
Then Iterator → your destination modulesAny public page, rendered, through managed proxies
Rendering, proxy routing, captcha handling, extraction
POST on every successful run
A custom webhook scenario that runs on every successful extraction.
Route rows by retailer, category or price change to different destinations.
Download the run’s JSON, iterate the rows and enrich them with other APIs.
See every execution and payload in Make’s history.
The webhook payload links to the run’s JSON, CSV and Excel files. Fetch the JSON with an HTTP module and parse it line by line; it is NDJSON.
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.
Start a Zap every time an Import.io run succeeds.
Setup 5 minMCPWebhookImport.io as an AI Agent tool and as a workflow trigger.
Setup 5 minWebhookStart Microsoft flows from Import.io runs.
Setup 10 minManagedWebhookPrice, competitor and MAP alerts in the channel your team watches.
Setup 5 min