> For the complete documentation index, see [llms.txt](https://www.usemotion.com/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.usemotion.com/help/time-management/all-things-calendars/reference-all-things-calendars.md).

# Reference: All Things Calendars

## Introduction

Motion integrates directly with external calendars — Google, Microsoft Outlook, and iCloud — to unify your schedule. External events sync into Motion so you can see all commitments in one place, while Motion tasks and events display back into your external calendars for visibility. By combining your personal and work calendars with Motion’s AI scheduling, you get a single, accurate view of your time.

#### At a Glance

* **Supported providers** → Google Calendar, Microsoft Outlook, iCloud Calendar.
* **Provider differences** → Google, Microsoft, and iCloud have unique sync behaviors, especially with recurring events and reminders.
* **Integration** → Events flow into Motion from external calendars; Motion tasks and events display back externally for visibility.
* **Permissions** → Calendar connections require read/write access so Motion can create and update events.
* **Benefits of displaying tasks externally** → Keep teammates and personal tools aligned by seeing Motion tasks directly on your standard calendar.
* **Limitations** → Sync delays, all-day event defaults, and recurrence patterns may depend on your external provider.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.usemotion.com/help/time-management/all-things-calendars/reference-all-things-calendars.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.