Build workflows with the PreyReach REST API. This community node sends ordinary HTTP resource requests and returns JSON responses. It does not connect to an MCP server or use JSON-RPC.

Installation

Install n8n-nodes-preyreach from Settings → Community nodes in your n8n instance. You can also install the npm package in a self-hosted n8n installation.

Authentication

Create a PreyReach API key in your account and paste it into the PreyReach API credential. The key is sent only to https://api.preyreach.com as a Bearer header. Credentials can be tested with the account endpoint.

Upgrading from 1.x or 2.x: replace the OAuth credential with an API key. Version 2 uses the public REST API's search records and allowance, separately from older MCP searches. Saved-lead operations are not available in this API-key integration. Review existing workflows before running searches.

Resources and operations

Choose a Resource, then an Operation. Only operations and input fields for that resource are shown. Resources: Account, Searches.

Requests

Operation	HTTP request
Account	`GET /v1/account`
Submit search	`POST /v1/searches`
Get search	`GET /v1/searches/:searchId`
Enrich completed search	`POST /v1/searches/:searchId/enrich`

Search submission returns id, status, and pollUrl. Pass that id to Get Search. Use n8n's Wait node between checks while a search is queued or running. Enrichment requires a completed search belonging to the same API key.

Workflow behavior

Each input item produces one linked output item with the original response envelope. List operations offer Return All or a Limit (default 50). The node follows paging tokens internally and combines the result arrays. Single-resource and write operations make one request. Selecting a write operation is sufficient; no extra confirmation checkbox is required. Failed requests stop the workflow unless Continue On Fail is enabled. HTTP errors omit credentials and raw request headers.

Requests use the fixed product API origin, encode resource identifiers, and do not follow redirects. Use a dedicated account for automation when you want separate access and data. Account ownership, workspace permissions, billing limits, and entitlement checks are enforced by the product API.

Development and support

Run npm ci, npm run lint, and npm test to build and validate the package with the n8n node CLI. Source and release automation: preyreach/n8n-nodes-preyreach. Report node issues in GitHub Issues.

Product: PreyReach · Privacy · Agent skill · MCP integration

MIT license.

Release checks (3.2.0)

Resource and Operation definitions are explicit in the TypeScript node source. This minor update preserves API endpoints, credential types and operation identifiers. Every publication must pass Prettier, the official n8n node CLI linter with zero warnings, the runtime tests, and the n8n community package scanner against both TypeScript source and compiled JavaScript. GitHub Actions runs these checks before publishing with npm provenance.

Run npm ci --ignore-scripts, npm test, and npm run review before proposing a release.