Outlook Reply To Email

Controlled node

Overview

The Outlook Reply To Email node sends a reply to an existing email thread using Microsoft Outlook. It requires the message ID of the original email to thread the reply correctly, and supports adding recipients, attachments, and both plain text and HTML body content.

This node is useful for automating email responses in customer service workflows, notification systems, or any process that requires programmatic replies to incoming messages.

Threading

The reply is threaded to the original email using the messageId input. If the message ID is not provided or is invalid, the email will be sent as a new message rather than a reply.

Inputs

Input	Type	Description	Default
Run	Event	Triggers the node to send the reply.	-
To	Text	Primary recipient email address(es). Can be a single email string or an array of email strings.	-
CC	Text	Carbon copy recipient email address(es). Can be a single email string or an array of email strings.	-
BCC	Text	Blind carbon copy recipient email address(es). Can be a single email string or an array of email strings.	-
Subject	Text	The subject line of the reply email.	-
Message ID	Text	The ID of the original email message being replied to. This is required to thread the reply correctly.	-
Body Text	PlainText	The plain text version of the email body.	-
Body HTML	PlainText	The HTML version of the email body. If provided, this will be used for rich formatting.	-
Attachments	Data	Files to attach to the reply. Can be a single file object or an array of file objects with id and name properties.	-
Connections	Connection	The Outlook connection configuration to use for sending the email. Configure this in the properties panel.	-

Outputs

Output	Type	Description
Done	Event	Fires when the email reply has been sent successfully or if an error occurs.
Status	Data	Contains a success message if the email was sent, or an error message if the operation failed.

Runtime Behavior and Defaults

• Email Validation: The node validates all email addresses (To, CC, BCC) to ensure they are properly formatted. If any email is invalid, the node will fail with an error status.
• Attachment Handling: Attachments can be provided as either a single file object or an array of file objects. Each file object must contain id and name properties referencing files in the Intellectible library.
• Message Threading: The node uses the messageId input to thread the reply to the original conversation. If the message ID is missing or invalid, the email may be sent as a new message rather than a reply.
• Connection Requirement: This node requires a valid Outlook connection to be configured in the properties panel. The connection determines which Outlook account sends the email.
• Error Handling: If the email fails to send (due to network issues, authentication problems, or invalid inputs), the status output will contain an error message and the done event will still fire.

Example Usage

Scenario: Automatically reply to incoming emails with a standard acknowledgment message.

1. Connect an Outlook Get Inbox node to retrieve incoming messages.
2. Connect the messages output to a For Each node to process each message individually.
3. Inside the loop, connect to the Outlook Reply To Email node:
   • Connect the run event from the For Each loop
   • Set To to the sender's email from the message data
   • Set Message ID to the message ID from the inbox data
   • Set Subject to "Re: {{subject}}" (using a Text node with template variables)
   • Set Body Text to a standard acknowledgment message
   • Configure the Connections property with your Outlook connection
4. Connect the done event to continue the workflow after the reply is sent.

Input Configuration:

To: {{sender.email}}
Message ID: {{message.id}}
Subject: Re: {{message.subject}}
Body Text: Thank you for your email. We have received your message and will respond shortly.

This will send a threaded reply to each incoming email while preserving the original subject line and conversation thread.