What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
To connect Reach to n8n, install the Reach API Community Node on a self-hosted n8n instance, create a Reach API token, save it as an n8n credential, and choose a Reach action in your workflow. The documented community-node installation applies to self-hosted n8n, not n8n Cloud.
What you need before connecting Reach
- A self-hosted n8n instance. The community-node installation process described here is not for n8n Cloud.
- A Reach API token generated through its current API or token interface.
- A defined workflow, such as passing a new form submission or CRM record into a contact action.
The Reach and n8n guide documents the node-based route. Its Community Node guide covers installation and credentials. Interface labels can change, so use the current guides if your dashboard differs.
As an Amazon Associate I earn from qualifying purchases.
How to use Reach with n8n
- Install the node. In your self-hosted n8n instance, open Settings > Community Nodes > Install, enter
n8n-nodes-hostinger-api, and confirm. Restart n8n if prompted. - Generate an API token. Open Reach’s current API or integrations area and follow its link to the public API documentation or token-generation interface. The exact menu wording varies across pages. Store the token securely.
- Save the token as an n8n credential. In n8n, open Credentials, create a Reach API credential, paste the token, and save it. Do not place the token in ordinary workflow text or in a workflow export that you share publicly.
- Add the API node and choose Reach. Add the Reach API node to a workflow, select the saved credential, set Category to Reach, and choose an action from the available list.
- Connect a trigger and map the data. Add a suitable source trigger, then map its email and other relevant fields to the selected Reach action. Available triggers and field names depend on the upstream app and action.
- Test before activating recurring runs. Use a small set of records for which you have permission to send marketing communications. Check the workflow run and confirm the resulting contact or data change in Reach before enabling the workflow.
What the Reach actions can manage
Reach describes more than 30 actions in the node. The documented API areas include contact and contact-field management, tags, segments, and retrieval of information about forms, campaigns, automations, and profile settings. Profile information can include domain status, plan limits, and features. The available actions in your installed node determine which operations you can perform.
Do not assume that an action can send a campaign or perform another write operation unless that operation appears in the current action list. Reach’s API documentation is the place to check supported endpoints and request details.
#1 Best Overall
Example: sync a form or CRM record to Reach
A basic contact-sync workflow has three parts: a trigger that detects a new submission or record, a mapping from the source fields to the Reach contact action, and a test run that checks the result. Possible sources include forms, Google Sheets, CRMs, and commerce platforms such as Shopify or WooCommerce. These examples do not guarantee that every app has a particular n8n trigger or that its fields map directly to a Reach action.
- Map the source email to the contact action’s email field.
- Map only additional fields the action accepts and that your workflow needs.
- Test with a consented record and check that the intended contact appears in Reach.
Adding a record to a marketing system is not permission to send marketing. Reach’s contact guidance says to add only contacts who have explicitly consented to receive marketing communications.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.When to use the HTTP Request node instead
If the community node does not expose the operation you need, n8n’s HTTP Request node can make API calls directly. This route requires you to consult the Reach public API documentation for the correct endpoint, method, authentication, parameters, headers, and request body. The exact endpoint and payload depend on the operation; do not guess them.
| Route | Best fit | What you need to handle |
|---|---|---|
| Reach API Community Node | An operation exposed as a Reach action in the node | Install and maintain the community node; configure its credential and action fields. |
| n8n HTTP Request node | An API operation not exposed by the community node | Follow the Reach API schema and configure the request, authentication, and data yourself. |
For HTTP Request setup, n8n’s n8n API tutorial outlines the general configuration areas. It does not supply Reach-specific endpoint or payload examples. Keep credentials private, and protect any webhook URL used to trigger the workflow from unauthorized access.
Quick Recap
Rank #4
- Book - powershell for sysadmins: workflow automation made easy
- Language: english
- Binding: paperback
Troubleshooting setup issues
- The community-node menu or installation option is missing: verify that the instance is self-hosted; the documented installation route is not for n8n Cloud.
- The Reach API credential fails: check that the credential contains the API token and that you selected it on the node. Generate or confirm the token through Reach’s current API interface if needed.
- The action or field you need is not listed: check the current Reach API documentation for the supported endpoint and schema; use HTTP Request only with those details.
- The workflow runs but the contact is not as expected: inspect the trigger output and field mapping, then test with one consented record before turning on recurring synchronization.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
