StyloDocs
Workflow blocks

Transform

Transform and reshape data between steps

View as Markdown

system/transform — Transform and reshape data between steps.

Where it appears

The Transform block lives in the Logic & control group of the Workflow Builder.

Fields

FieldTypeRequiredDefaultDescription
inputDatatext (multi-line, supports references)YesThe data to reshape. Accepts a literal JSON value or a <StepName.field> reference to an upstream output, which the selected transform is then applied to.
transformTypeselectYesextractThe kind of reshape to apply to the input. Extract pulls a single field by path, Filter keeps only listed fields, Map renames fields, and Template formats the data as text. The configuration field shown below depends on this choice. Options: extract, filter, map, template.
extractPathtextNoDot/bracket path to the single value to pull out of the input — e.g. ticket.subject or items[0].name.
includeFieldstext (multi-line)NoJSON array of top-level field names to keep from the input; all other fields are dropped from the output.
fieldMappingstext (multi-line)NoJSON object mapping new output field names to source field names from the input — e.g. {"ticketSubject": "subject"} reads input.subject and writes it as ticketSubject.
outputTemplatetext (multi-line, supports references)NoText template rendered with values from the input, where {{fieldName}} placeholders are replaced by the matching field. The rendered string becomes the transform's output.

Inputs and outputs

Inputs are the configurable fields above. The block produces these outputs:

Outputs

Reference an output downstream with <Transform.field>.

NameTypeDescription
successbooleanWhether transform succeeded
dataanyTransformed data
errorstringError message if failed

Example

A minimal configuration for this block:

{
  "type": "system/transform",
  "config": {
    "inputData": "<PreviousStep.field>",
    "transformType": "extract"
  }
}

Limits and failure modes

  • Required fields (inputData, transformType) must be set, or the block fails validation before it runs.
  • On failure the error output is populated; downstream blocks that reference other outputs may not receive values.

On this page