Utility Actions

Creating a List

What it does: Builds a list (array) from repeated items or from variables. Use to feed an ITERATOR or to build a payload for another step.

Inputs

• Items (required) — The list contents. Can be: multiple “Item” entries in the UI, or a single variable that is already an array, or a mix (e.g. “Add item” with value #Step1.contact, “Add item” with value #Step2.contact). Product may support “Add from variable” to spread an array into the list.

Outputs

A single variable holding the array. Use in ITERATOR’s List input or in steps that accept arrays.

Output schema

• list / value — The constructed array. Reference as #StepName.list or #StepName (product-dependent). Elements match the order and values you added (e.g. #StepName[0], #StepName[1]).

Stripping HTML Tags

What it does: Removes HTML tags from a string and returns plain text. (In some product versions this step may appear under a “Transform Data” category; the behavior is the same.) Use when you have HTML from email or web scrape and need plain text for AI or display.

Inputs

• HTML content (required) — The string containing HTML (e.g. #Trigger.body, #ScrapeStep.content). Can be a variable from any previous step.

Outputs

The same content with tags removed (and often whitespace normalized). Use for “Generate Summary”, “Extract Information”, or logging.

Output schema

• text — Plain-text version of the input (no HTML tags).

Process Freemarker Template

What it does: Processes a Freemarker template string with a data model (variables). Replaces placeholders (e.g. name, items?size) and returns rendered text.

Inputs

• Template string (required) — The Freemarker template (e.g. “Hello [user.name], you have [count] items.” using your placeholder syntax). Can be a variable (e.g. from a file or previous step).
• Data model (required) — Key-value map: variable names used in the template → values. Values can be variables (e.g. user: #Trigger.contact, count: #Step1.total). Nested objects and lists are supported for complex templates.

Outputs

The rendered string. Use for email body, file content, or dynamic messages.

Output schema

• output / text — The rendered result (plain string).

Creating a Constant

What it does: Defines a reusable constant value that can be referenced in later steps (e.g. API base URL, config flag, or static text). Useful to avoid repeating the same value and to support variable resolution from other steps if the product allows it.

Inputs

• Value (required) — The constant value. Can be text, number, JSON, or a string that includes variable placeholders (e.g. API URL with env) if the product resolves variables at runtime.
• Name (optional) — Friendly name for the constant. Defaults to the step name. Used when referencing (e.g. #StepName or #StepName.value).

Outputs

The constant value so later steps can reference it (e.g. in API URL, headers, or conditions).

Output schema

• value — The constant value. Reference as #StepName or #StepName.value depending on product. Type matches what you entered (string, number, or parsed JSON if supported).