Microsoft Outlook n8n integrationAutomate Microsoft Outlook with n8n.

This operation adds a new calendar to the connected mailbox, separate from the default one, so a workflow can file events without touching what the person already has open.

• Name: the calendar's display name, for example Client Calls.
• Calendar Group: an optional group to file the new calendar under, and Color to tell it apart at a glance.

This operation removes a calendar and every event scheduled on it, so it is worth confirming the target before this step runs.

• Calendar: the calendar to delete, picked from the list n8n loads from the mailbox, or supplied by ID, most often the expression {{ $json.id }}, which reads that field from the item arriving in the node, here from an earlier calendar.getAll.

This operation retrieves a single calendar's details, its name, color, group, and whether it is the mailbox's default calendar, without listing the events inside it.

• Calendar: the calendar to read, chosen from the list or passed by ID, most often the value an earlier calendar.getAll already returned.

A workflow that writes events to a specific calendar usually starts here: this operation returns every calendar in the mailbox to pick from.

• Return All: on, n8n fetches every calendar; off, it stops at Limit.
• Filter Query: an OData filter, only calendars that can be shared for example, to narrow the list before it reaches the rest of the workflow.

This operation changes a calendar's name, color, or default status without recreating it, so existing events stay attached.

• Calendar: the calendar to change, picked from the list or given as an ID; nothing else in the node says which calendar receives the new values.
• Name and Color: the new display name and color, and Default Calendar to make it the mailbox's primary calendar.

Creating a contact saves a new person to the mailbox's address book, ready to appear as a suggestion the next time someone addresses an email. Only one field is required.

• First Name: the contact's given name, the only field this operation requires.
• Last Name, plus a handful of optional fields to round out the card: Email Address, Company Name, Job Title.

Deleting a contact takes it out of the mailbox's address book for good. No step in the workflow brings it back.

• Contact: the contact to delete, picked from the list or supplied by ID, most often the value a previous contact.getAll already returned.

This operation retrieves one contact's full card, every field n8n knows about, from job title to phone numbers.

• Contact: the contact to read, picked from the mailbox list or handed over as an ID by the step before.
• Output: Simplified by default, or Select Included Fields to pick only the ones the workflow needs, such as Email Addresses or Company Name.

This operation lists contacts in the mailbox's address book, with the same field-selection options as contact.get.

• Return All: on, n8n fetches every contact; off, it stops at Limit.
• Filter Query and Email Address: narrow the list to contacts matching an OData filter or one of several email addresses, separated by commas.

This operation edits an existing contact's card without recreating it, so its history and category tags stay intact.

• Contact: the contact to change, taken from the list or from the ID an earlier lookup returned.
• Update Fields: one line per field to overwrite, the same list as on creation, Job Title and Company Name after a promotion, Email Address after a domain change.

This operation writes a new email without sending it, ready for a person, or a later step in the workflow, to review first.

• Subject and Message: the draft's subject line and body content.
• To, CC Recipients, and BCC Recipients: comma-separated recipient lists, plus Attachments to attach files.

Deleting a draft clears it from the mailbox for good, whether n8n created it or a person did, and it cannot be recovered afterward.

• Draft: the draft to delete, picked from the list or supplied by ID, most often the value draft.create returned earlier in the same workflow.

Reading a draft returns its current content, recipients, subject, and body included, before it goes any further in a review or send step.

• Draft: the draft to read, chosen from the list or supplied by ID.
• Output and Fields: keep the full record or select only fields such as toRecipients or bodyPreview, and Download Attachments to pull its files into the output as well.

This operation sends an existing draft as-is, the last step of a create-review-send sequence built earlier in the workflow.

• Draft: the draft to send, usually the ID draft.create returned earlier in the same run.
• To: an optional comma-separated recipient list that overrides the one already on the draft.

This operation edits a draft already sitting in the mailbox, its text or recipients, without starting over.

• Draft: the draft to change, taken from the list or from the ID kept earlier in the run.
• Subject, Message, To Recipients: the fields to overwrite, filed under Update Fields alongside Is Read to mark it read or unread.

This operation books a new event on a calendar, from a quick reminder to a full meeting with attendees.

• Calendar, Title, Start, and End: the four fields this operation requires, most often filled with values such as {{ $json.startDateTime }} coming from an earlier step.
• Attendees and Location: optional fields to invite people and set where the event happens.

This operation removes an event from a calendar. The cancellation reaches the mailbox owner and every attendee who had the slot on their own calendar.

• Calendar and Event: the calendar the event lives on and the event to remove, most often the ID an earlier event.create or event.getAll returned.

Reading an event returns its full details, time, location, organizer, and who is attending, useful right before a workflow needs to act on that specific meeting.

• Calendar and Event: which calendar and which event to read, most often supplied by the ID an earlier event.getAll returned.
• Output: Simplified by default, or Select Included Fields to keep only fields such as Attendees or Start.

This operation lists events on a calendar within a date range, the base for any reporting or reminder workflow.

• Calendar, Start Date, and End Date: the three fields this operation requires.
• Return All and Limit: return every event in range or stop at a fixed count, and Include Recurring Event Instances to expand a recurring meeting into each occurrence; left off, the series comes back as one master event and the weekly slots stay invisible.

This operation changes an existing event, its time to its attendee list, without canceling and recreating it.

• Calendar and Event: which event to change.
• Start, End, Attendees: the fields most often updated, filed under Additional Fields alongside Show As to mark the slot busy, free, or tentative. The attendee list sent on an update replaces the existing one in full, so a workflow adding one person has to send all the others again.

n8n creates a new mail folder at the root of the connected mailbox, and returns its Microsoft Graph folder ID for later steps.

• Name: the folder's display name, for example Invoices 2026.
• Parent Folder: optional, nests the new folder under an existing one instead of the mailbox root.

This operation takes an existing mail folder out of the connected mailbox.

• Folder: identifies the folder to delete, usually filled with {{ $json.id }} from an earlier folder.getAll or folder.create step.

This operation reads the details of one mail folder, such as its name and item counts.

• Folder: points to the folder to read, typically {{ $json.id }} from a previous step.
• Fields: limits the response to the properties actually read further down, Unread Item Count to fire an alert, Total Item Count to watch a folder grow.

n8n lists the mail folders in the mailbox, or only those under one parent folder when a search scope is set.

• Return All: on, n8n lists every folder in the mailbox; off, it stops at Limit.
• Filter Query: a raw query such as displayName eq 'My Folder' to match one folder by name.
• Parent Folder: restricts the search to the child folders of one folder instead of the whole mailbox.

Renaming an existing mail folder is what this operation does. Both fields are required here, the folder and the new name, so an update with an empty name stops the node instead of clearing the label.

• Folder: the folder to rename, usually {{ $json.id }} from a previous step.
• Name: the new display name applied to the folder.

The messages inside one specific mail folder come back with this operation, instead of the whole mailbox.

• Folder: the folder to read, for example a shared Support folder identified by {{ $json.id }}.
• Return All: on, n8n walks the whole folder; off, it stops at Limit.
• Search: filters on a keyword matched across the sender, subject and body of each message.
• Download Attachments: adds each message's attachments to the output as binary data.

Deleting a message pulls it out of the connected mailbox. No Folder field appears here, so the same step works wherever the message currently sits.

• Message: identifies the message to remove, usually {{ $json.id }} from the trigger or a message.getAll step.

Reading a message in full is the job of this operation.

• Message: points to the message to read, typically {{ $json.id }} from the trigger.
• Output: Simplified keeps the common fields, Select Included Fields narrows the response to the chosen Fields, Raw returns the full Graph API object.
• Download Attachments: includes the message's attachments as binary data in the output.

n8n lists and searches messages across the whole mailbox, not limited to one folder.

• Return All: on, n8n keeps paging until every match is in; off, it stops at Limit.
• Search: a keyword matched by default against the sender, subject and body.
• Filters: narrows results with structured conditions instead of a free-text search.

Moving a message into a different folder is what this operation handles.

• Message: the message to move, usually {{ $json.id }} from the trigger.
• Parent Folder: the destination folder, for example one created earlier with folder.create.

This operation replies to an existing message, keeping it in the same conversation thread.

• Message: the message being answered, usually {{ $json.id }} from the trigger.
• Reply to Sender Only: off, the reply also goes to every other recipient of the original message.
• Save as Draft: on, n8n creates the reply as a draft instead of sending it right away.

Sending a new message from the connected mailbox is the function of this operation.

• To: a comma-separated list of recipient email addresses.
• Attachments: attaches binary data from a previous step, for example a generated report.
• From: the mailbox the message leaves from, and it has to be the mailbox the credential actually opens, not any address the workflow fancies.
• Save To Sent Items: off, the message goes out without leaving a copy in Sent Items.

Sending a message here puts the workflow on hold until the recipient answers.

• Subject: the email subject, for example Approval required.
• Response Type: Approval adds approve or disapprove buttons inside the message, while Free Text and Custom Form send the recipient to a form instead.
• Append n8n Attribution: on, the message ends with the line saying it was sent automatically with n8n, worth switching off before it reaches a client.
• Limit Wait Time: optional, stops the wait after a set duration instead of blocking the workflow indefinitely.

Editing the properties of an existing message, without sending it again, is what this operation allows.

• Message: the message to update, usually {{ $json.id }} from the trigger.
• Is Read: marks the message as read or unread.
• Category Names or IDs: applies one or more Outlook categories to the message.

An attachment gets added to an existing message with this operation.

• Message: the message to attach the file to, usually a draft created earlier in the workflow.
• Input Data Field Name: the binary field holding the file, for example data from a previous node.
• File Name: optional, overrides the name taken from the binary property.

This operation downloads one attachment from a message as binary data.

• Message: the message that holds the attachment.
• Attachment: the specific attachment to download, usually {{ $json.id }} from an earlier messageAttachment.getAll step.
• Put Output in Field: the binary field name used to store the downloaded file.

n8n retrieves an attachment's metadata without downloading its content.

• Attachment: identifies the attachment to read, usually {{ $json.id }} from an earlier messageAttachment.getAll step.
• Fields: limits the response to chosen properties, for example Name or Size.

Every attachment on one message shows up here, ready to filter before a download.

• Message: the message to inspect, usually {{ $json.id }} from the trigger.
• Return All: on, n8n lists every attachment on the message; off, it stops at Limit.
• Fields: keeps only the properties the next step reads, instead of the full record of each attachment.