Power Automate can help take repetitive, predictable tasks off your plate. Once you understand the available actions and the logic for getting and updating data, you can use flows to make Dynamics 365 CRM and the other applications you use every day work together more efficiently. This class walks through several common CRM scenarios to provide a practical look at what Power Automate can do.
Getting started in Power Automate
One way to access Power Automate is at make.powerautomate.com. Before creating a flow, make sure you're working in the correct environment. It's often helpful to start in a sandbox environment so you can create, test, make changes, and test again without working with real production data. When the flow is ready, it can be moved into the production environment. From the Create area, you can choose from several types of cloud flows:
- Automated cloud flow: Runs when an event occurs. In CRM, this can include a record being added, modified, or deleted.
- Instant cloud flow: Runs when someone manually triggers it.
- Scheduled cloud flow: Runs according to a schedule, such as every Monday at 8:00 AM.
Scenario 1: Send an email when an opportunity is closed as won
Imagine you own a growing company and are starting to lose track of when invoices need to be emailed. You want to receive a reminder every time an opportunity is closed as won. This can be handled with an automated cloud flow.
Start with the Dataverse trigger "When a row is added, modified or deleted." Dataverse is Microsoft's database that underlies CRM. For this scenario, configure the trigger to run when an opportunity is modified. The flow also needs to be limited so it runs when an opportunity is closed as won. The example uses the appropriate backend status field and value to identify that condition. It's also helpful to give your triggers and actions descriptive names. Clear labels make it much easier to understand the flow when you return to it later.
Creating a dynamic link to the opportunity
The notification email can include a hyperlink that takes you directly to the opportunity that triggered the flow. Start by opening an opportunity record and looking at its URL. The URL includes a unique identifier, or GUID, for that opportunity. You can build a dynamic hyperlink by:
- Initializing a string variable for the hyperlink.
- Adding the portion of the opportunity URL that remains consistent.
- Using dynamic content to insert the unique identifier of the opportunity that triggered the flow.
Because each opportunity has its own unique identifier, the resulting link can point directly to the appropriate CRM record.
Sending the notification email
The final step is to add an email action. The email can include a subject such as "Send Invoice," a note explaining that the opportunity has been closed as won, and the dynamic hyperlink to the opportunity. After saving the flow, use Flow Checker to identify errors or warnings before testing it. To test the flow manually, perform the action that is supposed to trigger it. In this case, close an opportunity as won. When the flow runs successfully, the email is sent and its link opens the corresponding opportunity record.
Scenario 2: Automatically track the last activity date for leads
The second scenario focuses on helping a sales team monitor communication with open leads. In this example, a custom Last Activity Date field is created. The goal is to update that field automatically whenever an email is sent to a lead, eliminating the need for manual data entry. This begins with another automated cloud flow using Dataverse. The trigger runs when an email activity is added.
Checking whether the email is related to a lead
This flow needs a condition because not every email will be associated with a lead. A condition asks a question that produces a yes/no or true/false result. In this case, the question is essentially: "Is this email regarding a lead?" The Regarding field provides the information needed to answer that question. It is a lookup to the related CRM record and contains information such as the table, record name, and unique identifier. The flow checks whether the table name associated with Regarding equals Leads. If it does, the flow proceeds to update the lead.
Updating the last activity date
Use the Dataverse Update a row action to update the appropriate lead record. The unique identifier from the Regarding lookup identifies which lead needs to be changed. The flow then updates the custom Last Activity Date field with the Created On date from the email. Every CRM table has a Created On field, making that date available to the flow. Once configured, save and test the flow by sending or tracking an email associated with a lead. If the flow runs successfully, the Last Activity Date on that lead is updated automatically. The resulting CRM data can then be exported to Excel when needed for reporting or meetings.
Why clear flow names matter
Flows can become much more complex than these examples, with many triggers, actions, and variables. Renaming each step based on what it actually does makes it easier to understand where data is coming from and what each part of the flow is accomplishing. Instead of leaving a generic action name such as "Update a row," use a descriptive name that communicates its purpose.
Other ways to use Power Automate with CRM
These examples are only a starting point. Other scenarios discussed in the class include:
- Creating on-demand or button flows in CRM.
- Reopening an appointment with a button flow.
- Sending emails containing dynamic customer data.
- Dynamically populating Excel spreadsheets with Dynamics data.
- Bulk updating older records with new information.
- Customizing how SharePoint folders or libraries are created.
- Automating predictable and repetitive data entry.
- Sending internal or external reminders and notification emails.
Using button flows for controlled data changes
Button flows can also support processes where changes need additional oversight. For example, your organization might have strict requirements around changing customer information such as an address. A Power Automate button in CRM can launch a correction request. The user enters what needs to be corrected, and the flow sends the information to someone who has permission to edit the account. This provides a way to incorporate a controlled process around changes to CRM data.
Connecting your business applications
Dynamics 365 is one part of a larger collection of applications used to run a business. Organizations may also rely on Outlook or Exchange for email, SharePoint for file storage, and Excel for data visualization and analysis. Power Automate can help connect these applications when your business process requires additional automation. It can also help when applications outside the Microsoft ecosystem need to connect with Microsoft applications, or when two Microsoft applications don't connect in exactly the way your process requires.
The key is to look for work that is predictable and repetitive. Those processes may be good candidates for a Power Automate flow that reduces manual effort and helps CRM fit more closely with the way your business works.
