---
sourceDocument: Brazil Build or modify applications
sourceDocumentLink: https://www.servicenow.com/docs/r/application-development

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Notifications

# Notifications {#ariaid-title1}

Release version: Brazil  
Updated September 10, 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 Notifications

ServiceNow Notifications enable applications to communicate effectively with users by sending alerts related to application events, sharing knowledge base information, and supporting multilingual interactions through translations.
Notifications can be delivered via email, SMS, or push notifications using the ServiceNow AI Platform.
Show full answer Show less  

## Notification Triggers

Notifications can be triggered based on either table updates or specific events:

* **Event-driven notifications** are preferred when conditions are complex or when notifications are initiated from workflows. They also facilitate easier debugging.
* Simple notifications can be sent using the Notification activity in workflows or the Send an email action in Flow Designer.
* For critical or complex scenarios, trigger events from workflows or Flow Designer flows and configure notifications to respond to those events.

## Notification Content

Notifications support both static and dynamic content through email templates, scripts, and variables:

* **Notification variables** dynamically insert field values from the base record or related records via dot-walking, eliminating the need for scripting in many cases.
* Use the `URIREF` variable to link directly to the originating record.
* **Scripting** is available for advanced customization, such as setting recipient or sender details, but scripts embedded directly in notification bodies using `<mailscript>` tags may be unreliable. Instead, create email scripts separately and include them via ${mailscript:scriptname}.
* **Email templates** enable reusable content for subject lines and message bodies, improving consistency and efficiency across notifications.

## Configuring Recipients

Notifications can be sent to individual users, groups, or external email addresses:

* When targeting groups, enabling the "Include members" option sends the notification both to the group email and to each member individually.
* **Subscription-based notifications** allow users to select which emails they receive by marking notifications as subscribable. Mandatory notifications override user preferences, ensuring delivery.
* Email unsubscribe links can be added to allow users to opt out of subscription-based notifications.

## Email Watermarks and Troubleshooting

ServiceNow includes email watermarks in notifications by default to track and process user responses accurately. Watermarks can be omitted only when no responses are expected.

For common issues with outbound emails and notifications, refer to the Troubleshooting Outbound Email knowledge base article available via the ServiceNow HI portal.  
After the data model is defined and users are able to interact with the application, determine how the application should communicate with users. Configure notifications to alert users to application-related events, share
information in the knowledge base, and add translations so users can interact with the application in their native language.

The ServiceNow AI Platform can notify users by email, SMS text message, or push notifications.

## Triggers: Event Driven Notifications vs Table Updates {#notifications__section_qns_wqx_txb}

Configure notifications to trigger based on updates to a table or based on an event. Use event-based triggering when triggering requirements cannot be easily implemented in the notification conditions or when the notification is
triggered from a Workflow. Creating specific events also enables easier notification debugging.

Use the Notification activity in a workflow or the Send an email action in Flow Designer for simple notification use cases. For complex or critical notifications, trigger an event from a workflow or a Flow
Designer flow and configure a notification to fire off that event.

## Notification Content {#notifications__notification-content}

ServiceNow notifications support static and dynamic content using email templates, email scripts, and notification variables.

[Notification variables](https://www.servicenow.com/docs/access?context=notification-variables&version=brazil&pubname=brazil-platform-administration&ft:locale=en-US) add dynamic information to the body of a notification, such as field values from the base record. The variables also support dot-walking, which allows field values from any related
records to be included in the content without scripting.

For example, use the URI_REF variable to point to the record that originated the email.

Use [Scripting for email notifications](https://www.servicenow.com/docs/access?context=c_ScriptingForEmailNotifications&version=brazil&pubname=brazil-platform-administration&ft:locale=en-US) or dot-walk from the base record to include dynamic content that is not available in the record. Use the mail script API to set notification details, such as the
recipient and sender addresses, etc.  
Note:  
Scripts entered in the notification body using \<mail_script\> tags may not always work correctly. Always create email scripts at System Notifications \> Email \> Notification Email Script and include them in the notification body with ${mail_script:script_name}.

Create [Email templates](https://www.servicenow.com/docs/access?context=c_EmailTemplates&version=brazil&pubname=brazil-platform-administration&ft:locale=en-US) for content used in multiple notifications. Adding the content to an email template enables administrators to create reusable content for the subject line and message body of email
notifications.

## Configure recipients {#notifications__section_bpq_grx_txb}

ServiceNow emails can be sent to users, groups, or individual email addresses. When sending to groups, check the Include members field on the group record for the notification to be sent to the group email and
all members individually.

[Subscription-based notifications](https://www.servicenow.com/docs/access?context=c_SubscriptionBasedNotifications&version=brazil&pubname=brazil-platform-administration&ft:locale=en-US) - Select the Subscribable option on the notification to allow recipients to pick and choose the emails they want to receive.

For a subscription-based notification, the [Mandatory](https://www.servicenow.com/docs/access?context=t_MakingANotificationMandatory&version=brazil&pubname=brazil-platform-administration&ft:locale=en-US) option can be set to true for the recipients to receive the notification regardless of their individual preferences. Optionally, configure [Email unsubscribe links](https://www.servicenow.com/docs/access?context=email-unsubscribe&version=brazil&pubname=brazil-platform-administration&ft:locale=en-US) in the outgoing email to allow users to remove themselves from the notification.

ServiceNow uses email watermarks to correctly process user responses to notifications. Email notifications automatically include watermarks unless the Omit watermark option is selected in the notification. Omit
watermarks only when no email response is expected from the recipients.

The [Troubleshooting Outbound Email](https://hi.service-now.com/kb_view.do?sysparm_article=KB0521382) knowledge base article provides troubleshooting steps for the most common notification issues. Log in to the HI portal ([https://hi.service-now.com](https://hi.service-now.com/)) to access the article.