Configure Onesignal with Novu
Before you can send push notifications via OneSignal from Novu, you need to connect your OneSignal credentials.Step 1: Get your OneSignal credentials
To configure the OneSignal integration, you need an active account that has credentials for APNS, FCM, or both, and have access to two values from OneSignal app’s settings:- App ID
- App API Key
App ID and App API key.
Step 2: Connect Onesignal to Novu
Next, add these keys to your OneSignal integration in the Novu dashboard.Log in to the Novu dashboard
Open the Novu Dashboard.
Paste credentials
In the OneSignal integration form, paste your App ID and App API Key into the corresponding fields.

Using Onesignal with Novu
Once your integration is configured, you can start sending push notifications by registering your subscribers’player_id tokens and triggering a workflow.
Step 1: Add subscriber device token
When you set up the OneSignal SDK in your application, your users are automatically assigned a unique OneSignalplayer_id. This ID is used to target the user for push notifications.
To target a OneSignal user from Novu, you must register their player_id as the deviceToken for their Novu subscriber profile.
You can do this by making an API call to update the subscriber’s credentials.
- Node.js
- Python
- Go
- PHP
- .NET
- Java
- cURL
Step 2: Send a notification
- Node.js
- Python
- Go
- PHP
- .NET
- Java
- cURL
Using overrides to customize notifications
- Node.js
- Python
- Go
- PHP
- .NET
- Java
- cURL
Using external user ID
By default, Novu usesplayer_id to send notifications, but you can select the External ID option in the OneSignal integration settings in Novu. If External ID option is selected, then deviceTokens stored in subscriber credentials for the OneSignal provider, are used as external user IDs.
By default, Novu uses player IDs to send notifications. If your OneSignal integration uses external user IDs, then you can switch this behavior in the OneSignal integration settings in Novu.
Once enabled, the deviceTokens stored in subscriber credentials are treated as external user IDs instead of player IDs.