Trigger, audience and content are separate decisions
Notification
Defines when a message is sent, which users or groups receive it and what the message contains.
Event
A registered named occurrence that notifications, Script Actions and other processes can react to.
Email Script
Reusable server-side logic that produces dynamic content inside an outbound email.
CSA exam clue
Who receives what and when points to a Notification. Decouple a named occurrence points to an Event. Generate complex dynamic email content points to a mail script.
Notification: when, who and what
A notification connects three configuration areas: the trigger, the recipients and the content. Depending on the supported channel, it can react to a record insert/update, a fired event or a notification step in Flow Designer.
Information disclosure risk: ServiceNow notes that recipients are not automatically excluded by record ACLs. Confirm that every selected recipient should receive every field or attachment included in the message.
Event: a reusable named occurrence
The Event Registry lists events the instance recognizes. A custom event should be registered so notifications and Script Actions can select and process it. A Business Rule, flow or script can queue an event with a record and optional parameters.
Example: critical incident escalation
A Business Rule detects a meaningful state transition and queues incident.critical.escalated. One notification emails the incident commander, while a Script Action records additional operational context. The producer does not need to contain both downstream implementations.
Use meaningful names and document the record/table and meaning of parm1 and parm2. Avoid firing the same event repeatedly for unrelated updates.
Email Script: reusable dynamic rendering
Mail scripts add server-side logic to outbound email content. Reference a reusable script from the message or template, then use the available context to print values, query related records or adjust supported message properties.
- Use a template for reusable subject/body structure and branding.
- Use ordinary notification variables for simple field substitution.
- Use a mail script only when content needs logic or related-data processing.
- Use instance properties for environment-specific links rather than hard-coded hostnames.
- Keep queries bounded and avoid leaking fields that recipients should not receive.
Trace the complete delivery flow
- A record change, flow step or script creates the trigger.
- If event-driven, the named event is registered and queued with the correct record and parameters.
- The notification trigger and conditions evaluate true.
- Recipient logic resolves active users with usable addresses and notification preferences.
- The platform renders template variables and any referenced mail scripts.
- An outbound email record is generated and processed by the email delivery configuration.
- The receiving mail system accepts, delays, filters or rejects the message.
Separating these stages prevents random changes to message content when the real failure is an event that never fired or a recipient that never resolved.
Troubleshoot a missing notification
- Confirm the trigger: record operation, changed field, event or Flow Designer step.
- For events: verify registration, event name, table, event log entry, record and parameters.
- Check notification state: active, correct table, trigger, conditions and advanced condition.
- Resolve recipients: user/group fields, active status, email address, preferences and event parameter flags.
- Preview content: template, variables, mail script syntax, event parameters and null references.
- Inspect outbound email: generated state, recipients, subject, body and error details.
- Check delivery configuration: sending enabled, SMTP/provider status, domain authentication and mail-system rejection.
- Test safely: use a controlled non-production record and prevent accidental real-recipient delivery.
ServiceNow CSA practice checks
Several processes should react to one named business occurrence. What provides decoupling?
Best answer: a registered event that notifications or Script Actions can process.
An email needs a formatted list of related requested items. What fits?
Best answer: a reusable mail script referenced by the notification or email template.
Where are message trigger, recipients and content configured together?
Best answer: the notification record.
Frequently asked questions
What is the difference between a ServiceNow event and notification?
An event is a named occurrence recorded for the platform to process. A notification defines when a message is sent, who receives it and what it contains; an event can be one of its triggers.
What is a ServiceNow email script?
A mail script is reusable server-side logic that dynamically changes outbound email content. It can print record information and use the current record, template, outbound email and triggering event context.
Must custom ServiceNow events be registered?
Yes. Register a custom event so notifications, Script Actions and other platform features can recognize and react to it.
Do notification recipients automatically follow record ACLs?
No. ServiceNow warns that email recipient selection is not automatically restricted by record ACLs. Administrators must verify that every recipient is permitted to receive the included information.
Official ServiceNow references
Use current ServiceNow documentation for creating email notifications, the Event Registry, scripting for notifications, email templates and system notification channels. Features vary by release, scope and installed applications.