n8n-nodes-scrapeatlas

Retrieve public profiles, posts, videos, comments, search results and account usage
with ScrapeAtlas in n8n. Select a platform and operation, fill in its parameters,
and pass the complete JSON response to the next node.

Install

In self-hosted n8n, open Settings → Community nodes → Install, enter
n8n-nodes-scrapeatlas, and confirm installation. Then add ScrapeAtlas to a
workflow.

For a manual installation, run these commands on your n8n host, then restart n8n:

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

For containers, run the install as the n8n user inside the persistent n8n volume.
See the setup guide for details.

Credentials

Create a customer API key in the ScrapeAtlas dashboard.
Add a ScrapeAtlas API credential and paste it into API Key. n8n tests the
key against the free authentication endpoint and stores it in its credential store.
Requests send the key only to https://api.scrapeatlas.com.

Use the node

1. Add ScrapeAtlas to your workflow and select your credential.
2. Select Resource, then Operation.
3. Fill in the required fields. Use Additional Fields for optional filters,
   limits and pagination tokens. Array fields accept JSON arrays.
4. Execute the node. Each input item produces one API request and one output item,
   linked to the corresponding input item.

Import the example workflow, select your credential,
and execute it to retrieve the bsky.app profile. A successful retrieval costs
one ScrapeAtlas credit, including partial results; failed requests and account
utilities cost zero. Use n8n expressions to supply fields from earlier nodes.

The node can also be selected as a tool for n8n AI agents.

Output and pagination

The output is the endpoint's full JSON response. Check status and coverage;
field names vary by endpoint. Null values, warnings and pagination tokens are
preserved. Use Split Out on the endpoint's list field to process records.

To get another page, pass the response's token to the corresponding parameter in
Additional Fields. Workflow loops should have an explicit page limit and stop
when no continuation is returned. Each page is a separate request and can use a
credit. The node does not automatically paginate or retry requests.

HTTP and API failures stop execution. To handle them in a workflow, set n8n's
On Error setting to continue; the output includes error, httpStatus and the
original failure body when the gateway returned one. Transport errors use a
generic message so request credentials and query values cannot leak into errors.

Development

The endpoint catalog is generated from the repository's public API catalogs and
runtime schemas. Run pnpm mcp:generate after endpoint changes; this also updates
n8n. pnpm n8n:check checks freshness and runs n8n's TypeScript build and linter.
node --test scripts/n8n.test.mjs exercises the node's execution interface offline.
The package has no external runtime dependencies besides n8n's workflow peer.

For setup help, contact ScrapeAtlas support.

License

MIT. The ScrapeAtlas mark is copied from this repository's official website asset.