Automation library · Data collection

Start ScraperAPI crawler jobs from webhooks

Started by another system calling it, and works across n8n data table. 9 steps: a working afternoon to understand properly.

Medium

9 stepsMedium: a working afternoon
0Branches: places the flow splits
0Loops or waits
1Service it connects to

The flow

Starts it 4Logic 2Service 3

The steps in the order they run, from what starts it.

  1. 1Set up storageManual triggerStarts it
  2. 2Receive crawl requestWebhookStarts it
  3. 3Receive crawl resultsWebhookStarts it
  4. 4Create crawled-pages tableData TableService
  5. 5Build crawl parametersCodeLogic
  6. 6Parse crawled pagesCodeLogic
  7. 7Start crawler jobScraper ApiService
  8. 8Store crawled pagesData TableService
  9. 9Respond with crawler jobRespond To WebhookStarts it

How it's built

Starts on
Another system calling it
Steps
9
Size
Medium: a working afternoon
Connects to
n8n data table
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account. You connect your own accounts after importing it; none are included.

What starts it?

It starts on another system calling it.

Does it use AI?

No. Every step is fixed logic or a call to a service, so it does the same thing every time.

How long does it take to set up?

Plan an afternoon. 9 steps is enough that you should read each one before running it.

How do I import it?

Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.

Before you run it

Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 9 steps before you point it at anything that matters.