Gmail CC field should be allowed to be empty (for dynamic mapping cases)
Aliff Rush
In the previous version of the Gmail module, CC recipient fields were optional and could be left empty without causing errors. The current version requires at least one email address when the CC section is expanded, which breaks workflows where CC recipients are conditionally added based on form responses or other dynamic data.
Use Case:
Many automation scenarios involve variable CC recipients depending on user input. For example:
Typeform submissions where users optionally provide 0-4 CC email addresses
Customer service workflows where CC count varies by case type
Invoice sending where CC recipients depend on customer preferences
In these scenarios, the number of CC recipients can be zero, one, two, three, or more - it's entirely variable based on the data source.
Current Workaround Required:
Users must now either:
Create complex formulas to concatenate non-empty emails
Use Router modules with duplicate Gmail configurations (one with CC, one without)
Add placeholder/dummy email addresses
Requested Change:
Please make CC recipient fields truly optional again, allowing them to be mapped to variables that may be empty without triggering validation errors. If a mapped CC field is empty, simply don't include it in the sent email.
Thank you for considering this improvement.
Log In