​

Node Inputs

The OutlookSender node accepts several input values that are essential for defining the details of an email that will be sent using Microsoft Outlook. Below is the list of inputs that this node accepts:

• message id: (Optional) A unique identifier for an email message that you wish to respond to. If provided, the node will send a reply to this email rather than creating a new email thread.
• recipient: The email address of the person who will receive the email. This is a mandatory field and must be a valid email address.
• subject: The subject line for the email. This helps summarizes the email’s content and is important for the recipient to understand the context of the message.
• body: The main content of the email message. This is where you write the text that you want to convey to the recipient.

​

Node Output

• email status: After attempting to send the email, this output reports on the success or failure of the operation. It indicates whether the email has been sent successfully or whether there was an issue during the sending process.

​

Node Functionality

The OutlookSender node enables users to send emails directly from Microsoft Outlook through an automated process. It is designed to integrate seamlessly with Outlook, utilizing a provided authentication mechanism, such as an access token, to operate on the user’s behalf.

The functionality includes the ability to not only send new email messages but also to reply to existing ones, a feature that is determined by the presence or absence of a message id. The node handles composing the email, with customizable options for the recipient, subject, and body, and then sends the email from the user’s Outlook account.

Should there be any issue in creating or sending the email, such as problems with the Outlook service or authentication issues, these will be reported back via the email status output.

​

When To Use

You can use the OutlookSender node in scenarios where automated email communication is necessary. For instance:

• When you need to automate the process of sending regular updates or reports to stakeholders.
• When you want to create a workflow that responds to certain triggers by sending out emails.
• When you’re implementing a help desk system that requires sending acknowledgments, replies, or follow-up messages to users.

This node is particularly useful for automating routine email correspondence, enabling you to save time and ensure consistent communication patterns. It’s also valuable in customer service or marketing flow, where timely and consistent communication can greatly enhance user experience and engagement.