Email notifications that fire at the wrong time or contain broken variable references create support tickets and confused users. This guide shows you how to test notification logic and preview email content before switching on notifications for real users.
The problem with untested notifications
Most notification problems surface after they're already live — users complaining about spam, missing variables showing as blank fields, or notifications that don't fire when they should. Platform admins inherit notification rules built by different people over years, and a single misconfigured condition can flood inboxes or leave critical updates undelivered. Testing notifications in production means real users become your QA team, and rolling back a bad notification doesn't unsend the emails.
ServiceNow's notification testing approach
ServiceNow provides three ways to test notifications without live sends: Preview Notification shows you the rendered email content with real record data, Email Logs capture notification attempts so you can verify triggers fired, and the notification test tool lets you simulate conditions. The progression is preview first (does the content look right?), then test tool (do conditions trigger correctly?), then Email Logs (are notifications firing when expected?). Email Digests add another layer — they batch notifications to reduce volume, but you need to understand digest timing to test effectively.
Production-ready notification testing
Basic testing catches obvious problems, but production-quality testing covers edge cases: what happens when referenced records are deleted, how do notifications behave with different user roles, and do digest rules work correctly under load? Set up dedicated test data that covers your notification conditions, use Email Logs to monitor notification patterns after go-live, and build runbooks for common notification troubleshooting. The best notification implementations include test cases you can re-run after platform upgrades.
Before you start
- •notification_admin role or admin role
- •Outbound email enabled on the instance (System Properties > Email)
Sourdough: ServiceNow Monitoring and Analytics
A Chrome extension for ServiceNow Admins and Developers with essential tools, analytics, graphs and monitoring features.
Free to install. Pro $5/month after a 14-day no-card trial.
Pro requires the ServiceNow admin role. Upgrade inside the extension.
Step by step
Open the notification record
Navigate to System Notification > Email > Notifications and open the notification you want to test. If you're building a new notification, create it first but don't check the Active box yet — you'll test before activating.
Clone an existing notification as your starting point rather than building from scratch — most notification logic is variations on common patterns.
Preview the email content
Click the Preview Notification button at the top of the notification form. Select a real record that matches your notification's table (the Table field determines which records you can choose from). ServiceNow renders the email using that record's actual data, showing you exactly what recipients will see including resolved variables and conditionals.
Test with records that have empty or unusual field values — blank reference fields and special characters in text fields often break email formatting.
Use the notification test tool
Navigate to System Notification > Email > Test Email Notification. Select your notification, choose or create a record that should trigger it, then click Test. This simulates the full notification process including condition evaluation, but sends the email to your user account instead of the real recipients.
The test tool respects the notification's When to send conditions — if your test record doesn't match the conditions, no email gets sent and you won't see an error.
Check the Email Log
Navigate to System Logs > Email to see all notification attempts. Each log entry shows the notification name, recipient, subject line, and send status. Use this to verify your test notifications actually fired and to debug delivery issues. Filter by Type = 'send' and Notification to find your specific tests.
Email Log entries appear even when outbound email is disabled — the logs show what would have been sent.
Test digest behavior
If your notification uses Email Digests (Advanced tab > Digest type is not 'Never'), create multiple qualifying records within the digest window to verify batching works correctly. Navigate to System Notification > Email > Digest Definitions to see digest schedules, then check Email Logs after the digest should have run.
Digest notifications only send if there are qualifying records when the digest job runs — create test data just before the scheduled digest time.
Verify condition logic with edge cases
Test your notification conditions with records that sit on the boundary of your When to send logic. Create or modify test records to barely meet the conditions, then barely miss them. Use the test tool with each scenario to confirm the notification fires only when expected.
Date/time conditions are especially tricky — test with records created at different times and in different time zones if your instance supports multiple zones.
Best practices
Always test notifications with empty reference fields and null values — most notification failures happen when variables reference missing data.
Use a dedicated test user account with the same roles as your real recipients — notification visibility can depend on user permissions.
Document your test cases and save the test records — you'll need to re-run tests after notification changes and platform upgrades.
Set digest intervals longer than your testing window when developing — short digest windows make it hard to create test data before the job runs.
Monitor Email Logs for the first week after activating any notification — real-world data often triggers edge cases you didn't test.
Test Your Knowledge
Quick 3-question quiz — see how your ServiceNow skills stack up.
A list view on a table with millions of records is slow. Best fix?
Select an answer to continue