Resources · Make integration

LOBSTR.IO Make integrationAutomate LOBSTR.IO with Make.

What if every finished scraping run delivered its data on its own? The LOBSTR.IO Make integration gives you 7 modules: 1 instant trigger, 3 actions and 3 searches. It suits anyone who already runs Squids in LOBSTR.IO, and this page walks you from connection to a working first scenario.

Try the LOBSTR.IO integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the LOBSTR.IO Make integration let you automate?

The LOBSTR.IO Make integration links your LOBSTR.IO account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a single brick such as a trigger, an action or a search. Your Squids (the saved scrapers you set up in LOBSTR.IO) can then start runs and hand over their results without anyone copying files by hand.

Results that leave LOBSTR.IO by themselves. Watch Runs wakes the scenario when a run finishes, fails or changes status. Add List Results right after it and every scraped row becomes a bundle, one item passed to the next module, ready for a spreadsheet or a CRM.

Runs started from another tool. A sales team that logs a new target somewhere else can have Make call Launch a Run on the matching Squid, so the scrape starts without opening LOBSTR.IO at all.

An inventory of your scrapers. List Squids and List Runs return what exists in your account, and Get a Squid reads the name, crawler and parameters of one of them. A data lead can use that to check which scraper did what before sharing numbers.

Some limits are worth knowing. The Make documentation for this app is marked as AI-generated from the vendor docs, so it may hold mistakes; test each module with real data. When a need falls outside the 7 modules, Make an API call reaches other endpoints with the same connection. The same app can also exist on n8n; the n8n vs Make comparison explains how the two tools differ. To go further, the Make training covers scenario design, and the Make pricing guide explains how operations are counted.

Connect

How do you connect LOBSTR.IO to Make?

  1. 01

    Copy your API key in LOBSTR.IO

    You need an active LOBSTR.IO account first. From the dashboard, open Settings, go to the API key section and press Copy. Keep that key at hand: Make asks for it when you create the connection.

  2. 02

    Add a LOBSTR.IO module and create the connection

    In your scenario, add any LOBSTR.IO module and click Create a connection. A connection is your LOBSTR.IO account linked to Make once, then reused by every module of the app. The Connection name field is optional but helps when you manage several accounts.

  3. 03

    Paste the key and save

    Paste the API key you copied, or follow the instructions shown on screen, then save. The connection then appears in the dropdown of every LOBSTR.IO module you add later, so you never type the key twice.

First scenario

Your first scenario with LOBSTR.IO

GoalWhen a run ends in LOBSTR.IO, Make lists the rows it collected so you can send them anywhere.

  1. 01

    Create the scenario

    Open the Scenarios page in Make, create a new scenario and click the big + in the middle of the canvas. That empty circle becomes your first module.

  2. 02

    Add Watch Runs

    Search for LOBSTR.IO, pick Watch Runs, click Create a webhook and then Create a connection with your API key. The lightning badge on the bubble tells you this trigger is instant.

  3. 03

    Add List Results

    Click the + on the right of the trigger and choose List Results. Map the run coming from Watch Runs into it, so Make fetches the rows of exactly the run that just changed.

  4. 04

    Test with Run once

    Press Run once, then let a run finish in LOBSTR.IO. Open the small bubble above each module to read the bundles it received and check that the scraped rows look right.

  5. 05

    Switch the scenario on

    Once the test is clean, add the destination of your choice after List Results and turn the scenario on. From then on, each finished run pushes its results through without you touching anything.

Triggers

What starts a LOBSTR.IO scenario

1 module starts a scenario when something happens in LOBSTR.IO. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by LOBSTR.IO as soon as it happens.

LOBSTR.IO1Watch Runs

Watch Runs

Instant trigger

In Make“Triggers when a run in lobstr.io is finished, failed, or has changed status.”

Watch Runs gives your scenario a signal each time a LOBSTR.IO run finishes, fails or moves to another status, so the next steps start from fresh news instead of guesswork.

How it fires
instant, LOBSTR.IO calls Make through a webhook as soon as it happens, which is why the module shows a lightning badge.
When to use it
as the opening brick of any flow that must react to the end of a scrape, for example to collect results or to alert someone when a run fails.
Watch out
a status change also fires it, so filter on the status you care about before spending operations on the rest of the scenario.
Modules

What LOBSTR.IO can do in Make

LOBSTR.IO gives you 6 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

LOBSTR.IO1

Get a Squid

Action

In Make“Retrieves details of a specific Squid (your automation) in lobstr.io, including name, crawler, and parameters.”

Get a Squid hands you the full card of one saved scraper: its name, the crawler behind it and the parameters it runs with. Useful to document or double-check a setup.

When to use it
before launching a run from Make, to confirm you are pointing at the right Squid and not a similar one.
Watch out
it reads one Squid only; to browse them all, List Squids is the better pick.
LOBSTR.IO2

Launch a Run

Action

In Make“Launch a new run for a selected Squid”

Launch a Run starts a new scraping run on the Squid you select, so data collection kicks off from any event that reaches your scenario.

When to use it
when a new target lands in a form or a sheet and the scrape should follow without anyone logging in to LOBSTR.IO.
Watch out
pair it with Watch Runs in a second scenario to catch the moment the run ends.
LOBSTR.IO3

Make an API call

Action

In Make“Performs a custom API request to a lobstr.io endpoint. Specify the method, path, and optional JSON body.”

Make an API call lets you reach a LOBSTR.IO endpoint that none of the other six modules covers, reusing the connection you already created. You choose the method, the path and, if needed, a JSON body.

When to use it
when a feature exists in the LOBSTR.IO API but has no ready-made module in Make.
Watch out
you are on your own with the API documentation here, so test the request with Run once first.
LOBSTR.IO4

List Results

Search

In Make“Returns structured results from a specified Run or Squid. Supports pagination and optional task filtering.”

List Results brings back the structured rows collected by a given run or Squid, each row becoming a bundle you can map into a sheet, a database or a message.

When to use it
right after Watch Runs, to turn a finished scrape into usable data.
Watch out
a search can return many bundles, and each one counts operations in the modules that follow; the task filter helps trim what you pull.
LOBSTR.IO5

List Runs

Search

In Make“Lists all runs for a specific Squid.”

List Runs shows the history of runs for one Squid, one bundle per run, so you can see what happened to a scraper over its lifetime.

When to use it
to build a small report of past runs, or to find the run whose results you want to fetch again.
Watch out
it works on a single Squid; pick that Squid first, possibly with List Squids.
LOBSTR.IO6

List Squids

Search

In Make“Lists your Squids (saved scrapers) from lobstr.io with pagination. Use it to select a Squid or inspect configurations.”

List Squids returns the saved scrapers of your account, page by page, which gives you an inventory to choose from or to audit their configuration.

When to use it
at the start of a flow that must loop over every Squid,.
Watch out
results come in pages, so check you receive the whole list and not only the first batch.
Need help

Need help automating LOBSTR.IO with Make?

A person reads every message.

FAQ

LOBSTR.IO and Make: common questions

01Is the LOBSTR.IO Make integration free?
Yes, on the Make side. LOBSTR.IO is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum interval of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans drop the interval to 1 minute and allow unlimited active scenarios. Every module execution on a bundle counts as one operation on your plan. Your LOBSTR.IO subscription is a separate matter, described on their own pricing page.
02What do you need to connect LOBSTR.IO to Make?
An active LOBSTR.IO account and its API key. In LOBSTR.IO, open the dashboard, go to Settings, then the API key section, and click Copy. In Make, add a LOBSTR.IO module, click Create a connection, give it a name if you like and paste the key. For the Watch Runs trigger, which is instant, click Create a webhook before creating the connection. The connection is then reused by all 7 modules of the app.
03Does the LOBSTR.IO trigger in Make fire in real time?
Yes. Watch Runs is an instant trigger: LOBSTR.IO calls Make through a webhook as soon as a run finishes, fails or changes status, and the module shows a lightning badge for that reason. There is no scheduled trigger for this app, so no 15 minute polling to wait for. Keep in mind that every status change sends a signal, so a filter right after the trigger keeps only the events that matter to your flow.
04What if a LOBSTR.IO module is missing in Make?
Use Make an API call. It sends a custom request to any LOBSTR.IO endpoint with the method, path and JSON body you set, through the same connection as the other modules. It needs the LOBSTR.IO API documentation at hand. Also note that the Make documentation for this app is flagged as AI-generated from the vendor docs and may contain errors, so test each module on a real Squid before relying on it.
05Make or n8n for LOBSTR.IO?
It depends on the tool your team already uses. On Make, LOBSTR.IO offers 7 modules including an instant trigger, and this page covers only that side. Whether a LOBSTR.IO node exists on n8n is not documented here, so check that first. If both are available, compare how each tool fits your existing scenarios and skills rather than picking by habit, and test the same flow on real runs before committing.
Same platform

Other docs you might need on this stack.

Browse all integrations