Outlook Create Draft

Controlled node

Overview

Creates an email draft in Outlook on behalf of the connected user. The draft is saved to the user's Outlook Drafts folder, where it can be reviewed, edited, and sent later. This makes the node ideal for human-in-the-loop workflows where generated emails should be approved before sending.

Provide a Message ID to create the draft as a reply within an existing email thread. When a message ID is supplied, the draft is threaded as a reply to that message instead of starting a new conversation.

Because this is a controlled node, it only runs when it receives a Run event, and it emits a Done event when it has finished.

Validation

The node validates its inputs before creating the draft:

• To, CC, and BCC must each be a valid email address string, or an array of valid email address strings.
• A single Attachments value must be a file object containing an id and a name. Attachment arrays are passed through to Outlook without per-item validation by the node.

If validation fails, no draft is created and the reason is reported on the Status output.

Inputs

Input	Type	Description	Default
Run	Event	Triggers the node to create the draft.	-
To	Text	The primary recipient(s) of the email. Accepts a single email address or an array of email addresses.	-
CC	Text	Carbon copy recipient(s). Accepts a single email address or an array of email addresses.	-
BCC	Text	Blind carbon copy recipient(s). Accepts a single email address or an array of email addresses.	-
Subject	Text	The subject line of the draft email.	-
Message ID	Text	Optional. The ID of an existing Outlook message. When provided, the draft is created as a reply in the same thread as that message.	-
Body Text	PlainText	The plain text body of the email.	-
Body HTML	PlainText	The HTML body of the email. Use this for richly formatted content.	-
Attachments	Data	File(s) to attach to the draft. A single file object must have an id and name; arrays are passed to the Outlook service.	-
Connections	Connection	The Outlook connection used to create the draft.	-

Outputs

Output	Type	Description
Done	Event	Fires when the node has finished running.
Status	Text	The result of the operation. Contains the success status when the draft is created, or a failed: ... message describing why the draft could not be created.
Draft ID	Text	The ID of the newly created draft. Use this to reference the draft later, for example to update or send it. Empty if the draft was not created.

Runtime behavior

• The node only runs when the Run event fires.
• Empty text inputs are treated as if they were not provided, so you can safely leave optional fields blank.
• If To, CC, or BCC fail email validation, the node stops and reports the failure on Status.
• Errors from Outlook (for example, a missing connection or an API failure) are caught and reported on Status rather than halting the workflow. The exact message is supplied by the service or caught error.
• On success, Status contains the result status and Draft ID contains the identifier of the new draft.

Example

Draft an AI-written reply to a customer email:

1. Add an Outlook Get Inbox node connected to your Outlook connection, and run it to fetch recent messages.
2. Pass the body of the message you want to reply to into an AI Write node with a prompt such as "Write a polite reply to this customer email", generating the reply text.
3. Add an Outlook Create Draft node and wire:
   • The AI Write node's Output into Body Text
   • The original message's id into Message ID
   • The customer's address into To
   • A subject such as Re: Your inquiry into Subject
4. Connect the AI Write node's Done event into the Run event of the Outlook Create Draft node.
5. When the workflow runs, a draft reply appears in the connected user's Outlook Drafts folder, threaded to the original conversation. The Draft ID output can be logged or stored for later reference, and the Done event can trigger follow-up actions such as notifying a reviewer.