Connect lobstr.io to n8n and automate your scraping workflows
Install the official lobstr.io node in n8n to create batches, add tasks, launch runs, and pull scraped results — plus a trigger node that fires the moment a run finishes.
lobstr.io has an official n8n node, verified by n8n. It comes as a package with two nodes:
- lobstr.io — the action node. Create batches, add tasks, launch runs, and fetch results.
- lobstr.io Trigger — starts a workflow the moment a run finishes, fails, pauses, or resumes.
Between them you can build a full pipeline — scrape, then route the data anywhere n8n connects to — without writing a line of code.
The n8n app runs batches, which it calls Squids, their name in the API v1. To run an operation instead (one call, its records back at once), use an HTTP Request node: POST https://api.lobstr.io/v2/run with the header Authorization: Bearer <your API key> and a JSON body such as {"source": "google_maps", "operation": "places/get", "options": {"place": "Le Bouchon des Filles, Lyon"}}. Every operation's options are in the API docs.
Before you start
- A lobstr.io account with credits.
- n8n 1.57.0 or newer, running Node.js 20.15 or newer.
- Your lobstr.io API key — see how to find your API key.
Watch the setup walkthrough
Install the node
lobstr.io is a verified n8n node, so you install it the same way on n8n Cloud and on self-hosted n8n:
- Open the nodes panel
Click the + in the top-right of the canvas.
- Search for lobstr.io
Type
lobstr.io. The node appears in the results with a verified badge. - Install it
Click it and confirm the install. Both nodes — lobstr.io and lobstr.io Trigger — are added together.
The package is published as @lobstrio/n8n-nodes-lobstr. You only need that name if you're installing manually on a locked-down self-hosted instance — otherwise search is all it takes.
Add your credentials
- Copy your API key
Open the API menu in your lobstr.io dashboard and click Copy.

- Create the credential in n8n
Add a lobstr.io node to a workflow, then create a new lobstr.io API credential and paste the key.
- Save
n8n verifies the key against lobstr.io as you save, so you'll know immediately if it's wrong.
Your API key grants full access to your lobstr.io account. Treat it like a password — never paste it into a shared workflow or an exported template.
What the node can do
| Resource | Operations |
|---|---|
| Crawler | Get, Get Many, Get Parameters |
| Squid | Create, Delete, Empty, Get, Get Many, Update |
| Task | Create, Delete, Get Many |
| Run | Abort, Get, Get Many, Start, Start and Get Results |
| Result | Get Results, by batch or by run |
| User | Get Balance, Get Profile |
Get Parameters on the Crawler resource tells you exactly which task and batch parameters a given scraper accepts. Use it when you're not sure what to feed a crawler you haven't used before.
The two ways to run a scrape
Synchronous — Start and Get Results
Run → Start and Get Results launches the run, polls until it finishes, and outputs the scraped rows as items. One node, data comes out the other side. This is the simplest option and the right default for short scrapes.
This walkthrough does the whole thing inside n8n — providing the input, triggering the run, and collecting the results:
Or follow it as steps:
- Squid → Create
Pick a crawler, for example Google Maps Search Export, and create a batch.
- Task → Create
Add your tasks — URLs or search parameters, depending on what the crawler accepts.
- Run → Start and Get Results
Launch it and get the scraped data back as items.
Three options control the wait:
| Option | Default | What it does |
|---|---|---|
| Max Results | 0 (all) | Caps how many rows come back |
| Poll Interval (Seconds) | 10 | How often the node checks whether the run is done |
| Wait Timeout (Seconds) | 600 | How long it waits before failing |
Event-driven — the trigger node
For long runs, split it in two: let the trigger node wake the workflow when the run finishes, then fetch the rows. This is the most common way people use the node.
- Add the lobstr.io Trigger node
Select the batch you want to watch and pick the events. The default is run.done, which is what most workflows want.
Event Fires when run.doneThe run finished successfully run.errorThe run crashed with an error run.pausedThe run was halted, e.g. account limits reached run.runningThe run started or resumed - Fetch the rows
Add a lobstr.io node set to Result → Get Results, filtered by run, using
{{ $json.id }}from the trigger event. - Send the data on
Add whatever destination you need — a CRM, a database, a sheet, a Slack message.
Activating the trigger replaces any webhook delivery already configured on that batch. If you've set up a webhook in the batch's Delivery panel pointing somewhere else, it will be overwritten.
Things to know
- Launching a run spends credits, and an n8n trigger can fire far more often than you'd click Launch by hand. Put a filter or a schedule in front of the node so a runaway workflow doesn't drain your balance.
- Runs launched from n8n are ordinary runs. They appear in your dashboard, count against your slots, and spend the same credits.
- Every run re-processes every task in the Squid's list. To scrape only new inputs, use Batch → Empty and add fresh tasks before launching.
- Results expire after 7 days on Free, 45 days on Starter and Pro and 90 days on Team and Business (the run's
expires_at) — fetch them before then.
If all you want is the data in a spreadsheet or a bucket, you don't need n8n: lobstr.io can export to Google Sheets or Amazon S3 on its own. Reach for n8n when the data needs transforming, enriching, or routing to several places at once.