Event Alerting & Escalation: Managing Overdue Events

Scenario

During production, different kinds of events could occur. Each event can have a due date. The purpose of this automation is to check whether there are open events that have passed their due date. If there are, the automation updates the event's severity to P0 and sends a notification to the event owner about the overdue event.

Flow of the automation

Configure automation

Pre-requisites

This automation utilizes a Tulip table connector function to pull records from the table that need modification. The connector is installed on the instance simultaneously with the automation. To ensure the connector functions properly, a few settings must be configured:

Set the authentication

1. Create an API token on the instance that has the necessary permissions to read the Tulip tables. If an API token with the required access already exists, this step can be skipped.

2. Enter the API token details in the connector for authentication.
   

If you want to know more about connectors, check out this link: How to Create a Connector.

Set your server address

Along with the authentication of the connector, the server address must also be configured. Under the connector environment settings, paste the instance URL into the server address field for the environment where you want to use the automation.

Modifying the automation

In the automation, you can modify almost everything to fit your process.

To adjust the automation for a different table

If you want to use the automation with a different table, you need to change the table ID in the List open overdue events from Action table function, which is located under the Connector for Tulip table manipulations connector. Simply update the table ID to the one corresponding to the table from which you wish to retrieve the list.

Once the connector function has been modified, you only need to update the table data in the automation. Under the block configuration, find the appropriate table under the table field.

Modifying severity

We recommend changing the severity to fit you process. Currently in this scenario we use P0 as the highest severity option.

Modifying notification

Currently, the automation sends an email to notify the event owner about the overdue event. You can modify the email's recipient, subject, and body based on your needs.