Fallback / Default Value Syntax & Chaining for Workflow Merge Tags
N
Naman Gupta
Currently, when custom merge tags like {{contact.name}} are used in Workflow Actions (Notifications, Emails, SMS) and the field is empty or null, it evaluates as a blank space (e.g., "for .").
To prevent building bloated If/Else branches just to handle missing/null variable states, please add native support for fallback/default syntax and variable chaining inside workflow merge tags.
Proposed Syntax Examples:
- Basic Fallback: {{contact.name | "this contact"}}
- Field Fallback: {{contact.name | contact.phone}}
- Multi-Level Chaining: {{contact.name | contact.phone | contact.email | "Valued Customer"}}
This will allow clean, single-node messaging that gracefully handles missing contact data without cluttering the workflow canvas.
Log In