Newsletter approval with Power Automate (Flow)
This tutorial shows several examples of how you can use JungleMail for Office 365 together with Power Automate (previously Microsoft Flow) to automate the newsletter approval process.
Configuration
1. Configure the Power Automate integration with JungleMail for Office 365 outlined here.
Note
If you are using the JungleMail for Office 365 app installed from AppSource, you can skip Step 1 as the JungleMail 365 Connector is available in Power Automate.
If you have added JungleMail for Office 365 app via SharePoint App Catalog, you should create and use the Custom Connector described in Step 1.
2. Create an approval flow (see examples below).
3. In JungleMail for Office 365, go to Settings > Other and select the Flow & Automation tab.
4. Under Newsletter Approval, check the Enable newsletter approval box. Then, select the correct flow trigger (see examples below).
Example 1: standard approval flow
This flow is triggered whenever a newsletter is submitted in JungleMail for Office 365. Flow outcome is determined by the first person who responds to the approval request. If the newsletter is rejected, a notification email is sent to the person who submitted it.
Flow structure:
1. Create a new Automated cloud flow, then add the When newsletter is submitted trigger. The trigger title is also used in JungleMail for Office 365 settings to run the flow.
2. Add the Get newsletter details action. It requires a newsletter ID, select it from the Dynamic content tab.
3. Add the Start and wait for an approval action. Provide the approval type, title (displayed in the approval request email), and the emails of people responsible for approval. Optionally, you may add the Preview URL tag to show the link to newsletter content in the approval request email.
4. Add a condition for the actions following newsletter approval or rejection. Select Response from the Dynamic content tab.
For the "Yes" scenario, add the Newsletter approval secret tag which will automatically approve and send the newsletter.
For the "No" scenario, use the same tag. Optionally, add the Responses Comments tag if you want to see the assigned person's comment on the rejected newsletter report in JungleMail for Office 365. You may also configure an automatic email to yourself, notifying that your newsletter has been rejected.
Example 2: recurrent newsletter approval flow
This flow is triggered whenever a newsletter is submitted in JungleMail for Office 365. However, it is configured to only require approval if the newsletter is recurrent.
Flow structure:
1. Create a new Automated cloud flow, then add the When newsletter is submitted trigger. The trigger title is also used in JungleMail for Office 365 settings to run the flow.
2. Add the Get newsletter details action and use the Newsletter id tag from the Dynamic content tab.
3. Add a condition and use the Is recurrent tag to check if the newsletter is recurrent using the Is recurrent tag from the Dynamic content tab.
For the "No" scenario for the condition, add the Approve newsletter action with the Newsletter approval secret tag which will automatically approve and send the newsletter because it is not recurrent.
For the "Yes" scenario, add the Start and wait for an approval action. Add the approval type, title, and emails of the people authorized to approve the newsletter.
4. Add another condition to check if the newsletter was approved (Condition 2 in the image above), using the Outcome tag. For the "Yes" scenario, add the Approve newsletter action, and for "No, add the Reject newsletter action.
Example 3: approval flow based on recipient amount
This flow is triggered whenever a newsletter is submitted in JungleMail for Office 365. However, it is configured to only require approval if the newsletter has more than 100 recipients. Flow outcome is determined by the first person who responds to the approval request.
Flow structure:
1. Create a new Automated flow, then add the When newsletter is submitted trigger. The trigger title is also used in JungleMail for Office 365 settings to run the flow.
2. Add the Get newsletter details action and use the Newsletter id tag.
3. Add a condition and use the Total recipients tag to check if the recipient number is greater than 100.
For the "No" scenario, add the Newsletter approval secret tag which will automatically approve and send the newsletter.
For the "Yes" scenario, add the Start and wait for an approval action. Add the approval type, title, and emails of the people authorized to approve the newsletter.
4. Add another condition to check if the newsletter was approved, using the Outcome tag. For the "Yes" scenario, add the Approve newsletter action, and for "No", add the Reject newsletter action.