Power Automate Trigger Glossary: Automated, Instant, Scheduled

Power Automate uses four common terms for a flow's start condition, and if "automatisiert", "sofort", "geplant", and "instant" don't immediately tell you what's meant, it's easy to lose track, especially when the German documentation and the English interface use different words. This glossary brings together the key German trigger terms from Power Automate in one place, explains them using the official Microsoft documentation, and shows where each trigger makes sense in everyday use.

Whether you're building your first cloud flow or just want to look up the difference between an automated and an instant flow, here you'll find compact definitions with examples. At the end, we also answer the most common questions about trigger types in Power Automate.

What is a trigger in Power Automate?

According to the official explanation in the Trigger basics a trigger is the event that starts a cloud flow. For example, if an email arrives in your inbox, that very arrival can be the trigger that sends a notification in Microsoft Teams in the background. Every cloud flow needs exactly one trigger as its first step, everything after that is an action.

Power Automate distinguishes between three basic flow types, each tied to a specific kind of trigger: automated, instant, and scheduled. You'll also find this breakdown in the Cloud flows overview where Microsoft compares the three types by use case, example, and benefit.

Automated cloud flow (automatisiert)

An automated cloud flow starts as soon as an external event occurs in a connected service, without anyone having to actively intervene. According to Microsoft, the standard example is an email arriving from a specific person, or a mention of your company on social media. Typical triggers for this flow type:

• An email arrives in Outlook.
• A new file is added to OneDrive.
• A new row is created in Microsoft Dataverse.
• An item is changed in a SharePoint list.

Important for practice: not every connector offers automated triggers, so you're bound by what the respective service provides. In return, the flow runs entirely in the background once the event occurs, without you having to trigger anything yourself.

Instant cloud flow (sofort, originally „Instant")

This is where it gets interesting terminologically: the official German flow type is called „Sofortiger Cloud-Flow" in the Power Automate interface, while the same trigger type is called „Direkt/manuell" in another table of the Microsoft documentation. In both cases the same thing is meant: a trigger that a person actively triggers, for example by tapping a button in the app or on their smartphone. The English original calls this flow type „Instant cloud flow", which is why you'll often simply read „Instant" in community posts and older translations when „sofort" is meant.

According to the guide on Creating flows from your phone the main difference from automated flows is precisely that you trigger the flow manually, for example to quickly remind your team about a meeting. Typical use cases:

• Trigger an approval with one click from Teams or SharePoint.
• Start a recurring task with a tap on your smartphone.
• Generate a report on demand instead of automatically.

Scheduled cloud flow (geplant)

A scheduled cloud flow runs at a fixed time or at recurring intervals, regardless of whether an event is currently occurring or someone presses a button. The basis for this is the recurrence trigger, called „Recurrence" in the English original. According to the guide on Running cloud flows on a schedule you set the following:

• Start time: the date and time from which the flow should run for the first time, including the time zone.
• Frequency: whether the flow repeats every minute, hour, day, week, or month.
• Repeat every: the interval between two runs, for example every two weeks instead of every week.

Example from the documentation: a weekly project report sent automatically every Friday, or a daily data upload to SharePoint. According to Microsoft, the advantage over the other two trigger types is that predictable tasks can be set up once, without you having to actively do anything for each run.

Trigger conditions: restricting when a flow fires

Besides the three flow types, Power Automate has another important term: the trigger condition. It lets you restrict a trigger, regardless of its type, so that the flow only actually runs for certain values. For example, a SharePoint trigger that fires on every change to an item can be filtered with an expression so that only approved entries actually trigger a run. According to the Trigger basics this not only reduces unnecessary runs but also saves API calls, which lowers costs especially with usage-based billing.

Glossary at a glance

• Trigger: the event that starts a cloud flow.
• Automated: starts through an external event in a connected service, without manual action.
• Sofort / Instant / Direkt/manuell: three labels for the same trigger type that a person triggers actively.
• Geplant / Recurrence: starts at fixed times or at recurring intervals.
• Trigger condition: an additional filter that only allows a run when its criteria are met.

If you're unsure which trigger type fits your process, or want to cleanly link multiple flows with different trigger types together, the Power Automate consulting from NordFlux helps you build the right structure. You always stay in control of which process is triggered when and by what.

Frequently asked questions

What's the difference between „sofort" and „instant" for Power Automate triggers?

There's no difference in meaning, both terms refer to the same flow type. „Sofortiger Cloud-Flow" is the official German label in the Power Automate interface, „Instant" is the original English term, which also appears as „Direkt/manuell" in community posts, older guides, and sometimes in tables in the German documentation.

Can I later swap an existing trigger for a different trigger type?

Yes. According to Microsoft documentation, the trigger of an existing cloud flow can be deleted in the designer and replaced with a new one, as long as it remains the first step in the flow. So you could, for example, turn an instant flow into a scheduled one afterwards, but you'll need to set up the trigger configuration again.

How often can a scheduled trigger run at minimum?

The smallest configurable unit is one minute, so in theory you could run a flow every minute. In practice, you should adjust the frequency to your actual needs and your license model, since every run counts as a flow run and, depending on your plan, limits may apply to the number of runs.

Do I need a separate Power Automate license for each trigger type?

No, licensing doesn't depend directly on the trigger type, but on which connectors and how many runs you use. Standard connectors are already included in many Microsoft 365 plans; for premium, on-premises, or custom connectors you need a separate Power Automate license, regardless of the trigger type you choose.

What happens if a trigger condition is not met?

Then the flow doesn't start at all. According to the documentation, in this case no run history is logged and no action in the flow is executed, which avoids unnecessary runs and the associated consumption of Power Platform requests.