Resources · Make integration

NotiLens Make integrationAutomate NotiLens with Make.

Need a heads-up in NotiLens when something happens in another tool? The NotiLens Make integration gives you 2 action modules and no trigger. This guide shows how to link your account, build a first scenario that posts a message, and when to reach for the API module.

Try the NotiLens integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the NotiLens Make integration do for you?

The NotiLens Make integration lets a Make scenario (the automation you build in Make, a chain of modules) push a message into NotiLens with no code. Something happens in another app, Make picks it up, and the Send Message module sends the notice for you.

Know when a job fails. A developer can place Send Message at the end of a scenario that watches a deploy tool or a database, so a short alert reaches NotiLens whenever a step goes wrong. Each module is one brick of the scenario, and here NotiLens is always the last one.

Flag a new sale or signup. An online shop can chain a form or payment app to NotiLens: every new order becomes a bundle (one item flowing from module to module) and turns into a message the team sees.

Reach the rest of the API. When Send Message does not cover a need, Make an API Call talks to any NotiLens endpoint with the same connection.

Be clear about the limits: NotiLens has no trigger in Make, so it cannot start a scenario on its own, and the doc itself warns that its content is AI-generated and may contain mistakes. Check the vendor docs for anything critical. If you are still weighing platforms, the n8n vs Make page lays out both, and the Make training covers the editor from zero. Stuck on a run? See Make troubleshooting.

Connect

How do you connect NotiLens to Make?

  1. 01

    Get your NotiLens topic key

    Before opening Make, sign in to your NotiLens account. The doc says you need an active account and a secret key for each topic, so copy the key of the topic that should receive your messages.

  2. 02

    Open a connection from the module

    In your scenario, add a NotiLens module and click Create a connection. A connection is your NotiLens account linked to Make once; you can give it a name so you recognize it later.

  3. 03

    Paste the key and save

    Make's doc gives no NotiLens-specific steps, but since NotiLens works with a secret key per topic, expect the connection window to ask for that key. Paste it, then click Save. Every NotiLens module in your scenarios can now reuse this connection without asking again.

First scenario

Your first scenario with NotiLens and Make

GoalWhen something happens in another app, Make sends a message to NotiLens.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big + to add the first module. NotiLens has no trigger, so this first spot goes to the app where the event happens.

  2. 02

    Pick the starting event

    Search the other app by name, choose its module and connect that account. This module decides when your scenario runs and hands each new item to the next module.

  3. 03

    Add Send Message

    Click the + on the right of the first module, search for NotiLens and pick Send Message. Choose your NotiLens connection, or create it now with your topic key.

  4. 04

    Map the message

    Fill the module fields by mapping data from the first module: a customer name, a status, an error text. Keep the wording short so the notice reads well at a glance.

  5. 05

    Test with Run once

    Click Run once to execute the scenario one time, then open the bundles each module received. Check that a message showed up in NotiLens with the values you mapped.

  6. 06

    Schedule and switch on

    Set the schedule on the first module (a new scenario runs every 15 minutes by default) and switch the scenario on. Each module run counts as an operation on your Make plan.

Modules

What the NotiLens modules do

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

NotiLens1

Make an API Call

ActionIn the docs only

With this module you reach any NotiLens endpoint the listed modules leave out, using the connection you already set up. You write the request yourself, so it suits someone comfortable reading the NotiLens API documentation.

When to use it
a feature you saw in the NotiLens docs has no dedicated module in Make, and Send Message cannot do the job.
Watch out
the Make doc for NotiLens is marked as AI-generated, so confirm the endpoint in the vendor docs before relying on it.
NotiLens2

Send Message

ActionIn the docs only

Here is the module that gets a notice into NotiLens: it takes data from the earlier steps of your scenario and posts it as a message, so the right people hear about an event without checking another tool.

When to use it
almost always as the last brick, after the module that caught a new order, a failed job or a form reply.
Watch out
since each topic has its own secret key, the connection you pick most likely sets the destination topic, so choose it with care.
Need help

Need help automating NotiLens with Make?

A person reads every message.

FAQ

NotiLens and Make: common questions

01Is the NotiLens Make integration free?
Yes, on the Make side. NotiLens is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes of execution per run and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute and allow up to 40 minutes of execution. Usage is counted in operations each month. Your NotiLens subscription is a separate matter: the doc points to the NotiLens pricing page.
02What is needed to connect NotiLens to Make?
An active NotiLens account and a secret key for each topic you plan to send to, according to the Make doc. In Make, add a NotiLens module, click Create a connection, optionally name it, paste the key (the connection should ask for it, though the doc does not detail this step) and click Save. The connection is then shared by every NotiLens module in your scenarios. If you send to several topics, keep track of which key each connection uses, since with one key per topic, the key is most likely what routes the message.
03Does the NotiLens Make integration have a real-time trigger?
No. NotiLens offers no trigger in Make, only 2 action modules. Your scenario therefore starts with another app: a trigger from the tool where the event happens, or a Make schedule, which runs every 15 minutes by default on a new scenario. If the other app has an instant trigger, it calls Make through a webhook as soon as something happens, and Send Message then fires right after in the same run.
04What if a NotiLens module is missing in Make?
Use Make an API Call. When an app has this module, any endpoint of its API can be called from the scenario with the same connection, so you are not limited to Send Message. Keep in mind that the Make doc for NotiLens says its content is AI-generated and may contain mistakes, so verify the endpoint and its behavior in the NotiLens documentation, and contact NotiLens directly for questions about their docs.
05Should NotiLens be automated with Make or n8n?
It depends on the platform your team already uses. The same app often has an n8n node as well, so check whether one exists before choosing. In Make, you get Send Message plus Make an API Call and a visual editor with Run once for testing. The fair comparison is on your own criteria: which tools the rest of your stack connects to, who will maintain the scenarios, and which editor your team finds easier to read.
Same platform

Other docs you might need on this stack.

Browse all integrations