> 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/project-management/meeting-events/reference-meeting-events/notifications-and-reminders.md).

# Notifications & Reminders

Motion automatically sends notifications for events to keep both hosts and invitees informed. These apply to events created in Motion, through booking links, or synced from external calendars.

**Behavior**

* **Confirmations** → When an event is created in Motion (or via booking links), confirmation emails are sent to all attendees.
* **Reminders** → Attendees receive reminder emails before the meeting begins. Default reminder times are pulled from the source calendar settings (e.g., Google/Outlook).
* **Reschedules** → If an event time changes, Motion updates the event on all connected calendars and sends updated notifications.
* **Cancellations** → Canceling an event in Motion or an external calendar removes it from both systems and notifies attendees.
* **Guests** → Additional invitees added to an event receive the same notifications as primary participants.

**Limitations**

* Reminder timing cannot be customized in Motion; it follows the defaults from the external calendar provider.
* Motion does not send push or in-app notifications for every event change — external calendar settings drive most attendee reminders.

**Why it matters**\
Notifications and reminders ensure that all participants know when and where events happen, while keeping Motion’s calendar in sync with external platforms.

<br>


---

# 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/project-management/meeting-events/reference-meeting-events/notifications-and-reminders.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.