Example: Send a weekly report of new issues

In this example, we want to send a weekly Notepad report that contains a list of all newly created support tickets from the previous week. If there were none, we do not want to send a report. We will use the Support Ticket object type, which is a custom object type that we have created for this example.

Condition

We begin in the automation creation wizard by selecting the Object added to set condition. By selecting the Support Ticket object type without additional filters, the automation will trigger when new tickets are created.

Since we only want to send the report once a week, we add a schedule to the condition and specify that the automation should trigger every Monday morning at 8am.

Because we added a weekly schedule to the objects added condition, every Monday the automation will check whether new Support Ticket objects were created in the last week.

Effect

When the condition is met, we want to send an email with an attached PDF report that contains all support tickets that were created in the previous week. To accomplish this, we start by adding a notification effect.

Since the PDF report should be generated for all support tickets that were created in the previous week, keep the default object grouping Send one notification for all Support Tickets added. For the recipients, add a group that contains the intended users. Alternatively, to only notify users who have had new support tickets assigned to them, select only object-property backed users.

Because the information is contained in the attached PDF, we do not need a complex notification body: instead, we can rely on the Plain notification type to configure the content in the UI. We can also provide a link to a Quiver dashboard in the notification.

Attaching a Notepad document to a notification

To set up our notification attachment, we will use a Notepad template to dynamically create a Notepad document and attach a PDF of the Notepad document to our notification.

First, we need to create a Notepad template that can display the desired information. We can follow the steps outlined in the Notepad documentation for this. In our specific case, we create a Notepad template that takes in a Support Ticket object set as template input. Using the template input, we display a chart and render a table with the title and description of each object in the object set.

After saving and publishing our Notepad template, we can use it in our notification effect. First, we select it as attachment and define the template version. Then, we can connect the support tickets template input exposed by the Notepad template with the New Support Tickets condition effect input as shown below.

In this way, the Notepad template will be executed with the new support tickets as input and the resulting Notepad will be attached to the notification as PDF.

Summary

On the summary screen, we can confirm that the automation will send the Notepad template once for all new support tickets every Monday at 8am.