> For the complete documentation index, see [llms.txt](https://docs.autommate.com/userguide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.autommate.com/userguide/build-automations/use-inline-functions-in-action-inputs.md). # Use inline functions in action inputs Use inline functions to transform a value while configuring an action input, without adding a separate transformation action for every small operation. ### Before you start * Open an editable Hyperflow and identify the input you want to populate. * Know the source value and the type expected by the receiving field. * Use sample values that contain no passwords, tokens, or personal data. ### Add a function 1. Select the action input. 2. Type `fn.` to open the function suggestions. 3. Select a function and complete the parameter dialog shown by the editor. 4. Use a fixed sample value first. Then map the source variable or previous action output. 5. Run a controlled test and inspect the resulting input/output value. Parameters in the documented function syntax use `|` as a separator. Use the editor's suggestion for the selected function rather than assuming that a comma-separated expression is interchangeable. ### Text functions * `fn.UpperCase(text)` — convert text to uppercase. * `fn.LowerCase(text)` — convert text to lowercase. * `fn.Capitalize(text)` — capitalize the first letter. * `fn.Replace(text|old_str|new_str)` — replace text. * `fn.Contains(text|target_str)` — check for a substring. * **RemoveHTML** — select the function in the editor to remove HTML markup, then complete the suggested arguments. ### Numeric functions Use the function's precision argument where needed: * `fn.Sum(number1|number2|decimal)` * `fn.Difference(number1|number2|decimal)` * `fn.Multiply(number1|number2|decimal)` * `fn.Divide(number1|number2|decimal)` * `fn.Ceil(value|precision)` * `fn.Floor(value|precision)` * `fn.Round(value|precision)` * `fn.Abs(value|precision)` * `fn.Mod(number1|number2|decimal)` * `fn.PowerOf(number|exponent|decimal)` * `fn.Avg(number1|number2|precision:2)` * `fn.IsEven(value)` * `fn.IsOdd(value)` Do not use a formatted number as a numeric input without checking the receiving action's expected type. Decimal and thousands separators can matter when exchanging data with another application. ### Conversion and formatting * `fn.ToFloat(value|decimal)` — convert to a numeric value. * `fn.ToInt(value)` — convert to an integer. * `fn.ToStr(value|type)` — convert to text; date formatting options include `short` and `long`. * `fn.ToCurrency(value|style)` — format a display value using options such as `unit`, `delimiter`, `precision`, and `format`. * `fn.ToPhone(value|delimiter:optional|format:optional)` — format a telephone value. For additional optional arguments, select the function in the installed editor. A formatted string is not a validation of a bank amount, phone number, or business rule. ### Expected result The receiving action gets a value in the required form, and a controlled run produces the expected result. For example, a text-normalization test can compare `fn.UpperCase(hello)` with `HELLO` before mapping a real source field. ### Troubleshoot * No suggestions: confirm that the cursor is in a supported input and type `fn.` again. * Expression appears literally: check the syntax and whether that field evaluates expressions. * Wrong output: inspect the source type, parameter order, precision, and any formatting expected by the next action. * Empty input: inspect the previous action output before changing the expression. ### Related reference * [Configure actions and map data](/userguide/build-automations/configure-actions-and-map-data.md) * [Variables and input/output contracts](/userguide/build-automations/variables-and-input-output-contracts.md) ### Worked example: convert a department label to uppercase This example uses String → Assign in Docs - Action examples - 20261013. The fixed source is finance and the saved String variable is department\_normalized. It transforms local text without calling another business system. 1\. Open a test Hyperflow in Dev and add String → Assign. In Value to Assign, type fn. and choose UpperCase from the function picker.
Type fn. in Value to Assign and choose UpperCase from the installed function picker.

Type fn. in Value to Assign and choose UpperCase from the installed function picker.

2\. In the Uppercase dialog, enter finance in Source and select Save. The action input displays the selected UpperCase function. Use this parameter dialog rather than typing a guessed expression.
The Uppercase parameter dialog exposes Source and Save. Enter finance for this exercise.

The Uppercase parameter dialog exposes Source and Save. Enter finance for this exercise.

3\. In Source to be Assigned, select or create the String variable department\_normalized. Save Hyper Flow and select Run Hyper Flow. 4\. Open Logs Summary → View All Logs, then the String - Assign quick-info control. Choose Fetch Input/Output Values and Output. Compare the returned text with FINANCE. The Dev v1.0.1 run on 13 October 2026 started at 10:55:53 and ended at 10:55:54, Türkiye browser time. It completed with one transaction; the action Output type was string and Preview was FINANCE.
A later run at 11:04:15 confirms the same String Assign result: Output type string, Preview FINANCE. That expanded run also contains the separate Mate DB Set exercise.

A later run at 11:04:15 confirms the same String Assign result: Output type string, Preview FINANCE. That expanded run also contains the separate Mate DB Set exercise.

To extend the exercise, try hr and compare the result with HR. Then pass a source variable or an empty value and inspect the returned value before mapping it to a business action. These are follow-up checks; the recorded run above used the fixed value finance. Uppercase conversion alone does not validate a department.