Connector configuration
Use an Email connector to define the recipients for Notification Center email notifications.
Configuration
| UI label | API field name | Type | Required | Notification source type overrides | Allowed values | Default value | Description |
|---|---|---|---|---|---|---|---|
| Email addresses | emailAddresses | ArrayOfStrings | true | n/a | n/a | n/a | Email addresses that receive notifications |
| Dynamic email addresses | emailAddresses | ArrayOfStrings | false | n/a | n/a | n/a | A template that resolves to the recipients at send time. When set, it overrides Email addresses. |
Send to recipients chosen at send time
Dynamic email addresses takes a template instead of a fixed list, so one connector can reach the team that owns whatever fired. It is set per notification source type, so alerts and Cases can resolve recipients differently.
The template must resolve to a JSON array
The field writes to emailAddresses, which is an array. A template that resolves to a bare string, or to addresses separated by commas, is not a valid value and the notification is not delivered.
Wrap a single value in brackets and quotes:
["{{ alertDef.entityLabels.email }}"]
Pass a list through json_encode rather than printing it, which is what turns a list into a JSON array:
{{ case.labels.email | json_encode() }}
Notes
- Add up to 50 email addresses per connector
- Carbon copy (CC) and blind carbon copy (BCC) are not supported
Example
{
"emailAddresses": [
"sre-oncall@example.com",
"team-leads@example.com"
]
}
Next steps
Configure the subject and content of Email notifications in Message configuration.
Last updated on