Currently, the email field parameter syntax requires using auto-generated random short IDs (e.g., ###xxxxxx###). These are cryptic and hard to maintain when reviewing or editing email templates months later.
Request: Allow the custom_key value (e.g., first_name, email) to work as an alias in field parameter placeholders. Both ###xxxxxx### and ###first_name### would be valid if first_name is the custom_key assigned to that field.
Benefits:
1. Readable templates: "Dear ###first_name###," vs "Dear ###xxxxxx###,"
2. Consistent with the custom_key feature already used for webhooks and API responses
3. Easier maintenance: the custom_key is stable and meaningful, the short ID is opaque
To leave a comment, please authenticate.
