Power Automate for Beginners: Build a Flow That Emails New Contacts
Introduction
A contact lands in your CRM, but someone still has to send a welcome email. Power Automate can handle that step for you, along with tasks like copying data between apps, routing approvals, and sending reminders. Its visual tools help you build many workflows with little or no code.
This beginner’s guide explains the main Power Automate flow types, the parts that make a flow work, and how to email someone when a contact record is added. You’ll also see how to personalize the message with contact details and format a date.
Watch this practical demonstration to understand how Microsoft Power Automate simplifies workflow automation using triggers, actions, approvals and connections to business applications.
Learn how to automate repetitive tasks, streamline business processes and build smarter solutions with guidance from Sanjay Prakash Pradhan (Microsoft MVP).
How Power Automate reduces repetitive work
Power Automate is a cloud-based automation tool in Microsoft Power Platform. It connects apps and services so they can pass information and perform tasks without someone handling every step. Cloud flows work with online services, while desktop flows can automate actions in desktop apps.
Understand what Power Automate does
A flow is a set of steps that runs when something happens, when a user starts it, or at a set time. For example, a flow can detect a new CRM record and send an email through Outlook. The visual editor helps you build these steps by choosing triggers, actions, and settings.
Power Automate includes connectors for Microsoft services such as Microsoft 365 and Dynamics 365, as well as many third-party apps. Available connectors and features can depend on your license and setup. You can build flows in a browser, but some connections may need an admin to configure them.
See why automation matters in everyday work
Without automation, employees may copy CRM details into another app by hand. A travel request may move through several email replies before a manager approves it. Someone also has to remember to send routine reminders at the right time.
A flow can move data between supported apps, route an approval, or send a scheduled notice. That cuts down on repeated steps and helps work follow the same process each time. People can spend less time on routine tasks and more time on work that needs their attention.
Choose the right Power Automate flow type
Power Automate offers cloud flows, desktop flows, and business process flows. Each type supports a different kind of work, so choose based on what should happen and where it needs to happen.
Use cloud flows to connect online services
Cloud flows run online and connect services through triggers and actions. They can react to events, run when a user starts them, or follow a schedule. For example, a flow might respond to a new email or send a daily summary from a connected service.
Use desktop flows to automate clicks and typing
Desktop flows use robotic process automation to interact with a computer interface. They can click buttons, enter text, and work with Windows apps or websites. For instance, a desktop flow could follow steps to download a file from a website.
Use business process flows to guide a team
Business process flows guide users through a set of stages in a business process. A sales team might use one to follow the same steps as a deal moves toward close. This type helps people see what to do next; it doesn’t replace a cloud flow that performs background tasks.
Pick the trigger and understand a cloud flow’s building blocks
A cloud flow needs a clear starting point and a set of steps to perform. Its trigger defines when it starts, while actions do the work. Connectors link those steps to the services and apps involved.
Start automatically, on demand, or on a schedule
An automated cloud flow starts when an event occurs, such as receiving an email or adding a record. An instant flow starts when a user runs it on demand. A scheduled flow runs at a chosen time or interval, such as sending a summary email every day at 9:00 a.m.
Use triggers to define when a flow runs
A trigger is the event that starts a flow. For example, you might use a trigger for a new email or for a row added to a Dataverse table. Choosing the right event helps prevent the flow from running at the wrong time.
Use actions, connectors, and dynamic content to do the work
Actions are the tasks a flow performs after it starts. They can send an email, create a record, or update one. A connector links the flow to a service, such as Outlook or Dataverse, and provides the available triggers and actions.
Dynamic content passes information from one step to another. In an email action, for example, you can insert a contact’s name from the trigger rather than typing a fixed greeting. This lets one flow create a message that fits each new record.
Build a Power Automate flow that emails someone when a contact is created
This example uses a Dataverse contact record as the trigger and an Outlook action to send the email. Before building it, make sure you can access the right environment and that the needed connections are set up. The exact options you see may depend on your account and permissions.
Create an automated cloud flow and choose its trigger
In Power Automate, create an automated cloud flow and give it a clear name, such as “Email on new contact.” Search for the Microsoft Dataverse connector, then choose its row trigger. Set the change type to “Added” and select the Contact table.
The trigger’s event and table determine when the flow starts. If the flow should respond to records across the organization, set the scope to Organization where that option is available. Save the trigger settings before adding the next step.
Add an Outlook action and personalize the email
Add an Outlook action to send an email. Set the recipient, subject, and body; for a welcome message, you might use the new contact’s email address as the recipient. Check that the contact record includes a valid email before testing.
To personalize the greeting, insert the contact’s Full Name from the dynamic content list. You could write, “Hello,” followed by the name, then add a short note about the new record. The value comes from the trigger, so the same flow can address each contact correctly.
Save, test, and check the run
Save the flow, then create a test contact with the required fields. Once the record is saved, the trigger should start the flow. Check the flow’s run history to see whether each step succeeded or needs attention.
If the run succeeds, check the inbox for the email and confirm that the name appears as expected. If the flow fails, review the run details for missing data, connection issues, or a trigger setting that doesn’t match the test record. Fix the cause, then test again.
Make your Power Automate flow easier to trust
A flow is easier to maintain when it has a clear purpose and uses reliable data. Check its settings before you depend on it for routine work. Small tests can catch common problems early.
Format dates with expressions
Expressions can change data before a flow uses it. For example, formatDateTime() can format the contact’s Created On value so the email shows a readable date. In the expression editor, use the Created On value from dynamic content and choose a date format that suits the message.
Check connections, permissions, and flow settings
Confirm that each connector is signed in and has permission to access the needed app or data. Check that required fields, such as the recipient’s email address, are present. For Dataverse, also verify that the trigger’s table and scope match the records you want to monitor.
Keep the first flow focused and test it with sample records
Start with one trigger and a small number of actions. Test with sample records that include the fields your flow needs, then review run history after each test. Add conditions, loops, or variables only when the task calls for them.
Conclusion
Power Automate can take repeated steps out of everyday work. Choose a flow type that fits the task, set a clear trigger, and add actions through the right connectors. Dynamic content and expressions help tailor the result.
Start with a familiar task, such as emailing a contact when a Dataverse record is added. Test the flow with sample data, check its run history, and expand it only when the first version works as expected.
