Understanding the different types of triggers for cloud flows
Understanding the different types of triggers for cloud flows is an essential part of preparing for the PL-100 Microsoft Power Platform App Maker exam. Whether you’re working with Power Automate or Logic Apps, you’ll need to know how different triggers work to automate your processes and ensure smooth workflow execution. In this article, we will delve into the different types of triggers.
Manual Trigger
The manual trigger, as the name suggests, is used when you want to manually start a cloud flow. It doesn’t start automatically based on a particular event or on a specific schedule.
Most of the time, a manual trigger is useful when you need to test a cloud flow or observe its behavior. It is helpful in cases when you don’t want the flow to run autonomously, giving you control over when the flow should start.
Scheduled Trigger
A scheduled trigger is used to run a cloud flow at set intervals, such as daily or weekly, or at a particular time and day. This is ideal for routine tasks that need to be completed automatically without manual intervention.
A common example of a scheduled trigger would be a weekly report that pulls data from a database and sends an email with the attached data. The trigger would be set to activate once a week at a specific time, and the flow would run automatically to complete the task.
Event-based Trigger
For event-based triggers, the flow starts when a specific event happens. In the context of Power Automate, these events primarily involve changes in data or the status of an application.
For instance, you could have a flow that starts when an item is added to a SharePoint list, or when an email with a specific subject line enters your inbox. Event-based triggers are incredibly useful because they allow your processes to react in real time to changes and events.
Power Automate Button Triggers
Power Automate button triggers are a specific type of manual trigger that allow users in Power Apps to initiate a flow with the click of a button.
An example of a Power Automate button trigger could be an approval process in Power Apps. When an item is selected and an “Approve” button is clicked, this can trigger a flow to move the item to an approved state, send approval notification emails, and update any related records.
HTTP Trigger
An HTTP trigger starts a flow when it receives an HTTP request. If you’re familiar with APIs, you can consider HTTP Triggers as a way to create your own custom, lightweight API endpoint in the cloud. Once triggered, the flow can perform actions and return a response.
For example, you might have an HTTP Trigger that returns data from a database in response to a GET request, or updates a record in response to a POST request.
Conclusion
Having a thorough understanding of these trigger types is fundamental to optimize the use of Power Automate and Logic Apps, offering efficiency and performance improvements to your flows. Remember, the key to mastering triggers is practice – envision different scenarios, and try applying the right trigger!
Practice Test
True or False: There are only two types of triggers for cloud flows, Record-triggered and Business Process flow.
- True
- False
Answer: False
Explanation: Apart from Record-triggered and Business Process flow, there are also Power Apps-triggered, HTTP Request-triggered, Timer or scheduler-triggered, and External systems-triggered flows.
A Record-triggered flow can be set off by creating a new record in the cloud.
- True
- False
Answer: True
Explanation: A Record-triggered flow in cloud flows can be triggered by creating, updating, or deleting a record.
Which type of flow gets triggered when an app maker passes data from Power Apps to the flow?
- Record-triggered
- Business Process
- Power Apps-triggered
- HTTP Request-triggered
Answer: Power Apps-triggered
Explanation: Power Apps-triggered flow is designed to get triggered when an app maker passes data from Power Apps to the flow.
What does a Timer or scheduler-triggered flow mean?
- A. A flow that runs at a specific time daily.
- B. A flow that runs on a schedule set by the user.
- C. A flow that runs continuously without stopping.
- D. None of the above.
Answer: B. A flow that runs on a schedule set by the user.
Explanation: Timer or scheduler-triggered flow is designed to run on a user-defined schedule.
True or False: An HTTP request-triggered flow gets triggered when the flow receives an HTTP request from an external source.
- True
- False
Answer: True
Explanation: An HTTP request-triggered flow starts when the flow receives an HTTP request from another system or service.
Which type of flow is triggered when a step from a business process is executed?
- Record-triggered
- Business Process flow
- Power Apps-triggered
- HTTP Request-triggered
Answer: Business Process flow
Explanation: Business Process flow is designed to get activated and run whenever a step from a business process is executed.
Which of these flows gets triggered when connected to external systems like Azure Event Grid or SQL Database?
- A. Record-triggered flow
- B. Timer or scheduler-triggered flow
- C. External systems-triggered flow
- D. HTTP Request-triggered
Answer: C. External systems-triggered flow
Explanation: External systems-triggered flows get activated when connected to other external systems like Azure Event Grid, SQL Database etc.
True or False: Cloud flows can only interact with Microsoft services.
- True
- False
Answer: False
Explanation: Cloud flows can interact with both Microsoft services like Azure and Dynamics 365 as well as third party services like Twitter, MailChimp, etc.
In a __________ triggered flow, the flow gets activated when a scheduled task ends.
- A. Record-triggered
- B. Business Process
- C. Power Apps-triggered
- D. Timer or scheduler-triggered
Answer: D. Timer or scheduler-triggered
Explanation: Timer or scheduler-triggered flow starts running on a user-defined schedule like when a scheduled task ends or at a specific time on a daily basis.
An External systems-triggered flow can be associated with any non-Microsoft systems.
- True
- False
Answer. True
Explanation: External systems-triggered flow can be associated with any external system, not just limited to Microsoft systems. It can also connect to third-party services.
Interview Questions
What is a cloud flow trigger in the context of Microsoft Power Platform?
A cloud flow trigger is a predefined condition or event that initiates the execution of a flow created on Microsoft Power Platform.
How many types of triggers are primarily used in cloud flows?
There are primarily three types of triggers used in cloud flows: manual, automated, and instant.
What is a manual trigger in the context of cloud flows?
A manual trigger is a type of trigger that requires direct user input or action in order to function. The flow will only begin when a user specifically chooses to run it.
Can you describe an automated trigger for cloud flows?
An automated trigger is one that begins automatically when specific system events or changes take place. This can be when a new record is added or existing one is modified in a connected data source.
What is an instant trigger in a cloud flow?
Instant trigger allows the flow to be run manually at any given time from a button in Power Apps, the Flow mobile app, or the Flow website.
How is a “Scheduled” trigger used in cloud flows?
A “Scheduled” trigger allows a flow to be triggered based on a set schedule. For example, a user can set it to start every Monday at 8 AM and perform actions on a weekly basis.
How do you set up an IoT trigger in a cloud flow?
IoT triggers in Cloud Flow can be set up by linking the flow to an IoT device or hub such as Azure IoT Central and then specifying the conditions that cause the flow to trigger.
Would deleting a file from DropBox be a valid triggering event?
Yes, deleting a file is a valid event for triggering a flow. The flow can be designed such that once the file is deleted, a set of actions are then automatically initiated.
What does “Recurrence” mean in the context of cloud flow triggers?
“Recurrence” refers to setting a flow to occur frequently at predefined intervals, such as hourly, daily, weekly, monthly, or quarterly.
How would a SharePoint ‘When an item is created or modified’ trigger be used in a cloud flow?
This trigger would be used to launch a flow whenever a new item is added or an existing item is changed in a specific SharePoint list or library.
How could an ‘Office 365 Outlook’ trigger be applied in a cloud flow?
An ‘Office 365 Outlook’ trigger could be used to start a flow whenever a new email arrives in a specific inbox, or when an event is added to a calendar, etc.
Do HTTP triggers offer web-based automation capabilities in the context of cloud flows?
Yes, HTTP triggers can launch a flow from an HTTP request, thereby integrating web services and APIs into the flow for web-based automation.
Can Microsoft Teams be used as a potential trigger in a cloud flow?
Yes, a Microsoft Teams’ action like a new message in a specific channel can serve as a flow trigger, initiating predefined actions such as sending notifications or emails.
Which trigger is most suitable for real-time automation in cloud flows?
The “Automated” trigger could be the most suitable for real-time automation as it launches a flow immediately when a specified event or change occurs in the system.
Can a cloud flow have more than one trigger?
No, a cloud flow can have only one trigger. This means that each flow defines one event that causes it to run.