@Kiremit We’ve confirmed this issue isn’t related to using an Agent. Our team is migrating from the Send Email (SMTP) node to the Outlook node (since we now need OAuth), and we’ve noticed a major gap in usability.
Unlike the SMTP node, the Outlook node treats all optional fields (e.g., CC, BCC, Attachments) as mandatory once they are defined - they can’t be left empty or null. This creates real challenges for low-code workflows and reusability: instead of one flexible node that can handle multiple scenarios, we’re forced to branch logic or duplicate nodes to cover each case.
Feature request: Making optional parameters in Outlook node optional
It would be great if the Outlook node could be adjusted so that optional fields truly remain optional. This would bring it in line with the behavior of the SMTP node and better support low-code design.