> 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/import-from-microsoft-calender.md).

# Import from Microsoft Calender

**Category:** ERP

**Version:** 1.0

**Last updated:** May 28, 2026

**Author:** Any2Info

***

### Description

The **Import From Microsoft Calendar** node allows you to retrieve calendar events from Microsoft Calendar.\
It uses Microsoft Graph APIs to securely access calendar data within Microsoft 365.

Microsoft Calendar (part of Outlook / Microsoft 365) is used to manage appointments and schedules.\
With this node, you can import events from the **default calendar** of a specified mailbox.

The node retrieves events based on a given date and returns selected event data such as subject, time, and location.

#### How it works

1. Select a valid **Connection** to Microsoft
2. Open **Advanced** to configure:
   * The mailbox (email)
   * The date from which events should be retrieved
   * The columns to include in the output
3. The node retrieves calendar events
4. The selected data is returned as a new output table

***

### 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 the mailbox, date filter, and output columns. |

***

### Advanced Configuration

Within the **Advanced** screen, you configure which events are retrieved and what data is returned.

#### Fields

* **Email** → Mailbox from which events are retrieved
* **Created from** → Date from which events are retrieved
* **Columns to import** → Select which fields should be included in the output

#### Behavior

* The node retrieves events from the **default calendar** of the specified mailbox
* Only the selected columns are included in the output
* The output structure is based on your column selection

***

### Filtering Behavior

The **Created from** field determines which events are retrieved.

**Important:**

* The filter is based on:
  * When the event was **created**
  * When the event was **last modified**
* It does **not** filter on the event’s start date

This means:

* Only events created **and modified after the specified date** are returned

***

### Output

The node creates a new output table.

Each row represents a calendar event and may include:

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

Only the columns selected in the **Advanced** configuration are included.

***

### Tips & Best Practices

* Use a recent **Created from** date to limit data volume
* Ensure the connection has access to the specified mailbox
* Select only the columns you need to improve performance

***

### 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/import-from-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.