Resources · Make integration

HypeRate Make integrationAutomate HypeRate with Make.

Can Make pull your HypeRate heart rate into other tools? The HypeRate Make integration offers 1 action module, Retrieve Heart Rate Data, and no trigger. This page shows how to link your account, where that module fits, and how to build a first scenario around it.

Try the HypeRate integration on MakeSee the 1 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the HypeRate Make integration do for you?

The HypeRate Make integration lets a Make scenario, meaning the automation you build as a chain of steps, ask HypeRate for heart rate data and hand the result to the next step. Each step is a module, one brick of one app, and HypeRate brings exactly one: Retrieve Heart Rate Data, an action that runs when the scenario reaches it.

Because HypeRate has no trigger, it never starts a scenario by itself. Something else has to kick things off: the trigger of another app you already use, or the clock Make puts on the first module, which runs a new scenario every 15 minutes by default. Once the run reaches Retrieve Heart Rate Data, the value it gets back becomes a bundle, the item passed from one module to the next, and you can map it into a sheet, a message or a database row further down the chain.

Three typical setups follow from that. A logging flow, where a scheduled run reads the heart rate and appends it to a spreadsheet app so the history lives outside HypeRate. A notification flow, where another app's event fetches the current reading and posts it in a chat channel. A stream overlay helper, where the reading is pushed to a tool your audience sees. In each case HypeRate is the middle step, never the starting point.

Be clear about the limits. Make's own documentation says it cannot describe HypeRate completely because too little public information exists about the app, so the page stays on what is known: one action, no trigger, no Make an API Call module. Test every setup with Run once before relying on it, and keep the Make troubleshooting guide nearby.

If you weigh another automation tool, the n8n vs Make comparison lays out the criteria, and Make training covers scenario basics step by step.

Connect

How do you connect HypeRate to Make?

  1. 01

    Add the HypeRate module

    In a scenario, click the +, search for HypeRate and pick Retrieve Heart Rate Data. The module panel opens with a Create a connection button, since Make needs your account before it can read anything.

  2. 02

    Name and authorize the connection

    Click Create a connection and, if you like, give it a clear name. A connection is your HypeRate account linked to Make once and reused by every HypeRate module. Then follow the window: approve Make on HypeRate's page, or paste the key HypeRate gives you.

  3. 03

    Save and check

    Click Save. The connection now shows in the module's dropdown, and Make can list what it is able to read from your account. If the panel stays empty, reopen the connection and redo the authorization before going further.

First scenario

Your first scenario with HypeRate

GoalWhen an event happens in another app, Make reads your HypeRate heart rate and passes it on.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to place the first module. Pick the trigger of the app that should start the flow, such as a new row or a new message.

  2. 02

    Add Retrieve Heart Rate Data

    Click the + on the right of that first module, search for HypeRate and choose Retrieve Heart Rate Data. Select your connection, or create it now with Create a connection.

  3. 03

    Fill the module and map data

    Fill in the fields the module asks for. Once the connection exists, Make shows what it can read, and you can map values from the first module into the HypeRate step instead of typing them.

  4. 04

    Test with Run once

    Click Run once. Make executes the scenario one time and shows the bundles each module received, so you can see exactly what HypeRate sent back before adding the destination step.

  5. 05

    Schedule and switch on

    Add the module that should receive the reading, then set the schedule on the first module (every 15 minutes by default) and switch the scenario on. Each module run counts as one operation on your plan.

Modules

What the HypeRate module does

HypeRate gives you 1 module. For each one: what it does for you, when to reach for it, and what to watch out for.

HypeRate1

Retrieve Heart Rate Data

ActionIn the docs only

This action fetches heart rate data from your HypeRate account at the moment the scenario reaches it, then hands that reading to the next module as a bundle you can map anywhere.

When to use it
after another app's trigger or a schedule, when you want the current reading saved, posted or compared.
Watch out
it cannot start a scenario on its own, and Make documents it only partly, so check the output with Run once first.
Need help

Need help automating HypeRate with Make?

A person reads every message.

FAQ

HypeRate and Make: common questions

01Is the HypeRate Make integration free?
Yes, HypeRate is a standard app, so you can use it on Make's Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations, one per module run on one bundle, so each Retrieve Heart Rate Data call counts.
02What do you need to connect HypeRate to Make?
A HypeRate account and a Make account. Make's documentation lists no specific prerequisite for HypeRate and gives no dedicated connection steps, so the generic path applies: add the HypeRate module, click Create a connection, name it if you want, authorize Make on HypeRate's page or paste the key HypeRate provides, then click Save. The same connection is reused by every HypeRate module in your scenarios, so you only set it up once.
03Can HypeRate start a Make scenario by itself?
No. HypeRate has no trigger module in Make, scheduled or instant, so it cannot launch a scenario on its own. Start the flow another way: with the trigger of another app you use, or with the schedule on the first module, which runs every 15 minutes by default on a new scenario and can go down to 1 minute on paid plans. Retrieve Heart Rate Data then runs as a step inside that flow whenever the scenario reaches it.
04What if the HypeRate module you need is missing?
It depends on what you need. HypeRate has a single action in Make and no Make an API Call module, so Make gives you no way to reach any other HypeRate data. Make also states that its HypeRate documentation is incomplete due to limited public information. If Retrieve Heart Rate Data does not cover your case, look for another app that holds the same data, or ask the team for help designing the flow.
05Should you use Make or n8n for HypeRate?
It depends on the tool you already run. On Make, HypeRate offers one action, Retrieve Heart Rate Data, no trigger, and works on the Free plan. The same app often has an n8n node too, so check what each side provides before you decide. The useful criteria are which modules you need, how your flow starts, and which platform already hosts your other automations. Pick the one where your other automations already live.
Same platform

Other docs you might need on this stack.

Browse all integrations