Reshape every value
between every step

Start with the visual editor it covers about 90% of transformations a business workflow needs, including filtering, aggregation, string handling, date math, math, and field mapping. Switch to the JavaScript editor only for genuine edge cases: a complex dedup rule with custom logic, a parsing routine for an unusual format, a calculation with conditional branches that does not fit one expression. The visual editor is the default, the code editor is the escape hatch.

Five aggregation functions cover most business questions sum (total of a numeric field), count (number of records, optionally filtered), average (mean of a field), min (smallest), and max (largest). All five support an optional group by field, so you can compute sub aggregations like sum of revenue by region or count of tickets by owner without any custom code.

Every timestamp carries its timezone, and every date arithmetic operation honours it correctly by default. Adding days respects daylight saving transitions. Converting between timezones applies the right offset for the date in question. Formatting for an external system can target any timezone explicitly. The bugs that came from manual timezone math simply do not happen here.

Every common need a workflow encounters concatenate, split by delimiter, replace literally or by regex, trim whitespace, change case (upper, lower, title), extract a substring by index or pattern, check contains/starts with/ends with, format with template tokens, and pad to a target length. Every operation appears in the visual editor with a configuration panel and live preview.

The math editor supports standard arithmetic operators (plus, minus, times, divide, modulo, exponent) and built in functions for rounding, absolute value, min, max, and statistics. Precedence follows standard mathematics multiplication and division before addition and subtraction, parentheses for grouping. The expression builder shows precedence visually as you compose.

Live validation catches most issues before the workflow runs missing fields, mismatched types, references that do not exist all flagged inline during configuration with plain English explanations. For issues that only surface at runtime an unexpected null, a malformed external response, a JavaScript exception the execution log captures full context with input, partial output, and a clean error message, and the workflow can retry, skip, or fail gracefully.