| \n\nName\n\n | \n\nType\n\n | \n\nDescription\n\n |
|---|---|---|
| \n\ntable\n\n | \n\nReference or String\n\n | \n\nRequired. The variable identifier or name of a table to which the notification applies. To define a table, use the [Table API - ServiceNow Fluent](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/servicenow-sdk/table-api-now-ts.md).**Note:** Don’t select the Task \\[task\\] table, which is for extending other tables. Notifications that run on the Task table directly aren’t supported.\n\n |
| \n\ntriggerConditions\n\n | \n\nObject\n\n | \n\nRequired. The conditions that trigger the notification. For more information, see [triggerConditions object](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/servicenow-sdk/fluent-email-notification-api.md).\n\n |
| \n\nname\n\n | \n\nString\n\n | \n\nA unique name for the email notification.\n\n |
| \n\ndescription\n\n | \n\nString\n\n | \n\nA description of the purpose of the email notification.\n\n |
| \n\ncategory\n\n | \n\nReference or String\n\n | \n\nThe variable identifier or name of a notification category for grouping notifications. To define a notification category, use the [Record API - ServiceNow Fluent](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/servicenow-sdk/record-api-now-ts.md).Default: The default email category \\(c97d83137f4432005f58108c3ffa917a\\)\n\n |
| \n\nnotificationType\n\n | \n\nString\n\n | \n\nThe type of notification.Valid values:\n\n- email: A standard email.\n- vcalendar: A meeting invitation. Meeting invitations aren't supported with email digests.\n\nDefault: email\n\n |
| \n\nactive\n\n | \n\nBoolean\n\n | \n\nFlag that indicates whether the notification is active.Default: true\n\n |
| \n\nmandatory\n\n | \n\nBoolean\n\n | \n\nFlag that indicates whether the notification is required.Default: false\n\n |
| \n\nenableDynamicTranslation\n\n | \n\nBoolean\n\n | \n\nFlag that indicates whether to enable dynamic translation for the notification.Default: false\n\n |
| \n\nemailContent\n\n | \n\nObject\n\n | \n\nThe email content and formatting. For more information, see [emailContent object](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/servicenow-sdk/fluent-email-notification-api.md).\n\n |
| \n\nrecipientDetails\n\n | \n\nObject\n\n | \n\nThe email recipients. For more information, see [recipientDetails object](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/servicenow-sdk/fluent-email-notification-api.md).\n\n |
| \n\ndigest\n\n | \n\nObject\n\n | \n\nThe email digest content and formatting. For more information, see [digest object](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/servicenow-sdk/fluent-email-notification-api.md).\n\n |
| \n\n$meta\n\n | \n\nObject\n\n | \n\nMetadata for the application metadata.With the installMethod property, you can map the application metadata to an output directory that loads only in specific circumstances.\n\n```javascript\n$meta: {\n installMethod: 'String'\n}\n```\n\nValid values for installMethod:\n\n- demo: Outputs the application metadata to the `metadata/unload.demo` directory to be installed with the application when the **Load demo data** option is selected.\n- first install: Outputs the application metadata to the `metadata/unload` directory to be installed only the first time an application is installed on an instance.\n\n |
An incident has been escalated.
'\n }\n})\n```\n\n## triggerConditions object\n\nConfigure the conditions that must be met for the notification to be sent.\n\n**Note:** If the same trigger generates multiple notifications, the system sends only one notification. The system considers all other notifications, even if they have a different subject and body, as duplicates. The Ignore Duplicates business rule controls this functionality.\n\n| \n\nName\n\n | \n\nType\n\n | \n\nDescription\n\n |
|---|---|---|
| \n\ngenerationType\n\n | \n\nString\n\n | \n\nRequired. The method of triggering the email notification.Valid values:\n\n- engine: Sends the notification when a record is inserted or updated.\n- event: Sends the notification when custom events occur.\n- triggered: Manually triggered notifications. The following properties don't apply if this property is set to `triggered`.\n\n |
| \n\nonRecordInsert\n\n | \n\nBoolean\n\n | \n\nFlag that indicates whether to send the notification when a record is inserted. **Note:** Either this property or the onRecordUpdate property must be true.\n\nDefault: false\n\n |
| \n\nonRecordUpdate\n\n | \n\nBoolean\n\n | \n\nFlag that indicates whether to send the notification when a record is updated.**Note:** Either this property or the onRecordInsert property must be true.\n\nDefault: false\n\n |
| \n\neventName\n\n | \n\nString\n\n | \n\nThe name of a custom event to trigger sending the notification.This property is required if the value of the generationType property is `event`.\n\n |
| \n\naffectedFieldOnEvent\n\n | \n\nString\n\n | \n\nThe event parameter that contains the affected field.This property applies only if the generationType property is set to `event`.\n\nValid values:\n\n- parm1\n- parm2\n\n |
| \n\nweight\n\n | \n\nNumber\n\n | \n\nThe notification priority relative to duplicate notifications.Notifications that have the same target table and recipients are considered duplicates if the weights are different. If weights are same, an additional evaluation is done to check if the subject and the body \\(excluding watermark\\) are the same to qualify as duplicate notification. When there are duplicate notifications, the system only sends the notification with the highest weight. All other notifications are moved from the Outbox to the Skipped mailbox. The default value of 0 causes the system to send the notification \\(assuming the conditions are met\\).\n\nMaximum value: 1000\n\nDefault: 0\n\n |
| \n\ncondition\n\n | \n\nString\n\n | \n\nA filter query that specifies the fields and values that must be true for users to access the object. For more information, see [Operators available for filters and queries](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/r_OpAvailableFiltersQueries.md).\n\n |
| \n\nadvancedCondition\n\n | \n\nString\n\n | \n\nA JavaScript conditional statement that must return true or set a global answer variable to true to send the notification. For more information, see [Advanced conditions for email notifications](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/c_OptSpecifyingAdvancedCond.md).**Note:** This property is evaluated in addition to other conditions that you set on the notification. Both the condition and advanced condition must evaluate to true to send the notification.\n\n |
| \n\nitemTable\n\n | \n\nReference or String\n\n | \n\nThe variable identifier or name of the table to which the notification item refers. To define a table, use the [Table API - ServiceNow Fluent](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/servicenow-sdk/table-api-now-ts.md).\n\n |
| \n\nitem\n\n | \n\nString\n\n | \n\nThe item to use for the notification context.\n\n |
| \n\norder\n\n | \n\nNumber\n\n | \n\nThe execution order of the notification.Maximum value: 9999\n\nDefault: 100\n\n |
| \n\nName\n\n | \n\nType\n\n | \n\nDescription\n\n |
|---|---|---|
| \n\ncontentType\n\n | \n\nString\n\n | \n\nThe type of email content. Valid values:\n\n- text/html\n- text/plain\n- multipart/mixed\n\nDefault: text/html\n\n |
| \n\ntemplate\n\n | \n\nReference or String\n\n | \n\nThe variable identifier or sys\\_id of an email template \\[sysevent\\_email\\_template\\]. To define an email template, use the [Record API - ServiceNow Fluent](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/servicenow-sdk/record-api-now-ts.md).You can only specify an email template that meets one of the following conditions:\n\n- The template has the same scope and table as the notification.\n- The template has the same scope but has no specified table.\n- The template has the same table and is in the global scope.\n\n |
| \n\nstyle\n\n | \n\nReference or String\n\n | \n\nThe variable identifier or sys\\_id of an email style \\[sys\\_email\\_style\\]. To define an email style, use the [Record API - ServiceNow Fluent](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/servicenow-sdk/record-api-now-ts.md).\n\n |
| \n\nsubject\n\n | \n\nString\n\n | \n\nA subject line for the email. If empty, the system uses the Subject value from the email template.You can use the `\\${variable}` format for variable references. Variables map to column names available from the notification table, its parent tables, and reference tables. Use variables to include values from a record in the table, such as the short description or comments and work notes.\n\n |
| \n\nsmsAlternate\n\n | \n\nString\n\n | \n\nA notification message to send specifically to SMS devices. The SMS alternate message is limited to 140 characters. If empty, the system uses the SMS alternate value from the email template.You can use the `\\${variable}` format for variable references. Variables map to column names available from the notification table, its parent tables, and reference tables. Use variables to include values from a record in the table, such as the short description or comments and work notes.\n\n |
| \n\nimportance\n\n | \n\nString\n\n | \n\nThe level of importance of the message. Valid values:\n\n- low\n- high\n\n |
| \n\nincludeAttachments\n\n | \n\nBoolean\n\n | \n\nFlag that indicates whether to include attachments from the notification trigger record with the email.Default: false\n\n |
| \n\nomitWatermark\n\n | \n\nBoolean\n\n | \n\nFlag that indicates whether to omit the watermark attached to each email. For more information, see [Watermarks on notification emails](https://www.servicenow.com/docs/r/7LhbZn3yz3Q58qhjZoU9iQ/kTwHRtaHawJF_Sz_AA_tnA).Default: false\n\n |
| \n\nfrom\n\n | \n\nString\n\n | \n\nThe email address from which to send the notification.\n\n |
| \n\nreplyTo\n\n | \n\nString\n\n | \n\nThe email address to which recipients can reply.\n\n |
| \n\npushMessageOnly\n\n | \n\nBoolean\n\n | \n\nFlag that indicates whether to send the notification only as a push notification to a mobile device.Default: false\n\n |
| \n\npushMessageList\n\n | \n\nArray\n\n | \n\nA list of variable identifiers or sys\\_ids of push messages \\[sys\\_push\\_notif\\_msg\\] to associate with the notification. To define a push notification, use the [Record API - ServiceNow Fluent](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/servicenow-sdk/record-api-now-ts.md).**Note:** The push message and notification must be for the same table.\n\n |
| \n\nforceDelivery\n\n | \n\nBoolean\n\n | \n\nFlag that indicates whether to bypass user notification preferences that would prevent a notification and send the notification anyway.Default: false\n\n |
| \n\nmessageHtml\n\n | \n\nString\n\n | \n\nThe HTML content of the notification message. If empty, the system uses the message HTML from the email template.You can use the `\\${variable}` format for variable references. Variables map to column names available from the notification table, its parent tables, and reference tables. Use variables to include values from a record in the table, such as the short description or comments and work notes.\n\nThis property is required if the value of the contentType property is `text/html` or `multipart/mixed`.\n\n |
| \n\nmessageText\n\n | \n\nString\n\n | \n\nThe plain text content of the notification message. If empty, the system uses the message text from the email template.You can use the `\\${variable}` format for variable references. Variables map to column names available from the notification table, its parent tables, and reference tables. Use variables to include values from a record in the table, such as the short description or comments and work notes.\n\nThis property is required if the value of the contentType property is `text/plain` or `multipart/mixed`.\n\n |
| \n\nmessage\n\n | \n\nString\n\n | \n\nDeprecated. Message contents.\n\n |
Incident: \\${number}
\nPriority: \\${priority}
\nDescription: \\${short_description}
\nAssigned To: \\${assigned_to.name}
\nCreated: \\${sys_created_on}
\n \n| \n\nName\n\n | \n\nType\n\n | \n\nDescription\n\n |
|---|---|---|
| \n\nallow\n\n | \n\nBoolean\n\n | \n\nFlag that indicates whether users to receive this notification as a digest. If false, all other properties of the digest object are ignored.Default: false\n\n |
| \n\ndefault\n\n | \n\nBoolean\n\n | \n\nFlag that indicates whether digest mode is enabled by default for this notification.Default: false\n\n |
| \n\ntype\n\n | \n\nString\n\n | \n\nThe type of digest. Valid values:\n\n- single: Sends the notification in an email digest when it’s triggered multiple times during the selected interval for a single target record, for example INC001 only.\n- multiple: Sends the notification in an email digest when it’s triggered multiple times during the selected interval for a multiple target record, for example INC001, INC002, and more.\n\n |
| \n\ndefaultInterval\n\n | \n\nReference or String\n\n | \n\nThe variable identifier or sys\\_id of a digest interval \\[sys\\_email\\_digest\\_interval\\] to use as the default time interval for digest delivery. To define a digest interval, use the [Record API - ServiceNow Fluent](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/servicenow-sdk/record-api-now-ts.md).\n\n |
| \n\nsubject\n\n | \n\nString\n\n | \n\nA subject line for the email digest. If empty, the system uses the Subject value from the email template.You can use the `\\${variable}` format for variable references. Variables map to column names available from the notification table, its parent tables, and reference tables. Use variables to include values from a record in the table, such as the short description or comments and work notes.\n\n |
| \n\nhtml\n\n | \n\nString\n\n | \n\nThe HTML content of the email digest. You can use the `\\${variable}` format for variable references. Variables map to column names available from the notification table, its parent tables, and reference tables. Use variables to include values from a record in the table, such as the short description or comments and work notes.\n\n |
| \n\ntext\n\n | \n\nString\n\n | \n\nThe plain text content of the email digest. You can use the `\\${variable}` format for variable references. Variables map to column names available from the notification table, its parent tables, and reference tables. Use variables to include values from a record in the table, such as the short description or comments and work notes.\n\n |
| \n\ntemplate\n\n | \n\nString\n\n | \n\nThe variable identifier or sys\\_id of an email template \\[sysevent\\_email\\_template\\]. To define an email template, use the [Record API - ServiceNow Fluent](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/servicenow-sdk/record-api-now-ts.md).\n\n |
| \n\nseparatorHtml\n\n | \n\nString\n\n | \n\nAn HTML separator that appears between each item summarized in the digest.You can use the `\\${variable}` format for variable references. Variables map to column names available from the notification table, its parent tables, and reference tables. Use variables to include values from a record in the table, such as the short description or comments and work notes.\n\nDefault: ` \\n \\n `\n\n |
| \n\nseparatorText\n\n | \n\nString\n\n | \n\nA plain text separator that appears between each item summarized in the digest.You can use the `\\${variable}` format for variable references. Variables map to column names available from the notification table, its parent tables, and reference tables. Use variables to include values from a record in the table, such as the short description or comments and work notes.\n\nDefault: `--------------------------------------------------------------------------------\\n`\n\n |
| \n\nfrom\n\n | \n\nString\n\n | \n\nThe email address from which to send the notification.\n\n |
| \n\nreplyTo\n\n | \n\nString\n\n | \n\nThe email address to which recipients can reply.\n\n |
| \n\nName\n\n | \n\nType\n\n | \n\nDescription\n\n |
|---|---|---|
| \n\nrecipientUsers\n\n | \n\nArray\n\n | \n\nA list of variable identifiers or sys\\_ids of users \\[sys\\_user\\] or a list of email addresses to receive the notification. To define a user, use the [Record API - ServiceNow Fluent](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/servicenow-sdk/record-api-now-ts.md).\n\n |
| \n\nrecipientFields\n\n | \n\nArray\n\n | \n\nA list of fields that reference the users or user groups to receive the notification. The fields must be reference fields.For example, if a notification uses the Incident \\[incident\\] table, you can specify the `opened_by` field to send the notification to users or groups who opened the incident. This list of users or groups is variable and depends on the values of the associated task record. You can also select a field that includes an email address string to send a notification to that address.\n\n |
| \n\nrecipientGroups\n\n | \n\nArray\n\n | \n\nA list of variable identifiers or sys\\_ids of user groups \\[sys\\_user\\_group\\] to receive the notification. To define a user group, use the [Record API - ServiceNow Fluent](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/servicenow-sdk/record-api-now-ts.md).**Note:** Group members receive individual notifications only if **Include members** is selected in the group record.\n\n |
| \n\nexcludeDelegates\n\n | \n\nBoolean\n\n | \n\nFlag that indicates whether to exclude delegated users. Set this property to true to help prevent the instance from sending email notifications to delegates of the users and members of the groups you selected.Default: false\n\n |
| \n\nisSubscribableByAllUsers\n\n | \n\nBoolean\n\n | \n\nFlag that indicates whether to allow all users to subscribe to the notification. For more information, see [Subscription-based notifications](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/c_SubscriptionBasedNotifications.md).**Note:** If the record contains sensitive or protected data, consider restricting the recipient list only to those users and groups who normally have access to it, leaving the value of this property as false. You can also configure your notification content so that private or sensitive data isn’t exposed. For example, you could insert a link back to the associated record, so that details aren’t revealed in the notification.\n\nDefault: false\n\n |
| \n\nsendToCreator\n\n | \n\nBoolean\n\n | \n\nFlag that indicates whether to send the notification to the person who performed the action that started the notification process, if the person is also a recipient. If the event creator isn’t specified in one of the recipient fields, the event creator doesn’t receive a notification regardless of the setting in this field.Default: false\n\n |
| \n\neventParm1WithRecipient\n\n | \n\nBoolean\n\n | \n\nFlag that indicates whether the event parameter 1 contains one or more notification recipients.This property only applies to event-based notifications.\n\n |
| \n\neventParm2WithRecipient\n\n | \n\nBoolean\n\n | \n\nFlag that indicates whether the event parameter 2 contains one or more notification recipients.This property only applies to event-based notifications.\n\n |