First Flow in 15 Minutes (Current Interface)

Anyone who wants to build their first own flow in Power Automate signs in with a Microsoft account at make.powerautomate.com, selects "Create" in the left-hand menu, and then sets up a trigger and an action within a few minutes, for example an automatic email on a schedule or when a new file arrives. The interface has changed: the start page now has a Copilot field that suggests a suitable trigger together with actions from a description in plain language; anyone who prefers the classic approach still builds the flow manually using search fields for triggers and actions. This guide walks step by step from sign-in to the first saved and tested flow. As of: July 2026.

Signing in and understanding the start area

Getting started happens via make.powerautomate.com, there you sign in with a business Microsoft account; a private Microsoft account is only sufficient for a limited scope of functions. In the left navigation area you will find the items "Home", "Create" and "My flows", through which all further steps run. For the first flow, the basic functionality included in most Microsoft 365 business plans is usually sufficient; as soon as you want to connect premium connectors or your own data sources, an additional license is often required.

Creating a new flow: with Copilot or from scratch

There are two ways to get started. In the first way, you describe in the "Create automation with Copilot" field on the start page, in your own words, what should happen, for example an email once a month to a fixed address. Copilot then suggests a trigger and one or more actions; with "Keep and continue" you accept the suggestion, check the connections for a green checkmark, and select "Create flow". In the second way, you select "Create" and, under "Start from blank", the appropriate flow type: an automated cloud flow starts through an event such as a new email, a scheduled cloud flow runs on a schedule, an instant cloud flow is triggered manually by a click or button. After naming it, you select the specific trigger from a search list.

Configuring trigger and action in the designer

In the designer you initially see only the trigger; you add an action via the plus sign below it. In the "Add an action" search field, you type in, for example, "Send an email" and select "Send an email (V2)" under Microsoft 365 Outlook. In the expanding configuration area you enter recipient, subject and text; via the lightning icon you insert dynamic content from the trigger, such as the name of a file or the sender of an email, so that the text is automatically filled with real values. This combination of search field, configuration area and dynamic content recurs in practically every flow, regardless of which application is involved in the trigger or the action.

Saving, testing and evaluating the flow

Using the "Save" button in the top right, you save the flow; a green message confirms the save. To test it, select "Test" in the toolbar, then the option "Manually" and then "Test flow". If the test runs successfully, a green checkmark appears; with "Done" you close the test run. After that it is worth looking at the run history: via "My flows" you open the new flow and see in the area with the 28-day run history whether individual runs succeeded or failed, including the inputs and outputs of each step. If a run fails, it usually helps to look at the red error message directly at the affected step. A detailed version with an example newsletter flow is also offered by the official Microsoft tutorial.

Anyone who wants to use this first flow as a starting point for larger processes will find that Power Automate consulting from NordFlux offers support for setup and operation, without you giving up control over your own data.

Frequently asked questions about the first flow in Power Automate

Do I need a paid license for the first flow?

No, for a simple automated or scheduled flow with standard connectors such as Outlook or SharePoint, the basic functionality included in many Microsoft 365 Business and Enterprise plans is usually sufficient. As soon as you need premium connectors, your own databases or higher execution limits, a separate Power Automate license becomes necessary; a short licensing consultation clarifies in advance which plan fits your project.

What is the difference between an automated, scheduled and instant cloud flow?

An automated cloud flow starts as soon as a defined event occurs, such as a new file or email. A scheduled cloud flow runs on a fixed schedule, for example once a month. An instant cloud flow is triggered manually, for example by a click in the mobile app or as an action in a Power App. You select all three types when creating a flow under "Create" and "Start from blank".

Do I have to use Copilot to build a flow?

No, Copilot is an option, not a requirement. Via the "Without Copilot" tab you continue to build every flow the classic way, using search fields for triggers and actions; the result is technically identical, only the path there differs.

Why does my test run fail?

The most common cause is a connection that has not yet been authorized, recognizable by a red exclamation mark instead of a green checkmark next to the respective app. Other typical reasons are missing permissions for a mailbox or a library, as well as empty required fields in an action. The run history shows the exact error message for each step; further help is offered by the official Troubleshooting a cloud flow from Microsoft.