Skip to main content
The Push Notifications channel lets Sagepilot send browser and mobile notifications through Web Push, Firebase Cloud Messaging, and Apple Push Notification service. Use it for journey steps, app-owned notification flows, and re-engagement messages.

​
Before you start

  • Decide which platforms you need: Web Push, Android, iOS, or a combination.
  • For Web Push, prepare VAPID public key, VAPID private key, and contact email.
  • For Android, prepare a Firebase service account JSON file.
  • For iOS, prepare APNs team ID, key ID, bundle ID, private key, and sandbox setting.
  • Make sure your app or website can capture and store push tokens for customers.
Image placeholder: add a screenshot of the Push Notifications card in the Create Channel modal.

​
Create the push channel

1

Open Channels

In Sagepilot, open Channels and click Create Channel.
2

Select Push Notifications

Choose Push Notifications from the Voice & Mobile category.
3

Set general details

Add the channel name and enable the provider types you plan to use.
4

Configure Web Push

Add VAPID public key, VAPID private key, and contact email.
5

Configure Android

Upload or paste the Firebase service account JSON. Sagepilot reads the Firebase project details from the JSON.
6

Configure iOS

Add APNs team ID, key ID, bundle ID, private key, and choose production or sandbox mode.
7

Save and test

Save the channel, then use Test Send with a valid device token or FCM registration token.
Image placeholder: add screenshots for General, Web Push, Android, iOS, and Test Send tabs.

​
Platform checklist

​
Verify the setup

  1. Save the channel with the platform provider enabled.
  2. Register a push token from your app or website.
  3. Send a test notification from Sagepilot.
  4. Confirm the device receives the notification.
  5. Confirm failure states are visible if the token is invalid or expired.

​
Operational notes

  • Do not mix sandbox and production APNs credentials.
  • Store customer push tokens through your app integration before relying on journeys.
  • Rotate provider credentials according to your mobile security policy.