Actions vs. Triggers

Contents

keyboard_tab
Course Introduction
1
Introduction
PREVIEW1m 14s
Connecting Data with Connectors
Course Summary
8
Summary
1m 14s

The course is part of this learning path

Start course
Overview
Difficulty
Beginner
Duration
19m
Students
117
Ratings
5/5
starstarstarstarstar
Description

This course explores the core components of Microsoft's Power Platform, including the Microsoft Dataverse, common data model, compliance, connecting data to Power Platform, and the AI Builder.

Learning Objectives

  • Learn about the Microsoft Dataverse and the Common Data Model
  • Learn about Power Platform environments and data compliance
  • Understand the types of connectors you can use within Power Platform
  • Explore the AI Builder and various low- to no-code use cases for various AI Models

Intended Audience

This course is for anyone who wants to understand the core components within the Power Platform and who wants additional insight into how their data connects within it.

Prerequisites

To get the most out of this course you should already have a basic understanding of Power Platform. Before embarking on this course, we recommend that you take our course "Understanding the Business Value of Microsoft Power Platform" beforehand.

Transcript

Once you've connected your data with connectors, you are ready to leverage operations known as triggers and actions. Actions are tasks directed by a user which can be used in both Power Apps and Power Automate. They're tasks like retrieving data from a specific source, updating data in a database, or sending an email. Actions are prompted by other user interaction or a trigger, which is exactly what it sounds like. It triggers a flow within Power Automate to begin.

Triggers are specific to Power Automate and are events like receiving an email or a form being filled out and submitted. An easy way to think about triggers and actions are like cause and effect or the if-then scenario. If I receive an email, then save it to my OneDrive. In that example, the trigger is receiving an email and the action is saving it to your OneDrive. This also utilizes two different connectors in the same flow being Outlook and OneDrive, both of which require you to connect to those services for this flow to properly function. The if-then example can also be expanded upon to use multiple connectors and engage multiple actions after the trigger.

Using the same example, what if after saving the file to OneDrive, you wanted to upload it to a Teams channel? You could then utilize the Teams connector, and once that trigger activates, the email is saved to your OneDrive and then uploads to the Teams channel you designate. This would be an example of a single trigger engaging two actions, utilizing three different connectors. Flows can go even further than this connecting to multiple different outlets and engaging multiple actions. However, triggers are always required to start a flow. Next, we're going to look at the AI Builder and how you can use it alongside connectors to help streamline business processes.

About the Author
Avatar
Lee Mucciarone
M365 Content Creator
Students
636
Courses
9
Learning Paths
2

Lee has spent most of his professional career learning as much as he could about PC hardware and software while working as a PC technician with Microsoft. Once covid hit, he moved into a customer training role with the goal to get as many people prepared for remote work as possible using Microsoft 365. Being both Microsoft 365 certified and a self-proclaimed Microsoft Teams expert, Lee continues to expand his knowledge by working through the wide range of Microsoft certifications.