> For the complete documentation index, see [llms.txt](https://help.paintscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.paintscout.com/support/integrations/calendar-and-scheduling.md). # Calendar & Scheduling Connect Google Calendar for one-way or two-way sync of sales events with PaintScout. Connect PaintScout to Google Calendar to keep sales events in sync. You can use one-way or two-way sync, depending on how you want appointments to flow between both calendars. PaintScout currently supports Google Calendar for calendar sync. This section covers how to connect it, choose a sync direction, and control what your team can see in PaintScout. ## How calendar sync works Google Calendar sync supports: * **PaintScout → Google Calendar** — Send PaintScout sales events to Google Calendar * **Google Calendar → PaintScout** — Show Google Calendar events inside PaintScout * **Two-way sync** — Keep both calendars aligned automatically If you also manage appointment scheduling inside PaintScout, see [Sales Calendar & Events](/support/operations/events-and-calendar.md). ## In This Section * [Google Calendar](/support/integrations/calendar-and-scheduling/google-calendar-integration.md) — Connect Google Calendar, choose a sync direction, and control event visibility in PaintScout --- # 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://help.paintscout.com/support/integrations/calendar-and-scheduling.md?ask=&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.