Resources · Make integration

OneSignal Make integrationAutomate OneSignal with Make.

Need a push, email or SMS to leave OneSignal the moment something happens in another tool? The OneSignal Make integration gives you 8 modules, 7 actions and 1 search. This guide connects your account, builds a first scenario and explains which modules still deserve your time.

Try the OneSignal integration on MakeSee the 8 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the OneSignal Make integration do for you?

The OneSignal Make integration lets a Make scenario, the automation you build in Make as a chain of bricks, send messages through your OneSignal app. Something happens in another tool, Make picks it up, and OneSignal delivers the email, push or SMS to your audience without anyone copying data by hand.

Order updates that reach the buyer. For an online store, a new order in your shop app can feed Send a notification, so the customer gets a push or an SMS with the details you mapped from the order.

Alerts for your own team. A support platform flags an urgent ticket, and the same module sends an email notification to the people on call. Nobody has to watch a dashboard to know it happened.

Calls the listed modules do not cover. Make an API call reuses your OneSignal connection to reach any endpoint of the OneSignal API, which is the way out when you need more than a notification.

Two limits to know before you start. OneSignal has no trigger in Make, so your scenario always starts from another app or from a schedule. And six of the 8 modules carry the Deprecated label, which is covered in the notes below. If you want a guided path, the Make training walks through scenarios like these, and Make troubleshooting helps when a run fails. Still hesitating between the two tools? Read n8n vs Make.

Connect

How do you connect OneSignal to Make?

  1. 01

    Copy your keys in OneSignal

    Open your OneSignal dashboard, pick the app you want to automate, then go to Settings in the left sidebar and click Keys & IDs. Copy the App ID and the key labeled REST API Key.

  2. 02

    Add a OneSignal module

    In your Make scenario, add any OneSignal module and click Create a connection. A connection is your OneSignal account linked to Make once, then reused by every OneSignal module you add later.

  3. 03

    Paste the credentials

    Give the connection a clear name in Connection name if you like, then enter the credentials you copied and follow the instructions on screen. Once the connection exists, every OneSignal module in Make can use it.

First scenario

Your first scenario with OneSignal

GoalWhen a new record lands in another app, Make sends a OneSignal notification about it.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. This one comes from the app where the event happens, since OneSignal has no trigger.

  2. 02

    Pick the starting app

    Search the app that holds the event, a shop or a form tool for example, choose its module and click Create a connection to link that account too.

  3. 03

    Add Send a notification

    Click the + on the right of the first module, search OneSignal and choose Send a notification. Connect your account with the keys from the previous section.

  4. 04

    Map the message

    Fill the module fields and drag in data from the first module, such as a name or an order detail. Each bundle, one item passed from module to module, becomes one message.

  5. 05

    Test with Run once

    Click Run once to execute the scenario a single time, then open the bubbles to read the bundles each module received. Send the test to yourself before your audience sees it.

  6. 06

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. From then on, each new event produces its notification without you.

Modules

What each OneSignal module does

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

OneSignal1

Make an API call

Action

In Make“Performs an arbitrary authorized API call.”

This module lets you reach any endpoint of the OneSignal API from your scenario, with the connection you already set up, so you are not limited to the ready-made modules.

When to use it
the thing you need, such as a call that Send a notification does not offer, has no dedicated module on this list.
Watch out
you write the request yourself here, so keep the OneSignal API reference open while you fill it.
OneSignal2

Send a notification

Action

In Make“Sends an email, push or sms notification (message).”

Your customers or your team receive an email, a push or an SMS built from the data of the previous modules. In a typical OneSignal scenario, it is the last step.

When to use it
a shipment, a booking or an urgent ticket should reach someone right after another app records it.
Watch out
every message your scenario sends counts as an operation, one run of one module, so test with Run once on yourself first.
OneSignal3

Add a New Device (Deprecated)

ActionIn the docs only

Its name says it registers a device in your OneSignal app, and Make now labels it Deprecated. The official directory gives it no description, so this page cannot tell you more about its fields.

When to use it
only if an older scenario already relies on it and still behaves as expected.
Watch out
for a new build, check whether Make an API call covers the same need before you depend on it.
OneSignal4

Add a New Purchase (Deprecated)

ActionIn the docs only

By its name, this action records a purchase against a device in OneSignal. Make flags it as Deprecated and gives no official description: a legacy piece, not a starting point.

When to use it
you maintain an existing scenario that logs purchases this way and it still runs cleanly.
Watch out
open that scenario after any failed run, since a deprecated module is the first suspect.
OneSignal5

Add a Session (Deprecated)

ActionIn the docs only

As the title suggests, this one adds a session to a device in OneSignal. Make shows it as Deprecated and publishes no description, so nothing on this page goes beyond its name.

When to use it
keep it in a scenario that already uses it and returns the results you expect in Run once.
Watch out
do not design a fresh scenario around it; look at Make an API call for new work.
OneSignal6

Export Devices to CSV (Deprecated)

ActionIn the docs only

Going by its name, it asks OneSignal for an export of your devices as a CSV file. Make marks it Deprecated and the directory offers no description, so its output is not documented here.

When to use it
an older reporting scenario already calls it and you only need to keep that scenario alive.
Watch out
run it once and read the bundle it returns before you pass anything to the next module.
OneSignal7

Get a Device (Deprecated)

ActionIn the docs only

This action, judging from its title, fetches one device from your OneSignal app so later modules can use its data. It carries the Deprecated label and has no official description.

When to use it
a scenario you inherited reads a single device this way and you are not rebuilding it yet.
Watch out
if the bundle comes back empty in Run once, the module is the first thing to replace.
OneSignal8

List devices (Deprecated)

SearchIn the docs only

Unlike the other modules, this is a search: it can return zero, one or many devices, each one as its own bundle, and every following module runs once per bundle. Make lists it as Deprecated.

When to use it
an existing scenario loops over your devices this way and you want to keep it running.
Watch out
many bundles mean many operations downstream, so test on a small audience first.
Need help

Need help automating OneSignal with Make?

A person reads every message.

FAQ

OneSignal and Make: common questions

01Is the OneSignal Make integration free?
Yes, on the Make side. OneSignal is a standard app, available from the Make Free plan. That plan allows 2 active scenarios, at least 15 minutes between two 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 and remove the cap on active scenarios. Your OneSignal subscription is a separate matter, handled on the OneSignal side, and this page gives no price for it.
02What do you need to connect OneSignal to Make?
You need an active OneSignal account and its API credentials. In the OneSignal dashboard, select your app, open Settings in the left sidebar, then Keys & IDs, and copy the App ID and the REST API Key. In Make, add a OneSignal module, click Create a connection, name it if you want, and enter what you copied. That single connection then serves every OneSignal module in your scenarios, so you only do this once per account.
03Does OneSignal trigger Make scenarios in real time?
No. OneSignal has no trigger module in Make, so it cannot start a scenario by itself. The scenario begins with a module from another app, for example your shop or your form tool, and OneSignal comes after it to send the message. You can also start on a schedule set on the first module, every 15 minutes by default. How quickly the notification leaves then depends on the starting app and on that schedule, not on OneSignal.
04What if the OneSignal module you need is missing in Make?
Use Make an API call. It reaches any endpoint of the OneSignal API with the connection you already created, so it covers what the 8 listed modules leave out. That matters here because six of those modules carry the Deprecated label, and the directory describes none of them. The doc also warns that its OneSignal page is AI-generated and may contain mistakes, so check important details against the OneSignal documentation before relying on them.
05Should you use Make or n8n for OneSignal?
It depends on your criteria rather than on the app. On Make, OneSignal gives you Send a notification, Make an API call and six deprecated modules, with no trigger, and it runs from the Free plan. The same app often has an n8n node too, so check what that node offers for your case. Compare the tool your team already uses, the plan limits that apply to you and the modules you actually need, then pick the one that matches.
Same platform

Other docs you might need on this stack.

Browse all integrations