I Built an n8n Node for Hyros — 4,525 Installs and Counting
After years of wiring up Hyros API calls manually inside n8n HTTP Request nodes, I decided to build a proper community node. Here's what it does, how to install it, and the example workflows 4,500+ marketers are running with it today.
The Problem: Hyros Had No Native n8n Integration
If you've been running Hyros for more than a few months, you know the pain. You have leads coming in from multiple sources — Meta Ads, Google, organic — and you need to push revenue events, call data, and lead info back into Hyros so your attribution stays accurate.
The official Hyros integrations cover the basics. But if you're running any custom automation — syncing CRM data, pushing revenue from Stripe webhooks, tracking calls from Retell AI — you were stuck building raw HTTP Request nodes in n8n and manually managing auth headers, payloads, and error states.
I was doing this for my own clients and copying the same pattern across 20+ workflows. Enough. I built a proper community node so anyone using Hyros + n8n doesn't have to start from scratch.
The node is open source:
What the Node Does
The n8n-nodes-hyros package adds a native Hyros node to your n8n instance. It wraps the Hyros API with proper credential management, type-safe inputs, and response handling — so you can drop it into any workflow like you would any built-in node.
Operations supported:
- Create Lead — Push new leads into Hyros with email, phone, ad source, UTM data, and custom fields
- Track Revenue Event — Report a purchase or revenue event tied to a lead — amount, currency, product, transaction ID
- Track Call Event — Log inbound and outbound call data including duration, outcome, and lead attribution
- Update Lead — Update lead properties in Hyros: status, tags, custom fields, assigned agent
- Get Lead — Retrieve lead details by email or Hyros lead ID for downstream logic
- Track Custom Event — Fire any custom attribution event you've configured in your Hyros account
How to Install It
Community nodes install in two ways depending on your n8n setup. Here's both:
Option 1: n8n UI (Cloud or Self-Hosted)
- Go to Settings → Community Nodes
- Click Install
- Enter the package name:
n8n-nodes-hyros - Click Install and restart if prompted
Option 2: npm (Self-Hosted)
# Navigate to your n8n root and install
npm install n8n-nodes-hyros
# Restart n8n
pm2 restart n8n # or your process manager
Configure Credentials
After installing, create a new Hyros API credential in n8n:
- Go to Credentials → New Credential
- Search for Hyros API
- Paste your Hyros API key (found in Hyros → Settings → API)
- Save — all Hyros nodes will now use this credential
Example Workflows You Can Build
1. Meta Lead Ad → Hyros Lead Sync
Trigger: Meta Leads Ads webhook → Format lead data → Push to Hyros with UTM source → Send Slack notification to sales team.
Result: Every Meta lead is instantly attributed in Hyros with the correct ad source, campaign, and adset. No manual exports.
2. Stripe Webhook → Revenue Event
Trigger: Stripe payment_intent.succeeded → Look up customer email → Find Hyros lead → Track revenue event with amount and product.
Result: Every Stripe payment is automatically attributed to the correct marketing source in Hyros. Your ROAS data stays clean.
3. Retell AI Call → Hyros Call Event
Trigger: Retell AI call webhook on completion → Extract caller phone + duration + outcome → Match to Hyros lead → Log call attribution event.
Result: Voice AI calls are tracked in Hyros attribution, so you know which ads are driving booked calls — not just form fills.
4. GoHighLevel → Hyros Lead Attribution
Trigger: GHL webhook on new contact → Map UTM fields → Create or update Hyros lead with source data from GHL custom fields.
Result: Full attribution loop — from ad click to GHL CRM to Hyros without any manual data entry.
4,525 Installs — Here's What That Tells Me
As of March 2026, the node has 4,525 installs on npm. That's not a vanity metric — it tells me exactly how many automation builders hit the same wall I did and went looking for a solution.
The most common use case based on GitHub issues and DMs: revenue event tracking. People are using Stripe + n8n to push sales data into Hyros so their attribution isn't dependent on Hyros's native integrations alone.
Second most common: lead syncing from custom forms and CRMs that don't have native Hyros integrations — Webflow forms, GHL webhooks, Typeform submissions.
Open source, MIT licensed.
Found a bug or want to add an operation? PRs are welcome. The Hyros API covers more endpoints than I've wrapped so far — particularly the reporting endpoints — and I'm adding those incrementally.
Need Hyros + n8n Automation Set Up?
I build production-grade Hyros attribution systems and n8n workflows for agencies and direct-response brands. If you need the full stack — attribution setup, revenue event tracking, CRM sync, and reporting — I can have it running in a week.