Skip to content
Tutorials Center
My learning

Topics

Lesson 7 of 38 ยท Flows and Triggers

Instant Flows: Manual Triggers, Buttons and Inputs

Build instant cloud flows with the manually trigger a flow trigger, define text, file and yes/no inputs, run them from the mobile app, Teams and SharePoint, and respond.

An instant flow runs when a person asks it to. It is the right tool for tasks such as "send the weekly summary now" or "approve this document". Instead of waiting for an event, the flow starts with a button, and the button can ask for input.

Creating an instant flow

  1. Choose Create > Instant cloud flow.
  2. Name the flow, then choose a trigger. The most common is Manually trigger a flow. Others start the flow from Power Apps, a Teams message action, a SharePoint selected item, or a button in the mobile app.
  3. Select Create.

Trigger inputs

On the Manually trigger a flow card choose Add an input. Types available:

Input Use for
Text Names, comments, short values
Yes/No Switches such as "Notify manager"
File A file chosen by the user
Email A validated email address
Number Quantities
Date A date chosen from a calendar
Please select an option A fixed list, defined in the input's options

Each input gets a title and optional description, and the user fills it in when pressing the button. In later steps the input appears as dynamic content named after the title. Required inputs must be filled; optional ones come back empty.

You can use Advanced options to give an input a default value and to set a drop-down list of choices.

Where people run instant flows

  • The maker portal (open the flow and select Run).
  • The Power Automate mobile app, which shows buttons and can use the phone's camera and location.
  • Teams, by adding the Power Automate app, or the For a selected message trigger for message actions.
  • SharePoint, with the For a selected item trigger. Selecting an item on a list shows the flow under the Automate menu.
  • Power Apps, when a flow is added to an app and called with parameters.

Sharing matters: by default a button flow can be run by its owner only. Share it as a run-only user to let others press it, and choose whether they use their own connections or yours.

Returning a result

Some triggers let the flow respond. In a Power Apps flow you add Respond to a Power App or flow at the end, defining output fields. A flow called from another cloud flow uses Respond to a Power App or flow too. For an HTTP request flow you use the Response action (see HTTP and webhook triggers).

Limit outputs to what the caller really needs, and return a status such as ok plus a message so that failures can be shown to the user.

A stand-in for an input form

The next stand-in is plain Python. It models a button flow with inputs: it validates the inputs, then runs the steps. Real validation of required fields and types is done by the platform; the stand-in shows the logic.

Python Stand-in: a button flow with inputs

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Using Yes/No inputs

A Yes/No input becomes true or false. Use it in a Condition with the expression triggerBody()['boolean'] style references, or simply pick the dynamic content. Real input names depend on what you called them; for the first Yes/No input the code often shows a name like boolean, for text text, for a file file, and later inputs get a number suffix (text_1). Peek code on the trigger card shows the exact name.

Give inputs short, clear titles. The title is what the user sees in the button's form and what you pick later as dynamic content.

Instant flow patterns

  • Quick notification: button, then a Teams message or email using the typed message.
  • File processor: the user picks a file, the flow converts or stores it.
  • Approve selected item: a SharePoint button that starts an approval for the chosen row.
  • Parameterized report: a date input and a button, the flow builds a report for that date.

Date inputs and defaults

A date input returns text in a standard format, so you often convert it. This stand-in shows how a default value protects you when the user leaves the field empty.

Python Stand-in: default a missing date to today

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

In a real flow you would write if(empty(triggerBody()?['date']), utcNow('yyyy-MM-dd'), triggerBody()?['date']), covered in Text, dates and time zones.

Common mistakes

  • Making every input required, which discourages use. Mark only what you need.
  • Forgetting to share the flow, then wondering why colleagues do not see the button.
  • Putting long processing after the trigger without a response. The user waits with no feedback; reply early or send a notification when finished.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which trigger gives a flow a button that people press?

    Manually trigger a flow starts the run when a person presses the button, optionally with inputs.
  2. 2. Where can someone run an instant flow besides the portal?

    Instant flows can surface in the mobile app, Teams, SharePoint lists and Power Apps.
  3. 3. How do other people get to run your button flow?

    Run-only sharing lets chosen users press the button without being able to edit the flow.
  4. 4. Where can you find the exact internal name of a trigger input?

    Peek code shows the JSON, including names such as text or boolean.

Summary

  • Instant flows start from a button and can ask for text, file, yes/no, number, date and choice inputs.
  • They can be run from the portal, mobile app, Teams, SharePoint and Power Apps.
  • Share them as run-only users and choose whose connections they use.
  • Return a clear response so the caller knows what happened.

Next: Scheduled flows and recurrence