Resources · Make integration

Notiff Make integrationAutomate Notiff with Make.

Need a Notiff notification to go out the moment something happens in another tool? The Notiff Make integration gives you 2 action modules. This page shows how to link your account, build a first scenario and pick the right module, without writing code.

Try the Notiff integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Notiff Make integration let you automate?

The Notiff Make integration links your Notiff account to Make so a scenario, the automation you build in Make, can create notifications in Notiff on its own. Notiff has no trigger of its own in Make, so another app or a schedule starts the flow and Notiff receives the result.

Alert the team when a form comes in. A form app starts the scenario, and Create a Notification turns each new answer into a Notiff notification built from what the form collected.

Flag a new deal or a failed payment. Put the trigger of your CRM or billing tool first, then add Create a Notification. Each module is one brick of the scenario, and data from the first brick can be mapped into the second.

Reach what the listed modules skip. Make an API Call lets you call any endpoint of the Notiff API with the same connection, so you are not stuck with a single action.

Know the limit before you start: Make's own documentation for Notiff is marked as limited, because little public information exists about the app. Expect to read Notiff's side for details. If you are weighing tools, the n8n vs Make comparison lays out the differences, Make training covers scenario building from scratch, and Make troubleshooting helps when a run fails.

Connect

How do you connect Notiff to Make?

  1. 01

    Open the connection window

    Add a Notiff module to your scenario, then click Create a connection. A connection is your Notiff account linked to Make once; every Notiff module in your scenarios reuses it afterwards.

  2. 02

    Give it a name you will recognize

    Naming the connection is optional, but a clear label such as the workspace or client it belongs to saves confusion later, when several accounts sit side by side.

  3. 03

    Authorize and save

    Depending on what Notiff asks for, either approve Make on the Notiff page that opens or paste the key Notiff gives you. Then click Save, and the module is ready to fill.

First scenario

Your first scenario with Notiff

GoalWhen a new entry lands in another app you use, Make creates a Notiff notification with its details.

  1. 01

    Create the scenario and add a trigger

    From the Scenarios page, create a new scenario and click the +. Pick the trigger of the app where the event happens, since Notiff has none of its own.

  2. 02

    Add Create a Notification

    Click the + on the right of the first module, search for Notiff and choose Create a Notification. Link your account with Create a connection or pick the one you already made.

  3. 03

    Map the data into the notification

    Fill the fields the module shows. Instead of typing fixed text, click into a field and pick values from the first module, so each bundle (one item passing between modules) produces its own notification.

  4. 04

    Test with Run once

    Click Run once and trigger a real event in the first app. Read the bundles each module received and check that the notification appears in Notiff.

  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 a bundle counts as one operation on your Make plan.

Modules

What the Notiff modules do

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

Notiff1

Create a Notification

ActionIn the docs only

This action creates a notification in Notiff from the data your scenario carries, so an event somewhere else becomes an alert without anyone copying it by hand.

When to use it
right after the trigger of the app you watch, such as a form, a store or a CRM, when a person needs to know that something just happened.
Watch out
it runs once per bundle, so a trigger that returns many items sends as many notifications and uses as many operations.
Notiff2

Make an API Call

ActionIn the docs only

Reach any endpoint of the Notiff API from your scenario, using the connection you already set up, for the cases Create a Notification does not cover.

When to use it
when you need a Notiff feature that has no dedicated module in Make and you know which endpoint handles it.
Watch out
Make's documentation for Notiff is limited, so you will need the Notiff API reference to know the path and the data to send.
Need help

Need help automating Notiff with Make?

A person reads every message.

FAQ

Questions about Notiff and Make

01Is the Notiff Make integration free?
Yes, Notiff is a standard app in Make, so you can use it on the Free plan. That plan has its own limits: 2 active scenarios, at least 15 minutes between two scheduled runs, up to 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the minimum interval to 1 minute, remove the cap on active scenarios and count usage in credits each month.
02What do you need to connect Notiff to Make?
A Notiff account and access to its login or key. Make's documentation lists no prerequisite for Notiff and gives no app-specific steps, so the generic flow applies: add a Notiff module, click Create a connection, optionally name it, authorize Make on the Notiff page or paste the key Notiff provides, then save. Because Make marks its Notiff documentation as limited, keep the Notiff side of the setup open while you connect.
03Can Notiff start a Make scenario in real time?
No, Notiff has no trigger module in Make, so it cannot start a scenario by itself. You start the flow another way: with the trigger of the app where the event happens, which can be instant if that app offers a webhook trigger, or with a schedule on the first module, every 15 minutes by default. Notiff then comes second, and Create a Notification sends the result. Test the whole chain with Run once before you switch the scenario on.
04What if the Notiff module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the Notiff API with the connection you already have, which covers what Create a Notification does not. The catch is documentation: Make says it cannot provide complete documentation for Notiff because too little public information exists, so you will rely on Notiff's own API reference to find the right path and the data to send. If Notiff's API does not expose what you want, look at another app for that part of the flow.
05Should you use Make or n8n for Notiff?
It depends on the tool your team already runs. On Make, Notiff is a standard app open on every plan, with 2 modules: Create a Notification for the common case and Make an API Call for the rest. Apps on Make often have an n8n node too, so check whether one exists for Notiff before choosing. Pick the platform where your other apps and scenarios already live, so the Notiff step joins flows you maintain in one place.
Same platform

Other docs you might need on this stack.

Browse all integrations