Overview
What OneSignal is
OneSignal is a customer communication platform that sends notifications and messages, including email, to users across multiple channels.
Courier sits in front of it as one API, a visual editor, journeys, and every other channel, so you keep OneSignal for delivery and build multi-channel notifications on top.
You need a Courier account and your own OneSignal account with an App ID and REST API Key.
Why Courier
What you get with OneSignal + Courier
Design beautiful emails, no code
Build and edit email in Courier's visual editor. Product and marketing change content and layout without shipping code, then send through OneSignal.
Automate multi-step journeys
Onboarding, drip, and lifecycle sequences with delays and branching, all delivered through OneSignal.
Add SMS, push, and chat
The same notification can reach every channel. Add one when you need it, no new integration in your code.
Add an in-app inbox
A new, easy add-on: drop Courier Inbox into your web or mobile app so users get an in-product notification center alongside email.
Localize a template in seconds
Pick a language and let Courier translate the whole template with AI, then tweak any string. One template, every market.
Send to lists and audiences
Broadcast a one-off or recurring message to an entire list through OneSignal, alongside your transactional email.
Use cases
What teams build with it
Setup
Connect it in minutes
An admin adds OneSignal once on the Integrations page in Courier. Once connected, anyone on your team can design and send email through OneSignal, and add channels whenever they need them.
FAQ
Frequently asked questions
Can I use OneSignal with Courier?
Yes. OneSignal is a push notification service, and Courier supports it as a push provider. You trigger notifications with Courier's Send API and Journeys, and OneSignal delivers them to your users' devices.
Do I still need my own OneSignal account?
Yes. Courier orchestrates but does not deliver push itself, so you keep your OneSignal app, where devices are registered and subscriptions live. Courier sends through that app; without it there is nowhere to route the notification.
What do I need to connect OneSignal to Courier?
Two values from OneSignal: your App ID and REST API Key. You enter both on Courier's OneSignal integration page, and OneSignal's own documentation shows where to find them. That connection lets Courier send through your OneSignal app.
How does Courier know which device to send a OneSignal push to?
Each recipient profile needs either a oneSignalPlayerID (their OneSignal PlayerId) or a oneSignalExternalUserId (their ExternalId) in the message's to object. At least one must be present, or the send fails.
Can I customize the OneSignal push payload from Courier?
Yes. Any field on OneSignal's Create notification endpoint can be set through the providers.onesignal.override.body object, including priority, ttl, and small_icon. This lets you tune delivery behavior beyond Courier's standard push content.
Why do some OneSignal pushes fail in automated workflows?
OneSignal caps push payload size, so batched Automations carrying large data payloads can exceed it and fail. Enable data mapping in Courier to control which data passes to the push channel and stay under the limit.
Is Courier a replacement for OneSignal?
No. OneSignal still delivers every push to your users' devices. Courier adds one API for content design, Journeys, and other channels like email, SMS, and Courier Inbox, so OneSignal becomes one channel in a multichannel stack.
More
