Manually sending reminder emails can be a time-consuming and error-prone process. One aspect of effective task management is sending timely reminders to ensure important deadlines are met and commitments are fulfilled.
In this tutorial you will learn how to build an application to automatically send reminder emails at the right time and to the right recipients, using BRYTER Connect and Microsoft Power Automate.
Implementation
To implement automatic reminder emails, you are going to build two modules β a parent module which gets a collection of requests and then another child module which is executed for each item in this collection:
-
On the BRYTER platform, create a module and filter a database to get a list of requests for which a reminder email needs to be sent:
-
Create a BRYTER module and name this parent module. Add a Result node and delete the initial Input node.
-
Add a Read From a Database action node and select Filter records.
-
Configure a condition to read records that require an email reminder to be sent. As an example, we introduced a Status field to our database that reflects whether a request is ongoing or completed. Therefore, we filtered to show records where the status = ongoing.
Note that you have read the email addresses as a collection. As a collection can contain up to 500 items, ensure this limit is not exceeded for a given Read From a Database action.
-
-
Publish this module and enable the publishing option Only accessible via API key
-
Send the reminder emails:
In this section, you are going to build a second module which is then executed automatically for each item in the collection. To send the reminder emails for specific records, we will utilize a Batch Process action in this module.
-
Create a new BRYTER module and name it child module. Add a Result node and delete the input node. Click on the START node to add a start parameter. Type ID in the Name field and type id in the API parameter name field.
-
Then, add a Read From a Database action and reference the start parameter ID in the ID field.
-
Add a Send Email action and reference the email address from the Read From a Database action.
-
Publish child module to the Test environment.
-
In the parent module, add a Batch Process action. Select the collection in the dropdown field. In the Select module field, select the child module. In the MAP START PARAMETERS section, map the id from the collection to the start parameters to pass them from the parent module to the child module.
In case you have had the parent module open in another browser tab, you might need to reload the page for the dropdown to be updated.
-
-
In Microsoft Power Automate, create a scheduled cloud flow to regularly trigger a BRYTER module to send the necessary reminders.
-
Add HTTP Request Connector to your MS Power Automate Flow:
-
In the scheduled cloud flow, select Next step, then search for HTTP and select first connector called HTTP.
-
Use the following parameters to complete the configuration:
Method: POST
URI:
https://<tenant>.bryter.io/api/execution/<module-id>/sessions
-
<tenant>
: your tenantβs name -
<module-id>
: It is generated when you publish the module with API access. Please check the module publishing field to find the module ID.
Β Headers:
-
Authorization: Bearer <API KEY>. The API key is generated when you publish the module with API access. Please check the module publishing field to find the module ID.
-
Content-Type: application/json
-
The parameters are environment-specific. So you will need two Power Automate flows, one for Test and Live respectively in the end. -
-
Switch on the Microsoft Power Automate Flow.
If you have any questions, please contact our Technical Success Team at support@bryter.io.