Practice Lab 4 - Create a Power Automate flow

Estimated time: 30 minutes

Lab objectives

In this lab, you will learn to:

  • Navigate the Power Automate maker experience
  • Create an automated cloud flow triggered by a Dataverse event
  • Add conditions and actions to a flow
  • Send an email notification using a built-in connector
  • Test and monitor a flow

Scenario

Contoso wants to automatically notify the facilities team whenever a new high-priority facilities request is submitted. You will create an automated cloud flow that triggers when a new row is added to the Facility Request table and sends an email notification if the priority is High or Urgent.

Exercise 1: Create an automated cloud flow

  1. In a new Browser window, navigate to <Https://make.powerautomate.com> (or select Power Automate from the app launcher) and sign in.
  2. Change the Environment from Contoso (default) to Dev One
  3. Select + Create from the left navigation.

  4. Select Automated cloud flow.

    Create new Flow

  5. Name the flow Notify on High Priority Request.
  6. In the trigger search box, search for “When a row is added” and select When a row is added, modified or deleted (Microsoft Dataverse).

  7. Click Create.

    Screenshot showing trigger configuration

Exercise 2: Configure the flow

[!NOTE] It’s possible that your trigger step will say Invalid Parameters, if that is the case, it means that you need to configure a new connection. If your trigger says Invalid Parameters, follow the steps below:

  1. Select the when a row is added, modified, or deleted trigger.

  2. In the Parameters pane, select Change connection reference.

    Screenshot showing changing the connection

  3. Select Add New.
  4. Configure the connection as follows:
    • Connection name: Dataverse
    • Authentication Type: Oauth

  5. Select the Sign in button.

    screenshot showing signing to Dataverse

  6. Choose the MoD Administrator account.

Once you have configured the connection reference, we can configure the trigger.

  1. In the trigger step, configure the following settings:
    • Change type: Select Added.
    • Table name: Select Facility Requests (the table you created earlier).

    • Scope: Select Organization (to trigger for all users).

      Screenshot showing configuring the Dataverse trigger

  2. In the Copilot Pane on the Right, enter the following command. “Add a condition to see if the Priority is equal to high.”

We only want to send a notification for high-priority requests. Add a condition to check the priority value.

  1. Select the Newley added condition, and configure as follows:
    • In the left box, click in the field and select Priority (from Dynamic content – this comes from the trigger output).
    • Set the operator to is equal to.

    • In the right box, type the value for High (this is typically the numeric value of the choice — you may need to enter the integer value, such as 3, depending on your choice setup). Repeat by adding an Or condition for Urgent.

      Your completed condition should be Priority is equal to High.

      Screenshot showing Check Priority Condition

Now that we have our condition, we are going to configure the Notification email

  1. In the If True/Yes branch of the condition, click Add an action.

  2. Search for “Send an email” and select Send an email (V2) from the Office 365 Outlook connector.

    Screenshot showing configuring Outlook

  3. Select the Mod Administrator account

    NOTE: You may need to select the Sign in button. (You may receive a browser had blocked the connection authentication popup window. If so, select the Popup icon in the address bar and choose Always allow pop-ups and redirects from https://make.powerautomate.com)

  4. Configure the email:
    • To: Enter your own email address (for testing purposes).
    • Subject: Type “High Priority Facility Request: “ and then insert the Request Title dynamic content from the trigger.
    • Body: enter “A new high-priority facilities request has been submitted.”

    • Add dynamic content for Category, Priority, and Description on separate lines.

      Your completed email should resemble the image below:

      Screenshot showing Configured email

  5. Leave the If no branch empty (no action needed for non-high-priority requests).

Exercise 3: Save and test

  1. Click Save in the upper right.
  2. Test the flow:
    • Open your Facility Request table (in make.powerapps.com > Tables or through the model-driven app).
    • Add a new row with Priority set to High.
    • Return to Power Automate and click on the flow run history (under the 28-day run history section) to verify the flow ran successfully.
    • Check your email inbox for the notification.
  3. If the flow did not trigger or failed, click on the run entry to see step-by-step details and identify where the error occurred.