Do sums, format values and read JSON in a flow

Formulas let a flow work things out on the spot. A quote screen can multiply a monthly price by twelve, show a number the way your country writes it, or print a date from a booking. Write them straight into any text that accepts variables.

Variables are filled in first and formulas are worked out last, so a formula can use any variable. When one formula sits inside another, the inner one goes first:

Your annual total is FLOW.FORMATNUMBER(FLOW.CALCULATE($MONTHLY * 12, 2), DECIMALUS)

#FLOW.CALCULATE

FLOW.CALCULATE(expression, decimals) works out a sum.

• It understands +, -, * and /. Multiplication and division go before addition and subtraction.
• Decimals are written with a point, as in 19.90.
• No brackets and no negative numbers. Anything else, including a stray letter, gives 0.
• Decimals rounds the result. Leave it out and the decimals are cut off, so 2.5 becomes 2.

#FLOW.FORMATNUMBER

FLOW.FORMATNUMBER(number, format) writes a number the way your readers expect. For 1234.567:

• With no format, or a format that is not in the list, you get DECIMALUS.
• There is no currency format. Type the symbol yourself: $FLOW.FORMATNUMBER($TOTAL, DECIMALUS) or R$ FLOW.FORMATNUMBER($TOTAL, DECIMALNOUS).
• Tayon reads the first number in the value and ignores other characters. A value with no number in it gives 0.

#FLOW.FORMATDATE

FLOW.FORMATDATE(date, format, us) rewrites a date and time.

The input must be a date followed by a time, such as 12/25/2026 3:30pm or 25/12/2026 15:30.

• The date can use / or -. Leave the year out and the current year is used.
• The time can be 15, 15:30, 3pm or 3:30pm. A time is required. A date on its own is not understood.
• us says how to read the date: TRUE (the default) for month first, FALSE for day first.
• Dates written year first, such as 2026-12-25, are not understood.

For FLOW.FORMATDATE(12/25/2026 3:30pm, format):

A day-first input needs the third value: FLOW.FORMATDATE(25/12/2026 15:30, DATEUS, FALSE) gives 12/25/2026.

When the input cannot be read, the formula prints Invalid date format followed by the input. A misspelled format prints Invalid output format.

#FLOW.SUBSTRING and FLOW.REPLACE

FLOW.REPLACE needs all three values. It cannot replace text with nothing.

#Reading a value from a JSON reply

When an API/Webhook Call with Return Type set to JSON Response stores its reply under an identifier, you can print single values from it. Say the reply stored as CUSTOMER is:

{"name": "Maya", "address": {"city": "Lisbon"}, "orders": [{"id": "A1"}, {"id": "B2"}]}

There are two ways to reach inside it.

#Square brackets after the identifier

Put the path in one pair of brackets, with : between the steps.

When the whole reply is a list, add the position after the path, counting from 1: $RESULTS[name][2] is the name in the second item. The position can be a variable: $RESULTS[name][$CHOICE].

#The JSON() formula

JSON() puts each step in its own brackets, and positions start at 0.

JSON() also works on the left side of a split condition, as in JSON($CUSTOMER[address][city]) = Lisbon.

#When the value does not come out

• Names must match exactly, capitals included: [City] does not find city.
• A path that leads nowhere prints nothing in the bracket form, and null in JSON().
• These only work when the stored reply is a JSON object, or a list of objects.
• Use one form per field. When a text contains JSON(, the bracket form in the same text is not filled in.