Why this matters
n8n's HTTP Request node speaks the ReachOut API directly. Self-hosted teams keep the data path inside their infrastructure; cloud teams get instant integration. Either way, every call is authenticated by API key and lands in the audit log.
What you get
- No custom n8n node required — the HTTP Request node is enough.
- Self-hosted-friendly: keeps the integration path in your VPC.
- Webhook trigger nodes can react to ReachOut events without polling.
- Idempotency keys honored on every write — safe to retry.
Setup in 4 steps
- Create a ReachOut API key. Studio → Settings → API keys → Create.
- Add an HTTP Request node. Method: POST. URL: https://reachout-pulse-api.usereachout.com/api/contacts. Authentication: Header Auth → Authorization: Bearer YOUR_API_KEY.
- Map inputs. Use n8n expressions to pipe fields from previous nodes into the request body. Add an Idempotency-Key header derived from a stable upstream ID.
- Listen for ReachOut events. Optional: add a Webhook node to receive ReachOut delivery / open / click events. Subscribe via Studio → Settings → Webhooks.