> For the complete documentation index, see [llms.txt](https://academy.any2info.com/any2info-academy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.any2info.com/any2info-academy/no-code-platform/data-studio/data-hubs/toolbox/import-and-export/erp/export-to-microsoft-calender.md).

# Export to Microsoft Calender

**Category:** ERP

**Version:** 1.0

**Last updated:** May 28, 2026

**Author:** Any2Info

***

### Description

The **Export To Microsoft Calendar** node allows you to create or update calendar events in Microsoft Calendar.\
It uses Microsoft Graph APIs to securely interact with calendars within Microsoft 365.

Microsoft Calendar (part of Outlook / Microsoft 365) is used to manage appointments, meetings, and schedules.\
With this node, you can automatically create or update calendar events based on your data.

For each row in your data, one calendar event is created or updated in the **default calendar** of the specified mailbox.

#### How it works

1. Select a valid **Connection** to Microsoft
2. Open **Advanced** to configure:
   * The mailbox (email)
   * Start and end date/time
   * Timezone
   * Subject, location, and optional body
   * Optional update behavior
3. For each input row, an event is created or updated
4. The output contains event details and the original data

***

### Configuration Options

| Setting    | Required | Description                                                                         |
| ---------- | -------- | ----------------------------------------------------------------------------------- |
| Connection | Yes      | Select a Microsoft Office 365 connection or an OAuth2 connection (Microsoft Graph). |
| Advanced   | Yes      | Opens a configuration screen where you define all calendar mappings and settings.   |

***

### Advanced Configuration

Within the **Advanced** screen, you configure how your data maps to a calendar event.

#### Required fields

* **Email** → Mailbox where the event will be created
* **Start** → Start date and time
* **End** → End date and time
* **Time zone column** → Timezone (e.g. `W. Europe Standard Time`)
* **Subject column** → Title of the event

#### Optional fields

* **Location** → Event location
* **Body** → Event description (supports HTML)

***

### Create vs Update

The node can either create new events or update existing ones.

#### Create (default)

* A new event is created for each row
* This happens when **Update Existing** is disabled

***

#### Update Existing

When enabled:

* If no Event ID is provided → a new event is created
* If an Event ID is provided → the node attempts to update that event
* If the event no longer exists → a new event is created instead

***

### Output

The node creates a new output table. Each row represents a processed calendar event and includes:

| Column      | Description                      |
| ----------- | -------------------------------- |
| Id          | Microsoft event ID               |
| Email       | Mailbox used                     |
| StartTime   | Event start time                 |
| EndTime     | Event end time                   |
| TimeZone    | Timezone used                    |
| Location    | Event location                   |
| Subject     | Event title                      |
| BodyPreview | Preview of the event description |

Additionally:

* All original input columns are included

***

### Tips & Best Practices

* The connection must have permission to access the mailbox calendar
* Each input row results in **one calendar event**
* Events are created in the **default calendar** of the mailbox

***

### Changelog

| Version | Date         | Change                               |
| ------- | ------------ | ------------------------------------ |
| 1.0     | May 28, 2026 | Initial documentation version added. |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://academy.any2info.com/any2info-academy/no-code-platform/data-studio/data-hubs/toolbox/import-and-export/erp/export-to-microsoft-calender.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.