The Zenduty Email Advanced integration lets the user create a unique email address where you can send critical emails to, which will in turn create an incident on Zenduty and escalates to the right team and notifies them based on on-call schedules via email, text messages(SMS), phone calls(Voice), Slack, Microsoft Teams and iOS & Android push notifications, and escalates alerts until the alert is acknowledged or closed. Zenduty provides your support teams with detailed context around the Dynamics case along with playbooks and a complete incident command framework to triage, remediate and resolve incidents with speed.
Email Advanced integration also allows for restrictions on the email sender, Allowing only specific email senders to create an Alert on Zenduty.
You can also use Alert Rules to custom route specific Email alerts to specific users, teams or escalation policies, write suppression rules, auto add notes, responders and incident tasks.
Please note: This integration is currently in beta. Please report any unprocessed alerts to the Zenduty Support team.
To create incidents via Email(Advanced) with Zenduty, complete the following steps:
Getting started On the Zenduty Dashboard
To add a new Email Advanced integration, go to “Teams” on Zenduty and click on the “Manage” button corresponding to the team you want to add the integration to.
Next, go to “Services” and click on the “Manage” button corresponding to the relevant Service.
Go to “Integrations” and then “Add new Integration”. Give it a name and select the application “Email Advanced (Beta)” from the dropdown menu.
Go to “Configure” under your integrations to start with the configuration.
Configuration
To configure the Zenduty Email Advanced integration, follow these steps:
- To start of the configuration of the integration, Type in the Custom Email to which one would send the email to.
- The system will automatically check if the email is valid.
- The system will automatically check if the email is valid.
- Proceed by selecting whether one want to Restrict the alert creation to specific Emails.
- Any email address entered in this list would be allowed to created an alert on Zenduty. (When sending the email to the previously created custom email.)
- You can add any number of email addresses to this list in a comma seperated format.
- Proceed by either enabling Regex for extraction deduplication terms from the Email Subject.
The Entity Id of the Alert is generated from the Email Subject that is sent to the integration.
This Entity Id can be different if the ‘Triggered’ term in the email subject is changed to ‘Resolved’, Hence resulting in 2 seperate Incidents created for the same Alert.
In other words, if a previously triggered alert is marked as resolved, it would create a new incident instead of resolving the existing one.
By adding the appropriate regex terms, you can remove dynamic terms from the email subject line, making it possible to deduplicate alerts.
To help you determine which Regex to use, you can visit Regexr to optimize it for your specific needs.
Proceed by saving the Integration.
- Zenduty Email Advanced integration is now complete.
Respond to Email Advanced Integration (Beta) alerts faster
Looking for a better way to get real-time alerts from Email Advanced Integration (Beta), setup a solid incident escalation and incident response pipeline and minimize response and resolution times for Email Advanced Integration (Beta) incidents?