Skip to content
Tutorials Center
My learning

Topics

Lesson 11 of 38 ยท Actions and Expressions

Actions and Dynamic Content in Power Automate

Understand what actions are, how inputs and outputs work, how dynamic content links steps, how to find the right action, and how built-in actions like Compose and Condition fit in.

An action is one unit of work in a flow: send an email, get a row, create a file, call a URL. Each action takes inputs and returns outputs, and the outputs of earlier steps become the inputs of later ones. Once you see flows as a chain of data passing from card to card, everything else gets easier.

Where actions come from

When you choose + New step, the picker has tabs.

  • AI Capabilities: prompts, text recognition and similar tools.
  • Runtime: built-in actions and Control, Data Operation, Variables, Scope, Schedule, HTTP and Request groups.
  • Standard and Premium connectors: each connector shows its triggers and actions.
  • Custom connectors from your environment.
  • Recent and Built-in lists for fast access.

Search by what you want to do ("create file", "send email") and prefer the newest version of an action. Names carry versions such as (V2) or (V3). Use the highest version unless a flow needs older behaviour.

Inputs, outputs and dynamic content

Select a field in an action. A panel shows Dynamic content: a list of outputs from the trigger and every earlier action. Choosing one inserts a token like Subject or Attachments Name. Behind the scenes it is an expression, for example triggerOutputs()?['body/subject'] or outputs('Get_item')?['body/Title'].

A card's three-dot Peek code shows both the input values and the expressions. The Expression tab of the same panel lets you type a formula instead of picking a token (see Expressions first steps).

Data moves forward

Trigger output Subject, sender, id
Action input Fields you fill in
Action output Result for the next step

A step can only use outputs from steps above it.

1 / 2

Naming matters

Referencing the output of a card by name, as in outputs('Get_item'), uses the card's name with spaces replaced by underscores. If you rename a card later, the designer updates tokens it created, but expressions you typed by hand may break. Rename cards early, before you write expressions that depend on them.

A first look at common built-in actions

Action Group What it does
Compose Data Operations Stores a value or expression result for reuse
Condition Control If yes / if no branches
Apply to each Control Repeats actions for every item in an array
Initialize variable Variables Creates a named variable
Terminate Control Ends the run as Succeeded, Failed or Cancelled
Delay Schedule Waits
Scope Control Groups actions for error handling

You will meet each of them in the following lessons; Variables and Compose covers the data ones next.

Conditions

Add a Condition (Control group). Pick a left value with dynamic content, an operator (is equal to, contains, is greater than, is not empty...) and a right value. The card has an If yes and an If no branch. Use Add row to combine tests, and choose And or Or to combine them.

Condition values are compared by type: 1 and "1" differ. If a comparison fails unexpectedly, check whether one side is text and the other a number.

Simulating a chain of actions

This Python stand-in models actions as functions with inputs and outputs, and a dictionary that plays the role of "the run so far". It shows that every step reads earlier outputs and cannot read later ones. It is not Power Automate.

Python Stand-in: actions reading outputs of earlier steps

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.

If you move condition_and_send before compose_title in the tuple, you get a KeyError. In the designer the dynamic content list simply would not offer the later output.

Action settings

Every action has Settings in its three-dot menu:

  • Timeout: ISO 8601 duration such as PT30S for 30 seconds.
  • Retry policy: default, none, fixed interval or exponential. Chapter 7 explains this.
  • Pagination: retrieve more than the default page of results.
  • Secure inputs / secure outputs: hide sensitive values in run history.
  • Run after: choose when the action runs (success, failure, skipped, timed out), used for error handling.

Turn on Secure inputs and Secure outputs for actions that handle passwords, tokens or personal data. Otherwise anyone who can view run history can read the values.

Run after: a first look

By default an action runs only when the previous one succeeded. Open Configure run after from the three-dot menu of a card to also run it when the previous one failed, was skipped or timed out. That is the base of every error handler you will build in chapter 7.

Python Stand-in: run after success or failure

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.

Common mistakes

  • Choosing an old action version and wondering why a new field is missing.
  • Referencing an output with a typed name that no longer matches after a rename.
  • Putting too many unrelated steps into one flow. Split work into child flows or scopes.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What is dynamic content?

    Dynamic content tokens reference the trigger's and previous actions' outputs.
  2. 2. Which values can a step use as dynamic content?

    A step can reference the trigger and earlier steps, not later ones.
  3. 3. What should you turn on for an action that handles a password?

    Secure inputs and outputs hide values in run history.
  4. 4. What does 'Configure run after' let you do?

    Run after sets the status of the previous action that lets this action run.

Summary

  • Actions take inputs and return outputs; dynamic content connects them.
  • Use the newest version of an action, and rename cards before you write expressions that depend on their names.
  • Condition, Apply to each, Compose, variables, Scope and Terminate are the core built-ins.
  • Action settings control timeout, retry, pagination, secure data and run-after behaviour.

Next: Expressions first steps