Making optional parameters in Outlook node optional

We’re migrating from the Send Email (SMTP) node to the Outlook node for OAuth support and noticed a key usability gap:

The Outlook node treats optional fields (eg. CC, BCC, Attachments) as required once defined - they can’t be left empty. This breaks reusability, since a single flexible node can’t cover different cases without branching or duplication.

It would be great if these fields were truly optional, matching the behavior of the SMTP node and making the Outlook node more low-code friendly.

1 Like

Required to solve the recurring issue of fields that appear to be optional being mandatory. Bad UX/UI.