---
sourceDocument: Australia ServiceNow AI Platform user interface
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/pt-BR/platform-user-interface

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia ServiceNow AI Platform user interface

ft:clusterId :

    - platux

bundleId :

    - platux

workflow :

    - Platform


---

# Custom notifications in Next Experience

# Create custom notifications in Next Experience {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 min. de leitura

Provide better context and information about users' work by creating custom content for
in-product notifications in Next Experience.

## Antes de Iniciar

Role required: admin

## Por Que e Quando Desempenhar Esta Tarefa

Create notifications with custom title and message content for your applications and use
cases. Next Experience notifications appear as toast banners and in the Notifications
menu.  
Nota:  
Next Experience notifications aren't supported in the legacy Agent Workspace.

## Procedimento

1. Navigate to AllSystem NotificationProviderNotifications.
2. Select New.
3. On the form, fill in the fields.  
   {#create-custom-notifications-next-experience__id_tw3_421_cwb__entry__2}

   | Field | Description |
   |-|-|
   | Name | Name of the notification. |
   | Application | Application scope of the notification. |
   | Active | Option to activate the notification. The notification is active by default. |
   | When to send ||
   | Trigger | System action that triggers the notification. You can send the notification after a record is changed or after an event is triggered. |
   | Inserted | Option to send the notification after a record is inserted. This field appears when you select Record Change in the Trigger field. |
   | Updated | Option to send the notification after a record is updated. This field appears when you select Record Change in the Trigger field. |
   | Event | Event that triggers the notification. For example, to send a notification after an incident is closed or resolved, you would select the incident.inactive event. By default, this event is logged in the system each time a user resolves or closes an incident. Nota: You can select only an event that shares the same table as the notification. This field appears when you select Event in the Trigger field. |
   | Table | Table to receive notifications about. |
   | Conditions | Filter to specify the table records that users receive notifications about. For example, to send notifications about top-priority incidents, you would select Incident \[incident\] in the Table field and set the conditions to \[Priority\] \[is\] \[1 - Critical\]. |
   | Who will receive ||
   | Users | Users who receive the notification. Nota: Notifications in messaging channels are sent only to users with ServiceNow accounts (sys_user profiles). Consumers and customer contacts are considered as guests and can't receive notifications in messaging channels. |
   | Recipients listed in fields | Record fields that include users who receive the notification. For example, to send the notification to the record assignee, select Assigned to. Nota: This field shows up only if you select a table. |
   | Include the person whose action triggered the notification | Option to include the user who changed the record or triggered the event. |
   | Recipient(s) listed in event parm1 | Option to select whether Parm 1 contains a list of comma-separated sys_ids. For more information, see [Classic Events](https://www.servicenow.com/docs/access?context=events&version=australia&pubname=australia-build-workflows&ft:locale=en-US). |
   | Recipient(s) listed in event parm2 | Option to select if Parm 2 contains a list of comma-separated sys_ids |
   | Table containing recipients from event parm1 | Table that is used to resolve the sys_id of the recipient Nota: This field appears only when you select Event parm 1. |
   | Table containing recipients from event parm1 | Table that is used to resolve the sys_id of the recipient Nota: This field appears only when you select Event parm 2. |
   | Advanced event condition | Option to select when the recipients are from more than two tables. These are dynamic conditions. |
   [Tabela 1. Notifications form]

   {#create-custom-notifications-next-experience__id_tw3_421_cwb}
4. From the form context menu, select Save.
5. Select the Contents tab and then select New Provider Content.
6. Select Next Experience as the content provider.
7. On the form, fill in the fields.  
   {#create-custom-notifications-next-experience__table_vyy_21t_gtb__entry__2}

   | Field | Description |
   |-|-|
   | Name | An internal name for the notification content. |
   | Notification | The notification trigger that sends the notification content. |
   | Active | Option for whether the notification is sent when triggered. |
   | Table | Table to receive notifications about. |
   | Route | Next Experience Route |
   | Message Heading | Header text at the top of the message. From the Select variables list, you can select variables to include your message heading. |
   | Message | Secondary text of the message that follows the heading. From the Select variables list, you can select variables to include your message body. |
   [Tabela 2. Notification Next Experience Content form]

   {#create-custom-notifications-next-experience__table_vyy_21t_gtb}  
   The following example shows the values for a notification with custom content that
   references the number and short description of an incident.
   {#create-custom-notifications-next-experience__table_hqt_fdr_vvb__entry__2}

   | Field | Value |
   |-|-|
   | Name | Incident record update content |
   | Notification | Incident records |
   | Active | true |
   | Message Heading | ${number} changed |
   | Message | Short description: ${short_description} |
   [ ]

   {#create-custom-notifications-next-experience__table_hqt_fdr_vvb}
8. Select Submit.
{#create-custom-notifications-next-experience__steps_x5l_z2p_rvb}

## Resultado

When triggered, users configured to receive the notifications see notifications with custom
content as banners and in the Notifications menu in the Next Experience
Unified Navigation.

The UI Notification Inbox \[ui_notification_inbox\] table lists all sent notifications and their
recipients.
If users receive duplicate notifications, verify that the notification trigger has only one
content provider. If the notification has both a Next Experience and Workspace content
provider, remove the Workspace content provider from the notification trigger to send only the
Next Experience notification with custom content.