If you're using n8n for workflow automation and Hyros for ad attribution, you've probably wanted to connect them. Pull campaign performance data automatically. Trigger workflows when conversion events happen. Build attribution reports without touching a dashboard.

n8n-nodes-hyros is how you do it. It's the most-used Hyros community node for n8n — 4,525+ installs and growing.

This isn't an experimental side project. It's the tool agencies actually reach for when they need Hyros in n8n.

Why Connect Hyros to n8n?

Hyros is exceptional at one thing: accurate attribution. It tracks the person, not just the click, and connects ad spend to actual revenue even across long sales cycles, multiple devices, and email attribution paths that pixels miss entirely.

But Hyros is a dashboard. It shows you what happened. It doesn't act on what happened.

n8n is the action layer. It connects your tools, runs logic, and executes workflows automatically. When you connect Hyros to n8n, your attribution data becomes an active input to your business operations — not just a report you check on Fridays.

Examples of what this unlocks:

ROAS drops below threshold → n8n detects it via Hyros, pauses the campaign via ad API, alerts you in Slack
New high-value conversion event → n8n fires, syncs to CRM, notifies sales team, updates attribution dashboard
Weekly client report → n8n pulls Hyros performance data, formats it, sends to clients — fully automated, every time
Lead attribution on form submit → capture UTMs, match to Hyros lead record, push to your pipeline with full attribution context

4,525+ Installs — Most Used Hyros Automation Node

Over 4,500 n8n users have installed n8n-nodes-hyros. By a significant margin, it's the most widely adopted community integration for connecting Hyros to n8n.

At Vixi, this node is embedded in almost every client automation stack where Hyros is involved. We've used it for:

Automated weekly attribution digests sent to Slack
Anomaly detection workflows that alert when CPA or ROAS moves outside normal ranges
Multi-account reporting pipelines that aggregate data across client ad accounts
Custom dashboards fed with live Hyros data via n8n → Google Sheets or Airtable

The install count isn't a vanity metric. These are agencies actively using it in production workflows.

Installation

In your n8n instance:

Go to Settings → Community Nodes
Click Install a community node
Enter: n8n-nodes-hyros
Confirm and restart n8n

Or install directly via npm (for self-hosted n8n):

npm install n8n-nodes-hyros

Once installed, the Hyros node appears in your node palette. Configure it with your Hyros API key and you're ready to build.

Full documentation: Package documentation

What Data Can You Access?

The node exposes the Hyros API endpoints most agencies actually need:

| Resource | Operations | |----------|-----------| | Campaigns | Get all campaigns, get by ID, get performance metrics | | Leads | Get by email, get recent leads, get full attribution path | | Events | Get conversion events, filter by date range and type | | Ad Accounts | List accounts, get attribution summary |

Each operation maps directly to a Hyros API endpoint. You configure the resource and operation in the node, pass your parameters, and the response flows into the next step of your workflow.

Example Workflow: Automated Weekly Attribution Report

Here's a simplified version of the weekly attribution report workflow we run for Vixi clients:

Schedule Trigger — fires every Friday at 4:00 PM
Hyros node — pulls campaign performance for the past 7 days
Code node — formats data, calculates week-over-week changes, flags anomalies
Claude AI node — writes narrative summary: "Campaign X drove 68% of revenue this week, up 22% from last week. Campaign Y is underperforming — ROAS dropped to 1.8x."
Email / Slack — sends formatted report to client

Before this workflow, someone spent 2+ hours every Friday on this. Now it runs automatically, every time, with better analysis than most humans produce manually.

Example Workflow: Lead Attribution Sync to CRM

When a new lead converts via Hyros:

Hyros webhook or scheduled poll — detects new conversion event
Hyros node — pulls full attribution path for the lead (which ad, which campaign, first touch vs. last touch)
CRM node (HubSpot, Monday.com, Pipedrive) — creates or updates contact with attribution data
Slack node — notifies sales team: "New lead from Facebook Campaign X — first touch was 14 days ago, converted after 3 email opens"

Your sales team now knows exactly which ad brought each lead before they pick up the phone. That changes the conversation.

Hyros + n8n + AI: The Full Stack

For agencies building serious automation infrastructure, the real power comes from combining Hyros data with AI reasoning.

The stack we recommend:

n8n-nodes-hyros — pull Hyros attribution data into n8n workflows
Claude AI node in n8n — analyze the data, write summaries, detect anomalies
hyros-mcp — connect Hyros directly to Claude Desktop or AI agents for on-demand attribution queries

These tools complement each other. n8n handles scheduled, event-driven workflows. The Hyros MCP handles conversational, on-demand data access. Together, they cover the full range of ways you'd want to interact with attribution data.

Implementation Support

VIXI’s specialists build HYROS workflows around CRM, payment and reporting requirements. Each engagement defines the supported event paths, checks error handling and includes a documented handover.

Explore our HYROS integrations and automation services to scope your workflow.

Frequently Asked Questions

What is n8n-nodes-hyros? It's a community node for n8n that lets you pull data from Hyros — campaigns, leads, events, attribution — into any n8n workflow. With 4,525+ installs, it's the most-used Hyros integration node for n8n.

Is n8n-nodes-hyros free? Yes. It's fully open-source and free to install and use. You'll need a Hyros account and API key, plus an n8n instance (self-hosted is free; n8n Cloud has its own pricing).

Does it work with self-hosted n8n? Yes. It works with both self-hosted n8n and n8n Cloud. Install via community nodes or directly via npm for self-hosted instances.

What version of the Hyros API does it use? The node uses the current Hyros REST API. For specific endpoint versions and any breaking changes, see the Package documentation.

Can I use this to automate Hyros reporting for multiple clients? Yes — this is one of the most common use cases. Configure separate credentials for each client's Hyros account, and build report workflows that run for each. Many agencies at Vixi do exactly this.

Is there an equivalent for AI agents (not just n8n)? Yes — hyros-mcp is the Model Context Protocol server for Hyros, which lets Claude, ChatGPT, and other AI agents query Hyros attribution data directly.

n8n-nodes-hyros: 4,500+ Agencies Automate Hyros With It