---
title: OneSignal
slug: onesignal
description: How to integrate OneSignal with Make.com
image: https://make-cxp-documentation.ams3.digitaloceanspaces.com/apps-center-icons/PREVIEW_onesignal.png
createdAt: 2025-02-03T13:28:28.553Z
---

| :inlineImage[]{src="https://make-cxp-documentation.ams3.digitaloceanspaces.com/apps-center-icons/onesignal.png" alt="OneSignal logo" caption size="50" width="512" height="512"} | OneSignal is a customer messaging platform for sending push notifications, emails, SMS, and in-app messages. Integrating with Make.com enables users to automate sending notifications, manage audience segments, and trigger personalized messages based on workflow events. |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

:::hint{type="warning"}
This is AI-generated content based on official OneSignal documentation. The content may contain mistakes. Please verify important information. If you have questions on vendor documentation, contact [OneSignal](https://documentation.onesignal.com/docs/en/disabled-apps) directly.
:::

# Requirements

To use the OneSignal app in Make, you must have an active account and an API Key, [create your account on OneSignal](https://onesignal.com/). For subscription, refer to the [OneSignal pricing page](https://onesignal.com/).

# Connect OneSignal and Make&#x20;

To get started, you must first create a connection between OneSignal and Make, allowing the two services to communicate.&#x20;

::::WorkflowBlock
:::WorkflowBlockItem
**Obtain your API Key in your OneSignal account**
:::

:::WorkflowBlockItem
**Create the connection in Make.**
:::
::::

## Obtain your API Key in your OneSignal account

Before you create the connection in Make, you should first obtain your **API Key** in your OneSignal account.

To obtain your **API Key&#x20;**:

::::WorkflowBlock
:::WorkflowBlockItem
Navigate to you&#x72;**&#x20;OneSignal dashboard**.
:::

:::WorkflowBlockItem
Select the desired app from the list of applications.
:::

:::WorkflowBlockItem
Click on th&#x65;**&#x20;Settings tab** in the left sidebar.
:::

:::WorkflowBlockItem
Click o&#x6E;**&#x20;Keys & IDs**.
:::

:::WorkflowBlockItem
Copy th&#x65;**&#x20;App ID** displayed on the screen.
:::

:::WorkflowBlockItem
Copy the API key labeled a&#x73;**&#x20;REST API Key** on the screen.
:::
::::

You will use this value while creating a connection in Make.&#x20;

Because the UI might have changed, the steps you see on your screen might be different, [check the vendor documentation for updates.](https://documentation.onesignal.com/reference)

## Create the connection in Make&#x20;

:::::WorkflowBlock
::::WorkflowBlockItem
[[Log in in your Make](https://www.make.com/en/register) account](https://www.make.com/en/register), add the OneSignal module to your scenario, and click **Create a connection.&#x20;**

:::hint{type="info"}
If you add a module with an instant tag, click **Create a webhook**, then **Create a connection.**
:::
::::

:::WorkflowBlockItem
*Optional:&#x20;*&#x49;n the **Connection name** field, enter a name for the connection.
:::

:::WorkflowBlockItem
Enter the **authentication credentials** you copied from your OneSignal account or follow the on-screen instructions to create the connection.&#x20;
:::
:::::

For detailed information on connecting an application, see **[Connect an application](https://help.make.com/connect-an-application)** page.

# OneSignal modules

After connecting to the OneSignal app, you can choose from a list of available modules to build your scenarios.&#x20;

:::ExpandableHeading
### Add a New Device (Deprecated)

Adds a new device to your account or system.
:::

:::ExpandableHeading
### Add a New Purchase (Deprecated)

Adds a new purchase record to a specific user's profile.
:::

:::ExpandableHeading
### Add a Session (Deprecated)

Creates a new user session in the system.
:::

:::ExpandableHeading
### Export Devices to CSV (Deprecated)

Generates and returns a CSV file containing detailed information about all available devices.
:::

:::ExpandableHeading
### Get a Device (Deprecated)

Retrieves detailed information about a specific device.
:::

:::ExpandableHeading
### List devices (Deprecated)

Retrieves a list of all devices connected to your app.
:::

:::ExpandableHeading
### Make an API call

Executes a custom API request to the connected service using your authorized credentials.
:::

:::ExpandableHeading
### Send a notification

Sends a notification message via email, push notification, or SMS.
:::

# Templates

You can look for more templates in [Make's template gallery](https://www.make.com/en/templates), where you'll find thousands of pre-created scenarios.

# OneSignal resources&#x20;

You can have access to more resources related to this app on the following links

- [OneSignal topics on Make community](https://community.make.com/search?q=OneSignal)
- [OneSignal website](https://onesignal.com/)
- [OneSignal API documentation](https://documentation.onesignal.com/reference)
- [OneSignal page on make](https://www.make.com/en/integrations/onesignal)

***

:::CtaButton{label="Get started for free" externalHref="https://www.make.com/en/register" openInNewTab="true"}

:::

