Lection + Make: send scheduled scrape rows to any scenario

Make receives each finished scheduled scrape from Lection through a Custom webhook. Add an iterator for the rows, then send them to any module in your scenario.

Start the 30-day Standard trial See setup steps

Requires: Standard, Professional or the 30-day Standard trial, since the Integrations delivery tab is on paid plans. You also need a Make account with a scenario.

← All integrations

What it does

Custom webhook in

Lection sends JSON with the event, schedule, run and dataset to the URL you paste.

Rows as an array

dataset.records holds one object per row, and dataset.columns gives the header order.

Optional secret

Set a secret in Lection and it is sent as the X-Lection-Secret header, so your scenario can check it.

Download link

When a run has an export, download.url is a time-limited link to the file.

Set it up

5 steps, about ten minutes the first time.

1
Add a Custom webhook in Make
Create a scenario, add the Webhooks module, choose Custom webhook, and copy the URL that Make generates.
2
Paste the URL in Lection
Open your schedule, go to the Integrations tab, pick Make and paste the URL. Add a secret if you want the header check.
3
Run a test scrape
Click Run now on the schedule. Back in Make, click Redetermine data structure so the webhook learns the payload fields.
4
Iterate and map the rows
Add an Iterator on dataset.records, then map each row into Google Sheets, Airtable, a database or any other module in the scenario.
5
Turn the scenario on
Activate the scenario so it receives every completed scheduled run. Turn it on before you rely on it.

Using Zapier or n8n instead? The webhook guides cover each one, along with Slack, Discord and Teams. All webhook guides

What Make receives

A shortened example. Real runs include more fields, and sample values here are made up.

Payload (shortened)

{
  "event": "scheduled_scrape.completed",
  "version": 1,
  "delivered_at": "2026-10-12T14:00:03.120Z",
  "schedule": { "name": "Competitor prices - weekly", "cadence": "weekly" },
  "run": { "status": "completed", "rows_extracted": 2 },
  "dataset": {
    "rowCount": 2,
    "columns": ["product_url", "name", "price"],
    "records": [
      { "product_url": "https://shop.example/p/1", "name": "Widget A", "price": "19.99" },
      { "product_url": "https://shop.example/p/2", "name": "Widget B", "price": "5.00" }
    ]
  },
  "download": { "url": "https://.../exports/run.csv?token=...", "expires_in_seconds": 2592000 }
}

Example use cases

Lead lists into your CRM

Run a Google Maps or directory search on a schedule, then add each business to your CRM from the iterator.

Price changes into a database

Send competitor prices to a Postgres or Airtable table on every run, and keep the history in your own system.

Routing by status

Use a router on run.status to alert your team on failed runs and load the rows for successful ones.

Frequently asked questions

Do I need a special Make app?

No. The Custom webhook module is enough. Lection sends plain JSON, so any scenario that starts from a webhook can receive it.

Lection says the webhook failed. Why?

Lection waits up to 12 seconds for a 2xx response and does not retry. Keep the first modules fast, or respond first and do the slow work after. The run is still saved in Lection.

Can I protect the webhook with a secret?

Yes. Set a secret in Lection and compare the X-Lection-Secret header in a filter before the scenario runs.

Is webhook delivery free?

It is on paid plans. The 30-day Standard trial includes it, and a card is required to start the trial.

Put Make to work with Lection

Start free, or try Standard free for 30 days to turn on webhook delivery to Make.

Start the 30-day trial Start free