You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Workflow variable inputs only accept a bare {{ref}}. Any transformation — a fallback, lowercasing, trimming, concatenation — requires creating a whole CODE (serverless logic function) step. A small set of safe inline expressions would remove most of them.
Motivating example
In one person-enrichment workflow, 9 of 10 CODE steps exist only to do trivial transforms:
coalesce() / first-non-empty — pick a company name from a linked company else a text field; pick a title from 4 candidate fields; domain fallback (3 steps)
string ops (lower(), trim(), strip a URL down to its host) — inline within the above
Proposal
Support a small, safe expression/function set inside {{ }} variable fields, e.g.:
{{ coalesce(a, b, c) }}
{{ ifnull(a, b) }}
{{ lower(x) }}
{{ trim(x) }}
{{ concat(a, b) }}
{{ default(x, "fallback") }}
Benefit
Eliminates the majority of CODE steps — each of which is a serverless function to author, deploy and maintain, and adds latency — and keeps simple transforms visible inline instead of hidden inside code.
This discussion was converted from issue #24046 on August 13, 2026 09:26.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Summary
Workflow variable inputs only accept a bare
{{ref}}. Any transformation — a fallback, lowercasing, trimming, concatenation — requires creating a whole CODE (serverless logic function) step. A small set of safe inline expressions would remove most of them.Motivating example
In one person-enrichment workflow, 9 of 10 CODE steps exist only to do trivial transforms:
coalesce()/ first-non-empty — pick a company name from a linked company else a text field; pick a title from 4 candidate fields; domain fallback (3 steps)lower(),trim(), strip a URL down to its host) — inline within the aboveProposal
Support a small, safe expression/function set inside
{{ }}variable fields, e.g.:Benefit
Eliminates the majority of CODE steps — each of which is a serverless function to author, deploy and maintain, and adds latency — and keeps simple transforms visible inline instead of hidden inside code.
All reactions