Picking the right trigger

1. Picking the right trigger

Welcome to Intermediate Power Automate. You'll build production-grade flows that handle real data, branch on conditions, route approvals, and recover when things break. It starts with the single most consequential decision in any flow.

2. What you'll learn

Here's how the course is laid out. Chapter one picks the right trigger, the single most consequential line of any flow. Chapter two reads data, resolves people, fetches documents, and sends notifications. Chapter three adds conditional logic, Switch routing, run-after failure handling, and the diagnostic loop. Chapter four brings in approvals and ships a production-ready capstone.

3. Meet the instructor

This course was developed with Dani Kahil, founder of Kahil Consulting and a Microsoft MVP in Power Platform. Dani has spent fifteen years designing real-world automations across Power Platform, Dynamics 365, and Azure DevOps. His goal for this course is to take you from someone who can build a flow to someone who can ship one that's production-ready and handed over. This course assumes you've completed Introduction to Power Automate, or you're comfortable with dynamic content, expressions, Conditions, Switch, Apply to Each, and run history.

4. A flow's first decision

Every Power Automate flow starts with exactly one trigger. The trigger is the moment that decides when the flow runs. Before you build anything else, you have to answer one question. What real-world event should start this flow? Get that right and the rest follows. Get it wrong and the flow either misses things, or it burns through your run budget for no reason.

5. The three trigger families

Triggers come in three families. Recurrence triggers fire on a schedule, whether that's every morning at eight, every hour, or every Monday, so they cover your periodic sweeps. Automated triggers fire when something happens in a source system, like when a row in a database changes, a file lands in a document library, or an email arrives. And Manual triggers fire when a person presses a button, which makes them the right fit for on-demand tools where a user kicks the flow off themselves.

6. Manual triggers can take inputs

One detail worth knowing about manual triggers is that they take inputs. Open the trigger card, click Add an input, and collect Text, Number, Yes/No, and more. Each input becomes a dynamic content token in every downstream action. The user types values into a dialog at run time and the flow takes it from there. Handy for ad-hoc tools, like generating a welcome pack or kicking off a report.

7. The same flow, three different triggers

Here's the catch. The same flow body can be wired to any of the three depending on what you're listening for. Run every morning at eight is a Recurrence. When someone uploads a signed document is a SharePoint file trigger. When a Dataverse row's status changes to Renewed is a Dataverse trigger. Remember: the trigger isn't a technical choice. It's a description of the real-world event you're automating.

8. Templates as starting points

You don't always start from blank. The Templates gallery has hundreds of pre-wired flows, like email me when a SharePoint item is added, save Outlook attachments to OneDrive, or post to Teams when a form is submitted. Pick a template that matches your event and you start with the right trigger in place. Always audit before you adopt, but it's often faster than wiring from scratch.

9. Let's practice!

Pick the right trigger family and the rest falls into place. Time to try it out.

Create Your Free Account

By continuing, you accept our Terms of Use, our Privacy Policy and that your data is stored in the USA.