---
sourceDocument: Xanadu ServiceNow AI Platform Administration
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/xanadu/platform-administration

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu ServiceNow AI Platform Administration

ft:clusterId :

    - platadm

bundleId :

    - platadm

workflow :

    - Platform


---

# Push notification setup with a custom push application for ServiceNow mobile apps

# Push notification setup with a custom push application for ServiceNow mobile
apps {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

If you are using your own custom mobile or push application, you must configure your
app for use and set up the push contents.
Setting up a push notification infrastructure that uses a custom push app involves a push
admin (also called push app developer or mobile app developer) and system administrator.
When push admins create a customized push app, they also configure the app, its push message
content (payload generators), and optional attributes, such as push action scripts. The
admin creates and updates the push notifications for the custom push app. After users
install the custom push app and initially log in to their instance from their mobile device,
the system automatically creates a device (channel) for the custom app.  
Note:  
These instructions are intended for users who develop their own customized push application. You do not need to configure the ServiceNow mobile push application.

This process describes configuration used in the ServiceNow mobile app. Push Notification configuration for the current ServiceNow mobile UI can be found at [Mobile push
notifications](https://www.servicenow.com/docs/access?context=sg-mobile-push-notifications&version=xanadu&pubname=xanadu-mobile&ft:locale=en-US)  
Figure 1. Push notification setup tasks for a custom push app

## Before you begin {#r_PushNotificationSetupCustom__section_ymt_gz1_sjb}

Complete the steps in [Activate push notifications](https://servicenow-prod.fluidtopics.net/fPbiPvA0orzM4ShlqpnZ4Q "Several plugins must be activated to use push notifications. If you have the Mobile UI (com.glide.ui.m) plugin active, push notification plugins are automatically activated.").

Assign the push_admin role to your organization's mobile app developer.

## What to do --- push admin

Configure push notifications for your custom push app. This process differs for iOS and Android devices.

1. (iOS only) [Upload a push certificate to your instance](https://servicenow-prod.fluidtopics.net/lU0_F2BiLNTXEWj8SZvB8A "Upload a push certificate to your instance so that you can use it later to connect your iOS device to the push notification system.")

   Upload a push
   certificate to your instance so that you can use it later to connect your iOS device to the push notification system.
2. [Create a push application record for your custom app](https://servicenow-prod.fluidtopics.net/Uasca9pJX3foHO5a5gEApw "Register your customized mobile application with your instance to receive push notifications for the application.")

   Register your customized mobile
   application with your instance to receive push notifications for the application. The
   instance uses this push application record to identify the device + push application
   combination necessary to determine a push notification recipient.
3. [Create push message content](https://servicenow-prod.fluidtopics.net/tQgkGu7bKXir9hT62A_u4w "Push message content specifies additional JSON content in the push notification payload that is sent to the push provider.")

   Create a JSON content payload
   for different types of push notifications. The content determines how a push
   notification appears on the push application, and whether the user can send a message in
   response to the push notification. The push admin can create attribute definitions that
   specify a default push action script or string, for use in the push message content.
4. (Optional) [Create a push message attribute definition](https://servicenow-prod.fluidtopics.net/CNPz233RBWtfsmVmw_Z8rw "Push message attribute definitions allow you to create reusable properties for push message content specification.")

   Push message
   attribute definitions allow you to create reusable properties for push message content
   specification.
5. (Optional) [Create an attribute value or action for a push message](https://servicenow-prod.fluidtopics.net/CYoFV1rVr5BlxWYwvAaScQ "Attribute values are associated with push messages to provide a way for the message to include certain types of information in the push notification.")

   You can
   create attribute values that override the default attribute definitions used in the push
   message content.
6. (Optional) [Create a push action](https://servicenow-prod.fluidtopics.net/U~c168y~9EKg~vFmzxuotg "A push action is a server-side script that runs when the instance receives a response to an actionable push message.")

   A push action is a
   server-side script that runs when the instance receives a response to an actionable push
   message.
{#r_PushNotificationSetupCustom__ol_jbv_ggb_sjb}

## What to do --- admin {#r_PushNotificationSetupCustom__section_kqv_bzw_l1b}

Create the push messages and push notifications: The administrator [creates the push
messages](https://servicenow-prod.fluidtopics.net/grGlMpSNla2eMhPKosrNkQ "Before you create a push notification, create the push message with the actual message content for the notification."), [sets up push
notifications](https://servicenow-prod.fluidtopics.net/6y4B~NLX8AxJKuVJdwxJuw "Email administrators can create a notification that specifically sends a push notification.") for the custom push app, and if desired, the content.

## Next steps {#r_PushNotificationSetupCustom__section_uzf_gcd_k1b}

Use the Push Installation API to opt users in to receive push notifications. For more
information, see [Push Installation API](https://www.servicenow.com/docs/access?context=pushinstallation-api&version=xanadu&pubname=xanadu-api-reference&ft:locale=en-US).

