← All integrations
Import.io + Make

Automate web data workflows with Make

Add Make’s custom webhook as the Import.io extractor’s webhook URL and every successful run starts your scenario.

Connects via
Webhook
Setup
5 min
Available on
Every plan
Scenario
Trigger   Webhooks → Custom webhook
Next      HTTP → Make a request → GET the run’s JSON link from the payload
Then      Iterator → your destination modules

How it connects.

Source

The web

Any public page, rendered, through managed proxies

Engine

Import.io

Rendering, proxy routing, captcha handling, extraction

Path

Webhook

POST on every successful run

Destination

Make

A custom webhook scenario that runs on every successful extraction.

What teams do with it.

Branching workflows

Route rows by retailer, category or price change to different destinations.

Enrichment steps

Download the run’s JSON, iterate the rows and enrich them with other APIs.

Visual monitoring

See every execution and payload in Make’s history.

Set it up.

  1. In Make, add a Webhooks module, then Custom webhook, and copy the address.
  2. Paste it as the webhook URL in the Import.io extractor’s settings.
  3. Run the extractor once so Make learns the payload structure, then add modules.

Questions.

How do I read the rows?

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.

When does the webhook fire?

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.

How do I secure the webhook?

Webhooks accept custom headers. Add a shared-secret header in the extractor’s webhook settings and reject any request that doesn’t carry it.

Run Make
on fresh data.