If you use Math Operations in your workflows, you have probably hit the point where you needed to save the result to a custom field just to use it again in the next step. That workaround is no longer necessary. Math Operation results are now saved as output variables automatically - ready to use in any following action without any extra steps.

What's changed

When a Math Operation runs in a workflow, its result is now stored as an output custom variable for that action. In any later step, you can select that output directly from the custom value picker and use it however you need - including feeding it into another Math Operation.

If you want to also save the result to a contact field or record, you still can. Simply select a field in the Update field option and the result will be written there too. But if you only need the value for use further down the workflow, you can leave that field empty and work with the output directly.

Why it matters

The old approach meant an unnecessary middle step - calculate something, save it somewhere, then pull it back out again. For workflows with multiple calculations or branching logic that depends on a calculated value, that added up quickly.

Now the result flows straight through. One Math Operation can reference the output of a previous one, making it much more practical to build workflows that involve sequential or dependent calculations.

A simple example: a workflow calculates the total number of sessions a client has completed, then uses that output in the next step to decide which follow-up message to send - all without saving anything to a custom field first.

How to use it

Add a Math Operation step to your workflow and configure your calculation. In the next action, open the custom value picker and select the Math Operation output from the list. That is all there is to it.