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.
in the mean time, here’s a workaround. You can send error output, and send the email without the cc if there is an error.
If this response helped you, please click the heart to show that it is useful If this response solved your issue, mark it as the solution to help the community
The workaround unfortunately is not a workable solution when migrating existing workflows. An alternative workaround option is to built a sub-workflow handling all different cases (CC, BCC, attachments), but honestly, what’s the point?
If this response helped you, please click the heart to show that it is useful
If this response solved your issue, mark it as the solution to help the community