Resources · Make integration

Notify! Make integrationAutomate Notify! with Make.

Need an alert on screen when something happens in another app? The Notify! Make integration gives you 2 action modules: one sends a notification, the other reads the history. This guide connects your account and builds a first scenario.

Try the Notify! integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Notify! Make integration do for you?

The Notify! Make integration links your Notify! account to Make, a no-code tool where you build a scenario: a chain of modules, each module being one brick that does one job. Both Notify! modules are actions, so another app or a schedule starts the scenario, and Notify! delivers the alert at the end of the chain.

Tell the sales team when an order lands. For an online store, a new order in the shop app can start the scenario, and Send a notification to a device or group pushes the alert to the sales group, so nobody has to keep the dashboard open.

Warn one person when a request comes in. A support lead can get a notification on a single device whenever a form tool collects a request, with the customer name mapped from the previous module.

Look back at what went out. Notification History, going by its name, reads notifications already sent. The documentation does not describe its output, so test it with Run once before you build on it.

Know the limits first: Make says it cannot provide complete documentation for Notify!, so the editor, not a guide, shows you each field. The app has no Make an API Call module either. If a step blocks you, the Make troubleshooting page and the Make training can help, and n8n vs Make explains how the two tools differ.

Connect

How do you connect Notify! to Make?

  1. 01

    Add a Notify! module

    In a scenario, add a Notify! module, for example Send a notification to a device or group, then click Create a connection. The connection is your Notify! account linked to Make once; every Notify! module reuses it.

  2. 02

    Name the connection

    Naming it is optional. A clear label, such as the account owner or the team, saves you a guess later when several connections sit in the same dropdown and you need to pick the right one.

  3. 03

    Authorize and save

    Make then asks you to authorize it on the Notify! page or to paste the key Notify! gives you. The documentation does not say which method this app uses, so follow the window, then click Save.

First scenario

Your first scenario with Notify!

GoalWhen an event happens in another app, Make sends a Notify! notification to a device or a group.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Notify! has no trigger, so this first module comes from the app where the event happens.

  2. 02

    Add the Notify! action

    Click the + on the right of that first module, search Notify! by name and pick Send a notification to a device or group. Click Create a connection if it is your first Notify! module.

  3. 03

    Fill the fields

    Fill the module fields. Make lists what it can read once the connection exists, and you can map data from the first module, such as a customer name, straight into the notification.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Check that the alert shows up, then read the bundles each module received; a bundle is one item passed from one module to the next.

  5. 05

    Schedule and switch on

    Set the schedule on the first module: a new scenario runs every 15 minutes by default, and the Free plan cannot go lower. Then switch the scenario on so it keeps running without you.

Modules

What the Notify! modules do

Notify! gives you 2 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Notify!1

Notification History

ActionIn the docs only

You get a look back at alerts from inside the scenario; going by the module name, it reads notifications already sent. The documentation does not describe what it returns, so your first run will tell you more than any guide.

When to use it
when you need to check what went out, for instance before sending a second alert about the same event, or to copy the trail into another app.
Watch out
click Run once and read the bundles before mapping anything, since the output is not documented.
Notify!2

Send a notification to a device or group

ActionIn the docs only

This module puts your alert on a screen: aim it at one device when one person needs to know, or at a group when a whole team does. Each run uses one operation, the unit Make counts on your plan.

When to use it
at the end of a chain, once the previous module holds something worth an alert, like a paid order.
Watch out
Make documents Notify! poorly, so do a first Run once with your own device as the target before pointing it at a real group.
Need help

Need help automating Notify! with Make?

A person reads every message.

FAQ

Notify! and Make: common questions

01Is the Notify! Make integration free?
Yes. Notify! is a standard app in Make, available from the Free plan. That plan gives you 2 active scenarios, at least 15 minutes between scheduled runs, 5 minutes of execution per run, 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, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations each month, one per module per bundle, so each notification sent uses one operation for that step. Any cost on the Notify! side is outside the scope of this page.
02What do you need to connect Notify! to Make?
A Notify! account and a Make account, as far as the documentation goes, since it lists no prerequisite. Add a Notify! module, click Create a connection, name it if you like, then either authorize Make on the Notify! page or paste the key Notify! gives you, and click Save. The documentation does not say which of the two methods applies, because Make notes it lacks public information on this app. Once saved, both modules reuse the same connection, so you only do this once per account.
03Can Notify! start a Make scenario on its own?
No. Notify! has no trigger in Make, only 2 actions, so something else has to start the scenario. You have two options. Put a trigger from another app first: an instant trigger is called by that app through a webhook as soon as something happens, while a scheduled trigger is polled on the scenario's schedule. Or simply run the scenario on the schedule set on its first module, every 15 minutes by default and down to 1 minute on paid plans. Notify! then sends its alert when the chain reaches it.
04What if the Notify! module you need is missing in Make?
Then this app will not stretch to cover it. Notify! has only 2 modules in Make and no Make an API Call module, the generic block some apps offer to reach their API directly. Anything beyond sending a notification or reading the history needs another route: look for another notification app in Make that does what you need, or ask the Hackceleration team to study your case. And since Make says its Notify! documentation is limited, test each module with Run once before relying on it.
05Make or n8n for Notify!?
It depends on where the rest of your automations live. On Make, Notify! gives you 2 ready modules that you add from the editor, connect once and test with Run once, which suits a first scenario. n8n may offer a Notify! node too, but check its catalog before deciding, since this page only covers Make. The useful criteria are the modules each tool offers for this app, the other apps in your chain, and the editor your team already knows. The comparison page linked earlier walks through how the two tools differ.
Same platform

Other docs you might need on this stack.

Browse all integrations