Resources · Make integration

Hyros Make integrationAutomate Hyros with Make.

Can Make feed Hyros the sales and calls your other tools record? Yes. The Hyros Make integration gives you 4 instant triggers and 6 actions. This guide is for marketers who track attribution in Hyros, and it takes you from the API key to a first working scenario.

Try the Hyros integration on MakeSee the 10 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Hyros Make integration do for you?

The Hyros Make integration links your Hyros account to Make, a no-code tool where you build a scenario: an automation made of modules, each module being one step. Hyros can start a scenario the moment a lead opts in or a sale is attributed, and Make can push leads, calls, clicks and orders back into Hyros.

Get outside sales counted in Hyros. A deal closed by phone or in a checkout tool can still land in your attribution: Create an Order records it and adds the lead if Hyros does not know them yet. If the buyer asks for their money back, Refund a Order updates that lead's income.

Tell your team when a sale is credited. Watch Sale Attributed starts the scenario as soon as Hyros attributes a sale, and a module from your chat app or spreadsheet can take it from there.

Keep booked calls in the picture. When your calendar tool logs a meeting, Create a Call hands it to Hyros. Later, Watch Attributed Call lets you react once Hyros ties that call to a lead.

Make reaches only what these modules and Make an API Call cover. The Make documentation for Hyros also warns that it is AI-generated, so confirm key details with Hyros. Still choosing a tool? Read n8n vs Make, check Make pricing, or start with the Make training.

Connect

How do you connect Hyros to Make?

  1. 01

    Copy your API key in Hyros

    You need an active Hyros account. Open the Settings section in Hyros, then the API Access or API Keys tab, and copy the API key displayed there. Keep it at hand for the next step.

  2. 02

    Open the connection window in Make

    Add any Hyros module to your scenario and click Create a connection. A connection is your Hyros account linked to Make once, then reused by every Hyros module. The Connection name field is optional.

  3. 03

    Paste the key and save

    Enter the API key you copied, or follow the on-screen instructions, and save. The next Hyros module you add simply picks this connection from the list, with no key to paste again.

First scenario

Your first scenario: send an outside sale to Hyros

GoalWhen a sale is recorded in your checkout tool, Make creates the matching order in Hyros.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. This first module is the trigger: search the app where your sales happen, such as your checkout tool.

  2. 02

    Connect the sales app

    Pick the module of that app that watches new sales, click Create a connection and link the account. Make then lists what it can read there, so you choose instead of typing.

  3. 03

    Add Create an Order

    Click the + on the right of the first module, search Hyros and pick Create an Order. Select your Hyros connection, then map the buyer and order details from the sale.

  4. 04

    Test with Run once

    Click Run once and place a test sale. Each module shows the bundles it received (a bundle is one item, here one sale). Open Hyros and check that the order appears.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module; a new scenario runs every 15 minutes by default. Then switch the scenario on. Each module run on one bundle counts as one operation on your plan.

Triggers

Which Hyros events can start a scenario?

4 modules start a scenario when something happens in Hyros. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Hyros as soon as it happens.

Hyros1Watch Assigned Lead Origin

Watch Assigned Lead Origin

Instant trigger

In Make“Triggers when a lead is assigned.”

Starts your scenario as soon as Hyros assigns an origin to a lead. You get each assignment in Make as one bundle, ready for the next module, without opening Hyros to see where a new contact was credited.

How it fires
instant. Hyros calls Make through a webhook as soon as it happens, and the module carries the lightning badge in the editor.
When to use it
you want every newly credited lead routed to the rep, list or sheet that matches its origin.
Watch out
on this module, click Create a webhook before Create a connection, in that order.
Hyros2Watch Attributed Call

Watch Attributed Call

Instant trigger

In Make“Triggers when a call is attributed to a lead.”

Gives you a signal each time Hyros ties a call to a lead, so a sales conversation turns into an event your other tools can act on. The attributed call reaches Make as a single bundle.

How it fires
instant. Hyros calls Make through a webhook as soon as the call is attributed, with no polling on your side.
When to use it
your closers should see in their CRM or chat which lead a call now belongs to, right after Hyros links them.
Watch out
it reacts to attribution, not to the call itself; to record a new call in Hyros, use Create a Call instead.
Hyros3Watch Opted In Lead

Watch Opted In Lead

Instant trigger

In Make“Triggers when a lead has opted in.”

Launches the scenario when a lead opts in, which makes it the natural start for a welcome sequence handled outside Hyros. Every opt-in arrives as its own bundle, one lead at a time.

How it fires
instant. Hyros alerts Make through a webhook as soon as the opt-in happens.
When to use it
a fresh subscriber should be added to your email tool, tagged in your CRM or announced to the team the moment they join.
Watch out
each opt-in runs the scenario and uses operations, so keep the modules after it lean and test the chain with Run once first.
Hyros4Watch Sale Attributed

Watch Sale Attributed

Instant trigger

In Make“Triggers when a sale is attributed.”

Fires when Hyros attributes a sale, which is the moment your revenue gets a source. Make receives that sale as one bundle you can post, log or pass to another app.

How it fires
instant. Hyros calls Make through a webhook as soon as the attribution happens, which is why the module shows a lightning badge.
When to use it
you want a sales channel in your chat app, a row in a revenue sheet or a note in the CRM for every credited sale.
Watch out
if you also send orders with Create an Order, test both scenarios together with Run once so you see how they interact.
Modules

What can Make do in Hyros?

Hyros gives you 6 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Hyros1

Create a Call

Action

In Make“Create a call with all necessary information. Additionally, creates the lead if not already present.”

Logs a call in Hyros with its details and creates the lead on the way if Hyros does not have them yet. Calls booked or made outside Hyros then count in its reporting.

When to use it
your calendar or dialer records a meeting and you want Hyros to know about it without manual entry.
Watch out
because the lead is created when missing, run it once on a contact you know and check the result in Hyros.
Hyros2

Create a Click

Action

In Make“Creates a click for an ad from a platform in Hyros.”

Adds a click on an ad from a given platform to Hyros. You choose this action when a click happened somewhere Hyros does not collect it by itself and you still want it in your data.

When to use it
an ad tool or landing page sends click data to Make and should feed Hyros too.
Watch out
it only records the click; the lead and the sale go through Create a Lead and Create an Order.
Hyros3

Create a Lead

Action

In Make“Create or update lead and its tags in Hyros”

Creates a lead in Hyros, or updates it if it already exists, along with its tags. It is the action to reach for when a contact appears in another tool first.

When to use it
a form, a webinar tool or a CRM captures a person and you want Hyros to hold the same lead with the right tags.
Watch out
since it updates existing leads, the tags you send land on real records, so test with Run once before switching on.
Hyros4

Create an Order

Action

In Make“Create an order with all necessary information. additionally, creates the lead if not already present on the account.”

Records an order in Hyros with its details, and adds the lead to your account if it is not there yet. It is how a sale made outside Hyros gets credited in your numbers.

When to use it
a payment lands in your checkout, invoicing or booking tool and Hyros should see the revenue.
Watch out
sending the same sale twice gives you two orders; place the trigger on a clear event, such as a completed payment.
Hyros5

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Calls any endpoint of the Hyros API with the connection you already set up. It covers what the five dedicated actions and the four triggers do not.

When to use it
you need a Hyros feature that has no module of its own in Make.
Watch out
you write the request yourself, so keep the Hyros API documentation open and test the call with Run once before you build on its result.
Hyros6

Refund a Order

Action

In Make“Refund an order by order id and update the income of the lead.”

Marks an order as refunded using its order ID and updates the income of the lead in Hyros. Your revenue stays honest when a customer gets money back.

When to use it
a refund is issued in your payment tool and Hyros should reflect it on the right lead.
Watch out
it needs the order ID Hyros knows, so keep that ID from the step where you sent the order.
Need help

Need help automating Hyros with Make?

A person reads every message.

FAQ

Hyros and Make: common questions

01Is the Hyros Make integration free?
Yes, on the Make side. Hyros is a standard app, so its modules work from the Free plan. That plan has limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute, lift the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations per month. You still need an active Hyros account; its pricing is on the Hyros site.
02What do you need to connect Hyros to Make?
An active Hyros account and its API key. In Hyros, open Settings, then the API Access or API Keys tab, and copy the key shown there. In Make, add any Hyros module, click Create a connection, name it if you want, and paste the key. For the four instant Watch modules, click Create a webhook first, then Create a connection. The connection is stored once and reused by every Hyros module, so you paste the key a single time.
03Do Hyros triggers in Make fire in real time?
Yes. All four Hyros triggers are instant: Watch Assigned Lead Origin, Watch Attributed Call, Watch Opted In Lead and Watch Sale Attributed. Hyros calls Make through a webhook as soon as the event happens, rather than Make checking on a schedule. That is why these modules show a lightning badge in the editor and ask for a webhook before the connection. Each event arrives as one bundle, and every module that processes it uses one operation on your plan.
04What if a Hyros module is missing in Make?
Use Make an API Call. When the dedicated Hyros actions do not cover your need, this module can call any endpoint of the Hyros API with the same connection, so there is nothing new to set up. You pick the endpoint and the data from the Hyros API documentation. Keep in mind that the Make documentation for Hyros is AI-generated from the vendor docs and may contain mistakes, so confirm important behavior with Hyros before you rely on it in production.
05Should you use Make or n8n for Hyros?
It depends on your criteria, and neither tool wins by default. On Make, Hyros comes with 10 modules: four instant triggers, five actions and Make an API Call, all available from the Free plan. The same app often has an n8n node as well, so check whether one exists for Hyros and what it covers before choosing. Then compare what each tool lets you build for your own case. The n8n vs Make comparison on this site walks through both.
Same platform

Other docs you might need on this stack.

Browse all integrations