Polling or webhook?

You're in a training session with Aisha in IT at Vantara Group on how Power Automate triggers detect events. Aisha lists four statements about trigger behavior.

Quick contrast: Polling asks the service on a schedule ("anything new?"). Push / webhook waits to be notified the moment something happens.

Which statement describes a Push (Webhook) trigger?

This exercise is part of the course

Introduction to Power Automate

Hands-on interactive exercise

Turn theory into action with one of our interactive exercises

This exercise is part of the course

Introduction to Power Automate

BeginnerSkill Level

4.6+

Start Course for Free

Discover what Power Automate is, where it fits in the Microsoft Power Platform, and which of the three cloud flow types - Instant, Automated, or Scheduled - matches a given task. Get oriented in the maker portal, then build your very first flow from scratch and watch Copilot generate the same flow from a plain-English prompt.

Exercise 1: What is Power Automate?Exercise 2: Where does Power Automate fit in?Exercise 3: Pick the right flow type Exercise 4: Which flow type fits?Exercise 5: Navigating the Power Automate portal Exercise 6: Take a tour of the portal Exercise 7: Which section of the portal?Exercise 8: Your first flow Exercise 9: Build your first flow from scratch Exercise 10: Copilot builds it, can you read it?

Bring your flows to life by plugging into real Microsoft 365 services. Learn how connectors expose triggers and actions, choose between polling and webhook triggers, then upgrade a hardcoded email into a dynamic one using expressions like concat() and formatDateTime(). Finish by safely auditing a template and editing a flow in plain English with Copilot.

Exercise 1: Connectors in Power Automate Exercise 2: Trigger or action?Exercise 3: Send an email with a connector Exercise 4: Polling or webhook?

Current Exercise

Exercise 5: Dynamic content and expressions Exercise 6: Dynamic content or expression?Exercise 7: Upgrade an email with dynamic content Exercise 8: Reading flow run history errors Exercise 9: Templates and editing with Copilot Exercise 10: Explore a template Exercise 11: Edit and explain with Copilot

Make your flows think for themselves. Store and update values with variables and Compose, branch with Condition and Switch, loop over arrays with Apply to Each, and shape data with Filter Array, Join, and Select. Then put it all on a timer with Recurrence and match Automated triggers to the inbound events that fire them.

Exercise 1: Variables and Compose Exercise 2: Match the action to its purpose Exercise 3: Build a weekly status string Exercise 4: Conditions and Switch Exercise 5: Build an invoice checker with Condition Exercise 6: Build a ticket router with Switch Exercise 7: Loops and data operations Exercise 8: Pick the right data operation Exercise 9: Filter and loop through deliveries Exercise 10: Automated and scheduled triggers Exercise 11: Scheduled or Automated?Exercise 12: Build a daily delivery check

Wrap up by building a complete approval flow that pauses for a human decision, then learn to test it with Flow Checker, read run history to diagnose failures, and add a Configure run-after safety net. Finish by sharing flows correctly across three modes and applying a responsible-use checklist to anything Copilot generates for you.

Exercise 1: Build a complete approval flow Exercise 2: Which approval type?Exercise 3: Watch an approval flow run end-to-end Exercise 4: Build a leave-request approval flow Exercise 5: Monitor and troubleshoot Exercise 6: Catch and fix with Flow Checker Exercise 7: Skipped or failed?Exercise 8: Sharing flows and using Copilot responsibly Exercise 9: Is this Copilot flow ready to deploy?Exercise 10: Putting it all together Exercise 11: Congratulations!