> For the complete documentation index, see [llms.txt](https://docs.daylite.app/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.daylite.app/help/mac-fundamentals/calendars/google-calendar-sync.md).

# Google Calendar Sync

Keep a Google calendar and a Daylite category in two-way sync — no double-entry.

If you live in Google Calendar but run your business in Daylite, you're probably keeping two calendars in your head. Google Calendar Sync ends that. Pair one Google calendar with one Daylite category and everything flows both ways, automatically — book a meeting in either app and it shows up in the other, edits and all.

{% embed url="<https://www.youtube.com/watch?v=JKgLrOZRV8s>" %}

Once it's on, you get to:

* **Stop double-booking yourself.** Every meeting lives in both calendars, so your availability is always right no matter which app you're looking at.
* **Book from anywhere.** Create an appointment on your phone in Google Calendar and it's waiting for you in Daylite at your desk.
* **Sync only what belongs in Daylite.** Pair just the calendars you want mirrored and leave your personal one out — or run several syncs at once, each Google calendar mapped to its own Daylite category.
* **Put meetings in context.** Link synced Appointments to the contacts, opportunities, and projects they belong to, so your team sees the full story behind every meeting.
* **Keep the team in the loop.** Synced Appointments are visible across your Daylite team by default — and you control exactly who sees what.

Each sync pairs **one Google calendar** with **one Daylite category**, and covers past and future events alike. Your personal calendar only enters Daylite if you deliberately pair it, so keeping work and personal separate is just a matter of which calendars you choose to sync.

{% content-ref url="/pages/921a0f2385fef30513b7a2a8d44ae445b6d61374" %}
[Set up Google Calendar Sync](/help/mac-fundamentals/calendars/google-calendar-sync/set-up-google-calendar-sync.md)
{% endcontent-ref %}

{% content-ref url="/pages/18714ef5f1183fd10722ca67a912094310a5a990" %}
[How Google Calendar Sync Works](/help/mac-fundamentals/calendars/google-calendar-sync/how-google-calendar-sync-works.md)
{% endcontent-ref %}

{% content-ref url="/pages/y4khZ7xwTXnYhpXKydjp" %}
[Remove a Google Calendar Sync](/help/mac-fundamentals/calendars/google-calendar-sync/remove-a-google-calendar-sync.md)
{% endcontent-ref %}

{% content-ref url="/pages/Z4NEqRgJp4UCInGCASVe" %}
[Delete or Deactivate a Category Synced with Google Calendar](/help/mac-fundamentals/calendars/google-calendar-sync/delete-or-deactivate-a-category-synced-with-google-calendar.md)
{% endcontent-ref %}


---

# 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://docs.daylite.app/help/mac-fundamentals/calendars/google-calendar-sync.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.