Skip to content
scrapeatlas.Dashboard

Integrations

ScrapeAtlas for n8n

Retrieve public social data in your n8n workflows. Choose a platform and operation, then pass the JSON response to your next step.

Set up the nodeView on npm

Install on self-hosted n8n

  1. Open Settings → Community nodes → Install in your n8n instance.
  2. Enter n8n-nodes-scrapeatlas and confirm the installation.
  3. Add ScrapeAtlas to a workflow.

For a manual installation, run these commands in your n8n host's community-node directory, then restart n8n:

Terminal
mkdir -p ~/.n8n/nodes
cd ~/.n8n/nodes
npm install n8n-nodes-scrapeatlas

For containers, install as the n8n user inside the persistent n8n volume. Follow the n8n manual installation guide for your deployment.

Add your API key

  1. Create a key in your ScrapeAtlas API-key dashboard.
  2. Add a ScrapeAtlas node and create a ScrapeAtlas API credential.
  3. Paste your key into API Key and save. n8n validates it with the free authentication endpoint.

The node sends your credential to https://api.scrapeatlas.com. Successful retrievals cost one credit, including partial results. Failed requests and account utilities cost zero credits.

Choose your request

  1. Select the platform under Resource.
  2. Choose an Operation and fill in its required fields.
  3. Use Additional Fields for filters, limits and pagination tokens. Enter array values as JSON arrays.
  4. Execute the node. Each input item produces one request and one output item.

Use n8n expressions to pass values from previous nodes. You can also select ScrapeAtlas as a tool for an n8n AI agent.

Example: retrieve a Bluesky profile

  1. Add a Manual Trigger, then a ScrapeAtlas node.
  2. Select Bluesky and Profile.
  3. Set Handle to bsky.app, select your credential, and run the workflow.

Download the example workflow and import it into n8n. Select your credential after import. See the profile reference for the response fields.

Use results and request more pages

Each output item contains the full endpoint response, including null values, coverage warnings and pagination tokens. Check status and coverage before using the data. Use Split Out on the endpoint's array field to process individual records.

For another page, pass the returned token to the matching field under Additional Fields. Set a page limit in your workflow and stop when no continuation is returned. Each page is a separate request.

Failures stop the node. To route them through your workflow, set n8n's On Error option to continue and inspect error, httpStatus and body. HTTP 401 means the key needs attention; 402 means you need credits; 429 means you reached a rate limit. See Errors & responses.