Resources · Make integration

WiserNotify Make integrationAutomate WiserNotify with Make.

Can Make work with your WiserNotify account? Yes. The WiserNotify Make integration gives you 2 action modules: Get Data and Make an API Call. This guide shows how to link your API key, build a first scenario and test it before you switch it on.

Try the WiserNotify integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the WiserNotify Make integration do for you?

The WiserNotify Make integration links your WiserNotify account to Make, a no-code tool where you build a scenario (the automation itself, a chain of steps). It has no trigger of its own, so the scenario starts on a schedule or on an event in another app, then WiserNotify steps in with one of its 2 action modules.

Send WiserNotify data somewhere useful. Put Get Data after a trigger from another app, then add a module of the tool where the information should land, a sheet or a chat channel for example. The official doc gives no description of what Get Data returns, so run it once and read what comes back before you map anything.

Reach what the list does not cover. Make an API Call talks to any endpoint of the WiserNotify API with the connection you already set up. It is the way out when Get Data is not enough, as long as you know which endpoint to call.

Chain the two. Read something with Get Data, then use Make an API Call to act on it. That pattern is the first scenario below.

Keep the limits in mind. Make's own doc page for WiserNotify says its content is AI-generated and may contain mistakes, so check anything important against WiserNotify's documentation. The same app often has an n8n node too, and the n8n vs Make comparison helps you pick. New to the editor? The Make training starts from zero, and Make troubleshooting covers scenarios that stop.

Connect

How do you connect WiserNotify to Make?

  1. 01

    Copy your API key

    You need an active WiserNotify account. In WiserNotify, click your name at the top left of the page. The profile page opens and shows your API key: copy it and keep it at hand.

  2. 02

    Open the connection window

    In Make, add a WiserNotify module to your scenario and click Create a connection. A connection is your WiserNotify account linked to Make once, then reused by both modules.

  3. 03

    Paste the key and save

    The Connection name field is optional, but a clear name helps if you run several accounts. Paste the API key you copied, or follow the instructions Make shows on screen, and save.

First scenario

Build your first scenario with WiserNotify

GoalWhen the schedule fires, Make reads data with Get Data, then calls the WiserNotify endpoint you choose with Make an API Call.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Search for WiserNotify and pick Get Data.

  2. 02

    Link your account

    Click Create a connection and paste your API key. Then fill in the module fields; once the connection exists, Make lists what it can read for you.

  3. 03

    Add the API call

    Click the + on the right of Get Data, add Make an API Call, and map values coming from Get Data into the request, reusing the same connection.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received. A bundle is one item passed from a module to the next.

  5. 05

    Schedule and switch on

    Open the clock on the first module. A new scenario runs every 15 minutes by default; keep that or change it, then switch the scenario on.

Modules

What the WiserNotify modules do

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

WiserNotify1

Get Data

ActionIn the docs only

Judging by its name, Get Data brings information from your WiserNotify account into the scenario, so the next modules can reuse it without anyone copying it by hand. The official doc does not say which data, so you discover it on the first test.

When to use it
as the first WiserNotify step, when another app or a schedule has started the scenario and you need WiserNotify values downstream.
Watch out
click Run once before mapping fields, and read the bundle it returns.
WiserNotify2

Make an API Call

ActionIn the docs only

With this module you can reach any endpoint of the WiserNotify API from your scenario, using the connection you already created. It fills the gaps left by a catalog of only 2 modules.

When to use it
when Get Data does not return what you need, or when you want to act on WiserNotify rather than just read it.
Watch out
you pick the endpoint yourself, so check the WiserNotify API docs first.
Need help

Need help automating WiserNotify with Make?

A person reads every message.

FAQ

WiserNotify and Make: common questions

01Is the WiserNotify Make integration free?
Yes, on the Make side. WiserNotify is a standard app, so you can use it on the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans drop the interval to 1 minute and remove the cap on active scenarios. Make counts usage in operations, one run of one module on one bundle. You still need your own WiserNotify subscription, which this page does not price.
02What do you need to connect WiserNotify to Make?
An active WiserNotify account and its API key. To find the key, log in to WiserNotify, click your name at the top left and copy the key shown on the profile page. In Make, add a WiserNotify module, click Create a connection, give it a name if you like, and paste the key. The connection is then shared by both modules, so you only do this once per account. The Connection name field is optional, but a clear name helps when you manage more than one WiserNotify account.
03Does WiserNotify trigger Make scenarios in real time?
No, because WiserNotify has no trigger module in Make. The scenario has to start another way. The simplest is the schedule on the first module: a new scenario runs every 15 minutes by default, and the Free plan cannot go below that interval. The other way is a trigger from another app, placed first, with Get Data or Make an API Call after it. Either way, WiserNotify acts as a step inside the flow, never as the starting signal.
04What if the WiserNotify module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the WiserNotify API with the same connection as Get Data, so you are not limited to the 2 listed modules. You do need to know which endpoint to call and what it expects, which means reading the WiserNotify API docs. Also note that Make's doc page for this app states it is AI-generated and may contain mistakes, so confirm anything important with WiserNotify directly.
05Should you use Make or n8n for WiserNotify?
It depends on the tool you already run. On Make, WiserNotify comes with 2 action modules, one of them Make an API Call, and it works from the Free plan. The same app often has an n8n node as well. Neither tool is ranked here: the n8n vs Make comparison linked above lays out the criteria, so you can decide based on where your other automations already run. If you are just starting with Make, the Free plan is enough to build and test a first WiserNotify scenario before deciding anything.
Same platform

Other docs you might need on this stack.

Browse all integrations