The action called "Verfassen" in the German interface is Compose in English, and it is a temporary store for any kind of value. What it is used for and when variables are the better choice.
The action "Verfassen", Compose in the English original, is a temporary store: it takes in any value, a text, a number, an entire data object, or the result of a formula, and makes it available to all following steps as output. It does nothing more than that, and that is exactly what makes it so useful. The German translation misleads many people, because the block has only a marginal connection to composing text. As of: July 2026.
The decisive difference: a Compose is immutable, its value is fixed after the step. A variable ("Initialize variable" and its siblings), on the other hand, can be changed over the course of the flow, for example counted up in a loop or filled step by step. The rule of thumb is: anyone who only wants to record or calculate a value uses Compose, it is lighter and faster. Anyone who needs to change a value along the way needs a variable. A common pitfall here: variables must always be initialized at the top level of the flow, not inside a loop or condition, Compose has no such restriction.
Following actions access the value of a Compose step via its "output", in formulas via outputs with the name of the step. That is why it pays to rename Compose steps immediately: "Verfassen 7" becomes "Recipient list", and the flow stays readable even a year later. Our Power Automate consulting, and for the related evergreen topic of the German interface it is worth looking at "Apply to each" explained in German.
The German Power Automate interface translates the English action names literally, Compose became "Verfassen". What is meant is assembling a value, not writing text. Anyone searching for solutions should therefore always also search for the English term Compose, most guides online use it.
Yes, a Compose can hold a complete object or array, for example a self-built JSON with multiple fields. You then access individual parts via a formula. For structured data that is later to be read out selectively, the combination of Compose and "Parse JSON" is the usual pattern.
Practically not, Compose is one of the lightest actions there is and is noticeably faster than variable operations. The only thing to keep in mind is the action allowance of the license: a Compose also counts as an action, and in large loops this adds up. So within loops, use it only where it is really needed.
Founder of NordFlux. Spent four years automating processes at enterprise scale at Dräger, and now brings that depth to the mid-market — pragmatic and with full data sovereignty.
Certifications
Premium or Process? Here's how to find the right Power Automate license, and how flow groups save money on small flows.
Variables in Power Automate explained simply: Initialize, Set, Increment and Append – the most important actions in German.
The Compose action looks simple, but confusing it with variables produces flows that get harder to maintain with every change. NordFlux structures your flows from the start so intermediate steps stay traceable and later changes carry no risk. In an initial conversation, we review your existing flows for maintainability.
