--- sourceDocument: Australia ServiceNow AI Platform Administration sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/platform-administration Release : - australia ft:locale : - en-US ft:publication_title : - Australia ServiceNow AI Platform Administration ft:clusterId : - platadm bundleId : - platadm workflow : - Platform --- # Push notification system # Push notification system {#ariaid-title1} Release version: Australia Updated March 12, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Push Notification System The push notification system within ServiceNow facilitates the delivery and management of push messages for both the ServiceNow Classic mobile application and custom-built applications. Key components include the customer instance, push proxy, push provider, and the mobile push application itself. Show full answer Show less ## Key Features * **Push Proxy:** Acts as an intermediary that collects notifications for the ServiceNow Classic mobile application and forwards them to the respective push notification services (APNs or FCM). * **Push Notification Process:** Notifications are triggered by activities on the instance and sent to the appropriate push service based on user preferences. This includes sending message content and instance details for proper response handling. * **Response Handling:** Users can respond to notifications (e.g., approving requests) through a REST message back to the instance, where a designated script processes the response. * **Custom Applications:** Users can customize their push applications to allow responses to notifications, using scripts associated with each message to define possible actions. ## Key Outcomes By leveraging the push notification system, ServiceNow customers can enhance user engagement and streamline workflows through immediate notifications and actionable responses. This system ensures that notifications are effectively managed and that user actions are accurately processed to maintain operational efficiency. The push notification system involves several key elements that manage the delivery of push messages and push notification responses. Customer instance : Your ServiceNow instance. Push proxy : An instance that collects all push notifications that go to the ServiceNow Classic mobile application and forwards them to the ServiceNow applications for Apple iOS or Android. If you create a custom push application, you do not use the push proxy. Push provider : The provider of push messages, which is the Apple Push Notification service (APNs) or Firebase Cloud Messaging (FCM) service, for the ServiceNow Classic mobile app or custom mobile apps. Push application on a mobile device : The application, such as the ServiceNow Classic mobile application. You can also build and customize your own push application. ## Push notification process The push notification process is as follows: 1. Activity on the instance triggers a push notification. 2. The instance looks for who to send the notification to and checks the user notification preferences to find their push device settings. 3. The instance sends the push notification to the push notification service, either the Apple Push Notification service (APNs) or Firebase Cloud Messaging (FCM) service. If you are using the ServiceNow Classic mobile app, the instance sends the notification through a push proxy instance, which then forwards the notification to the APNs or FCM service. 4. The push notification service sends the notification to the user's push application. When the instance sends the notification to the push notification service, it includes message content along with the instance name and ID. This information ensures that a response to the notification is sent back to the correct instance. If the user can reply to the notification, such as sending an approval to a change request, the response is sent via REST message back to the instance. 5. The instance identifies a script to run to handle the response. 6. The script performs an action on the instance, such as marking a change request approved. If there is invalid JSON or if the script fails, an error response is sent back to the device. {#r_PushMessageArchitecture__ol_j4z_ywt_ls} Figure 1. Push notification system with the ServiceNow Classic mobile app ## Push notification responses {#r_PushMessageArchitecture__section_flz_bzk_pz} With custom push applications, you can have your users act on records in the instance by responding to a push notification. The actions that they can take are defined in a script that you associate with the notification message. The response is sent to the instance in this format: https://{instance_name}/api/now/v1/push/{application Name}/action/{action} The application name is the push application the user is using. The application name must match the application name in the Push Application \[sys_push_application\] table. The action is the Sys ID of the action in the Push Notifications Actions \[sys_push_notif_act_script\] table. **Related concepts** * [Push notification retention](https://servicenow-prod.fluidtopics.net/YyNx6oejuU6pjBcDqD~7xA "You can archive and eventually destroy push notifications that you no longer need or if your Push Notification table is excessively large.") **Related tasks** * [Activate push notifications](https://servicenow-prod.fluidtopics.net/GByFoNQ07CFmgWQIIukjkg "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.") * [Enable push notifications for logged-out users](https://servicenow-prod.fluidtopics.net/k~sC8VAIF40uuzwII0YV4A "Enable push notifications for users when they're logged out to deliver timely critical updates.") * [Requeue failed push notification messages](https://servicenow-prod.fluidtopics.net/32cBbqaQvvwD_9hB4a4rJw "Push notification delivery might fail for various reasons. You can view which messages failed and requeue them to be sent out if necessary.") **Related reference** * [Installed with push notifications](https://servicenow-prod.fluidtopics.net/rFO92cgxfDsmj_dv3hWlUQ#r_InstalledWithPushNotifications "Several types of components are installed with the push notifications plugins.") * [Push notification properties](https://servicenow-prod.fluidtopics.net/W8J0OptKauFAMF3IphzdLQ "Push notifications provides several properties to customize the setup.") * [Push notification setup with the ServiceNow mobile app](https://servicenow-prod.fluidtopics.net/QMZZNtcVZhWguNiq0omnag "The ServiceNow mobile application automatically enables push notifications and configures mobile devices for push notifications when users initially log in to the instance.") * [Push notification setup with a custom push application for ServiceNow mobile apps](https://servicenow-prod.fluidtopics.net/k3v6iHe2oAXzjGLarxMzTg "If you are using your own custom mobile or push application, you must configure your app for use and set up the push contents.")