Get started with triggers

A trigger is an event that starts a cloud flow. For example, you want to get a notification in Microsoft Teams when someone sends you an email. In this case, receiving an email is the trigger that starts this flow.

Power Automate offers connectors to services such as SharePoint and Outlook. Most connectors offer prebuilt triggers that you can use to start your flows. Here's a partial look at the triggers that Office 365 Outlook connector provides by default.

Choose the right trigger

Triggers can be started instantly or manually, on a schedule, or automatically when an external event occurs, such as when an email arrives. The following table lists some common trigger scenarios and the type of flow you should create.

Add a trigger to an existing flow

When you edit a trigger in an existing flow, the new trigger must be the first step of the flow.

1. Edit the flow and delete the existing trigger.

2. After you delete the trigger, Power Automate prompts you to select a new trigger.

3. Search for the connector and then select the app icon. The following screenshot shows the results if you search for Share.

   

4. When you select the app icon, the corresponding triggers and actions are listed. Select the trigger that best suits your needs.

Licensing for premium connectors

You need a standalone Power Automate license to access all premium, on-premises, and custom connectors. For flows that are in-context of an app built in Power Apps, you can leverage Power Apps license. Microsoft 365 plan licenses can use standard connectors but can't use premium connectors. To learn more about licensing, go to the Power Platform Licensing Guide.

To find your license, do the following steps.

1. Sign in to Power Automate.
2. Select My flows.
3. Select a cloud flow.
4. Go to the Details section and view the details under Plan.

Customize a trigger by adding conditions

Sometimes, you might need to customize a trigger so that it fires only when certain conditions are met. For example, you might be using SharePoint's When an item is created or modified trigger in Power Automate. This trigger fires for every change to SharePoint items. However, you might want the flow to only trigger when an item is created or the status is marked as Approved. While you can filter other events by adding conditions to the flow, the flow still runs and the calls are counted as an API request. This causes you to reach your API request limits faster. To avoid it, you can write expressions in trigger conditions, avoiding a run if the condition in trigger isn't met.

Use trigger conditions to reduce flow runs

Trigger conditions can help streamline your flows and reduce the number of unnecessary runs. This helps keep flow runs and Power platform requests consumption low. With trigger conditions, you can set up multiple conditions that must be met before a flow is triggered.

For example, you need to create a flow that processes every approved invoice. Without trigger conditions, your flow would trigger every time an invoice email is received, even if the invoice isn't approved. This can result in the flow running 1,000 times for 1,000 invoices, even though only 50 of them are approved.

By adding a trigger condition to trigger only when an invoice is approved, the flow runs only 50 times. This means it consumes fewer Power Platform requests. If the trigger condition isn't met, the flow isn't triggered, and no run history is logged.

This is especially important in pay-as-you-go environments, where every flow run is charged. By reducing the number of runs, you can keep your costs low while still achieving your desired outcomes.