Power Automate Variables Explained in German

Anyone who goes beyond the simplest trigger-action setup in Power Automate quickly runs into variables: small storage spaces for numbers, text, lists, or boolean values that a flow carries along during its run. They count loop iterations, collect results from multiple steps, or remember a status until it's needed later. For beginners, the German terminology in particular is often confusing, because several similarly named building blocks appear in the action catalog: Initialize, Set, Increment, Decrement, and Append.

This article classifies the four central variable actions in Power Automate according to the official Microsoft documentation, explains the German terms in detail, and shows what you need to watch out for regarding data type, scope, and loops. As of: July 2026.

What Are Variables in Power Automate and What Are They For?

A variable is a named storage location within a cloud flow to which you assign a data type and a value. According to the official documentation on Store and manage values in variables Power Automate supports six data types: Integer, Float, Boolean, String, Array, and Object.

Variables are useful when you:

• want to count loop iterations, for example how many times an Apply-to-each loop has already run.
• iterate over an array and need an index value to access a specific element.
• want to collect an intermediate result from multiple steps before using it at the end of the flow.
• want to carry a status or a condition along across multiple actions.

Important to know: according to the documentation, a variable exists only within the cloud flow that creates it, and persists across all loop iterations. If you want to access its value later, you reference the variable's name as a token, not the name of the action that created it.

Initialize Variable: The First Step for Every Variable

Before you can use a variable, it must be created with the Initialize Variable action. This action sets the name, data type, and optionally a starting value in a single step.

• Name: the identifier under which you reference the variable later.
• Type: the data type, for example Integer, String, or Array.
• Value: the starting value. According to the documentation it is optional, but it is recommended as a best practice so that the initial state of the variable is always clearly defined.

You should know two limitations before you build your flow. First, a single Initialize Variable action, despite its array-like internal structure, can only ever create one variable at a time; for each additional variable you need a separate action. Second, variables can only be declared at the global level, meaning directly in the main path of the flow, not within a scope, a condition, or a loop. If you want to start a counter inside a condition, you must place the initialization beforehand, at the top level.

Set Variable: Assigning a New Value

Once a variable exists, you change its content using the Set Variable action. Unlike initializing, there is no default value here; the value is a required field. The new value and the variable must also have the same data type, so an Integer variable does not accept a string value.

Set Variable is the right choice whenever you want to replace a value completely, for example to set a status from "pending" to "completed", or to overwrite an intermediate result from a previous action.

Increment and Decrement Variable: Counters in Loops

For counters, Power Automate offers two dedicated actions: they increment or decrement a variable by a constant value, without you having to calculate the current state yourself. According to the documentation, both actions work exclusively with Integer and Float variables.

• Increment: adds a value to the existing variable; the default value is one if no custom value is specified.
• Decrement: subtracts a value from the existing variable, likewise by one by default.

The classic use case from the Microsoft documentation is a loop counter: you initialize an Integer variable with a starting value of 0, place the Increment action inside an Apply-to-each loop, and after the loop has run you have the exact number of processed elements, for example email attachments, in the variable.

Append Values: Extending Strings and Arrays

For string and array variables there is also an Append function. It adds a value as the last element to an existing string or an existing array, without overwriting the previous content. To do this, search the action catalog for "append" and select the appropriate action for strings or arrays depending on the data type. The value to append is a required field and can generally be of any type.

This is practical, for example, when you collect the results of individual iterations within a loop, such as the IDs of processed records in an array, in order to output them together in a summary at the end.

Accessing the Value of a Variable

To use the current content of a variable in an expression, you access it via the function `variables('<VariableName>')`. According to the Reference guide to workflow expression functions this function returns the value of the specified variable, regardless of the data type. If, for example, you want to output the elements of an array variable as text, you combine it with the `string()` function: `@{string(variables('myArrayVariable'))}`. You can find more about building expressions with comparison operators such as `and`, `or`, or `equals` in the guide Using expressions in conditions.

Pitfall: Variables in Parallel Loops

Apply-to-each loops run sequentially by default in Power Automate, meaning one iteration after another. You can switch this setting to parallel execution to save time. However, if you use a variable inside the loop, such as a counter or a collected list, then according to the documentation you must stick with sequential execution if the results are supposed to be predictable. With parallel execution, multiple iterations access the same variable value at the same time, which can cause counter values or appended list entries to be lost or end up in the wrong order.

If you use Power Automate productively across multiple departments and want flows with more complex variable logic, nested loops, or larger data volumes to be built reliably, the Power Automate consulting from NordFlux supports you with setup, testing, and operations. You retain control over your flows, while the technical fine-tuning is handled by experienced hands.

Frequently Asked Questions

How many variables can I create in a flow with a single action?

Exactly one. Even though the Initialize Variable action has an array-like internal structure, according to the documentation it always creates only one variable per action. For each additional variable you need an additional Initialize Variable action.

Can I initialize a variable inside a condition or loop?

No. Variables can only be declared at the global level, meaning outside of scopes, conditions, and loops. Place the Initialize Variable action therefore always at the top level of your flow, even if you only fill the variable inside a loop later on.

Does Increment and Decrement also work with strings?

No. According to the documentation, the Increment and Decrement actions work exclusively with Integer and Float variables. For strings and arrays, you use the Append action instead to add values.

What is the difference between Set Variable and Append to Variable?

Set Variable replaces the entire content of a variable with a new value. Append to Variable, on the other hand, keeps the previous content and adds another value as the last element, which is only possible with string and array variables.

Do I always have to specify a starting value when initializing?

No, the field is optional. However, Microsoft explicitly recommends in the documentation setting a starting value anyway, so that the initial state of the variable remains traceable at all times, especially for counters, which should start at 0.