Scrapeer

n8n integration

Use the Scrapeer n8n node when an n8n workflow needs to start a saved Scrapeer Cloud Flow, wait for a short run, fetch a run later, or react when a run finishes. Scrapeer runs happen in the cloud and require an active Scrapeer subscription.

What you need

  • A saved Scrapeer Flow that can run in Cloud Runs.
  • A Scrapeer API key from Scrapeer settings.
  • An active subscription with Cloud Runs enabled.

The n8n credential test calls Scrapeer with the API key. Starting a run is still checked by Scrapeer when the run request reaches the API, so an n8n workflow cannot bypass subscription, project, team, or API key permissions.

Add Scrapeer to n8n

In n8n, open Settings → Community nodes, choose Install, and enter the Scrapeer community node package:

@scrapeer/n8n-nodes-scrapeer

Then create a Scrapeer credential in n8n and paste your API key. The node sends the key as an Authorization: Bearer header to https://auth.scrapeer.com.

Start with the Google Maps Leads workflow

The easiest first test is the Google Maps Leads to Google Sheets workflow template for n8n. It runs a saved Scrapeer Google Maps Leads Flow, passes the business type, location, and maximum result count into Scrapeer, normalizes the returned lead rows, and appends them to Google Sheets.

Before importing the n8n workflow, create a Google Maps Leads Flow from the Scrapeer Flow Library. Give it a clear name such as n8n-google-maps-leads, then select that saved Flow in the Scrapeer node inside n8n.

If you created the Scrapeer Flow while the n8n node settings were already open, close and reopen the node settings panel before choosing the Flow. n8n can cache option lists inside an open node panel.

n8n workflow canvas showing a Daily Schedule trigger, search input setup, a Scrapeer Google Maps Leads run, lead normalization, and a Google Sheets append step.
The n8n workflow keeps scheduling and Google Sheets in n8n, while Scrapeer runs the saved Google Maps Leads Flow and returns the lead rows.

Actions

The Scrapeer node includes these actions:

  • List saved flows returns saved Flows available to the API key.
  • Start a saved cloud run starts a Cloud Run and returns the execution ID immediately.
  • Start a saved cloud run and wait for the result starts a run and polls until it finishes or the timeout is reached.
  • Fetch run status and output returns status, output, errors, credits, and timestamps for one execution.
  • List recent cloud runs returns recent executions, with optional status and Flow filters.

For long or unpredictable browser jobs, prefer Start a saved cloud run and then use Fetch run status and output or the trigger. Do not keep an n8n workflow waiting for a long scrape unless the run normally finishes quickly.

Pass data into a Flow

Use Input Variables on the run actions to pass JSON into the Scrapeer Flow before it starts.

{
  "url": "https://example.com/products",
  "searchTerm": "running shoes"
}

Inside Scrapeer, use those values with normal variable syntax:

  • Put {{url}} in a Go To URL Block URL field.
  • Put {{searchTerm}} in a Fill Input Block, Template Block, HTTP Request Block, or another field that accepts variables.

Input variable names must start with a letter or _, then use letters, numbers, or _. Names beginning with __ are reserved. Keep inputs small: pass URLs, search terms, IDs, filters, or small JSON objects, not large scraped datasets or files.

Trigger on finished runs

Use Scrapeer Trigger to poll for terminal Cloud Runs. It can watch all Flows or one Flow ID, and it can emit completed, failed, cancelled, or filtered runs.

By default, the first poll records already-seen runs without emitting them. Enable Emit Existing Runs on First Poll only when you want the first trigger execution to include recent finished runs.

Output

The node returns n8n items with stable Scrapeer fields such as:

  • execution_id
  • project_id
  • project_title
  • status
  • mode
  • trigger
  • created_at
  • updated_at
  • finished_at
  • duration_ms
  • credits_used
  • data
  • outputs
  • error
  • workflow_id

Large files and artifacts should be handled as links or metadata. The node does not return raw internal block previews by default.

Common issues

The credential test fails. Check that the API key is copied correctly and has not been revoked.

The Flow dropdown is empty. Make sure the API key belongs to a user or team that can access saved Flows. If you just created the Flow, close and reopen the node settings panel so n8n reloads the Flow list.

Run Flow fails with a subscription message. Cloud Runs require an active Scrapeer subscription. Scrapeer checks this when the run request reaches the API.

A run starts but does not finish before the wait timeout. Use the immediate run action and fetch the result later, or use the Scrapeer Trigger for finished runs.

A URL input is blocked. Scrapeer blocks private, local, metadata, and otherwise disallowed targets in Cloud Runs. Check the URL value passed through n8n and make sure the Flow is meant to visit a public website.