Skip to main content
The ReachHunt nodes for n8n let you send DMs, manage leads and campaigns, and start workflows from ReachHunt events, all inside n8n.

​
What you can do

  • Run ReachHunt actions in any workflow with the ReachHunt node: send messages, manage leads and lead lists, and run campaigns and AI agents.
  • Start a workflow when something happens in ReachHunt with the ReachHunt Trigger, such as a reply or a finished campaign.
  • Give the n8n AI Agent ReachHunt actions as tools.

​
Before you start

  • n8n Cloud, or your own n8n server reachable over https.
  • Full access to every section of the ReachHunt workspace, to create an API key.

​
Set up

Setup takes about five minutes.
1

Create an API key

In ReachHunt, open Settings → API and create a key. n8n uses it to work in this workspace.
2

Install the nodes

In n8n, open Settings → Community nodes → Install, enter @reachhunt/n8n-nodes-reachhunt and install it.On your own server without that screen, run this there instead:
3

Add the credential

In n8n, open Credentials → Add credential, search for ReachHunt API, paste your API key and save. Leave Base URL as it is.
4

Build a workflow

Add a ReachHunt node to any workflow, or start a workflow with the ReachHunt Trigger.

​
Start workflows from ReachHunt

Pick the events you want in the ReachHunt Trigger. While the workflow is on, ReachHunt sends each event to it. You can see it in Settings → Webhooks as n8n: <workflow name>. Turning the workflow off removes it. Each event arrives as ReachHunt sends it, with id, type, apiVersion, createdAt, workspaceId and data. See Webhooks overview for every event type. ReachHunt sends events only to public https:// addresses. n8n Cloud works as it is. A self-hosted n8n must be reachable over https, and needs WEBHOOK_URL set if it runs behind a proxy. To send a sample event, open the webhook in Settings → Webhooks and select Send test event.

​
Available actions

Actions that send messages, react, answer requests or start campaigns reach real people from your connected accounts.

​
Workflow ideas

​
Tips

  • Accounts, lead lists, campaigns, AI agents, tags, statuses and teammates come with a searchable list. Switch to By ID, or use an expression instead.
  • Turn on Return All to page through everything, or set Limit. It is 50 by default.
  • Most conversation actions need the account and the conversation. Map them from the trigger, for example {{ $json.data.account.id }} and {{ $json.data.message.conversationId }}.
  • Send At on a scheduled message uses the time zone of the workflow.
  • Leave Status or Assignee empty to clear it.
  • When an action fails, the node shows ReachHunt’s own message, such as Campaign not found. With On Error → Continue, the error goes to the output instead of stopping the workflow.

​
Disconnect n8n

n8n works through its API key. Delete that key in Settings → API to disconnect n8n.