> For the complete documentation index, see [llms.txt](https://library.zoom.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://library.zoom.com/technical-library/zh-tw/guan-li-yuan-zhuan-qu/third-party-integrations/zoom-calendaring-integration-explainer.md).

# Zoom 行事曆整合說明

Zoom 的行事曆整合如何運作，包括支援的提供者，以及 Zoom 與已連接用戶端之間的驗證流程。

## 概覽

Zoom 行事曆整合可將 Zoom 連接到第三方行事曆供應商，讓使用者無需在應用程式之間切換，即可直接在 Zoom 用戶端和會議室系統中檢視與管理行事曆事件。

Zoom 支援與 Microsoft 365、Microsoft Exchange Server 和 Google Workspace 的行事曆整合。當行事曆整合啟用時，Zoom 的 Web 行事曆服務會負責所有已連線端點的驗證、權杖管理和事件同步——包括桌面和行動應用程式、Zoom Rooms，以及符合標準的 H.323/SIP 會議室系統。雙向行事曆同步預設為啟用，可確保在 Zoom 或連線的行事曆供應商中所做的變更，都會自動反映到雙方。

本文件說明行事曆整合的運作方式，描述各類端點的資料流程與安全性模型，並提供 Microsoft 和 Google 環境的設定指引。

{% content-ref url="/pages/b363807a8037be45d29ba26c1607907c9df76d40" %}
[Zoom 行事曆概觀](/technical-library/zh-tw/guan-li-yuan-zhuan-qu/third-party-integrations/zoom-calendaring-integration-explainer/zoom-calendaring-overview.md)
{% endcontent-ref %}

{% content-ref url="/pages/ddf78ee1734b83937b529f4534ba57ffdb932952" %}
[Zoom 行事曆端點](/technical-library/zh-tw/guan-li-yuan-zhuan-qu/third-party-integrations/zoom-calendaring-integration-explainer/zoom-calendaring-endpoints.md)
{% endcontent-ref %}

{% content-ref url="/pages/62e2f89589c48541d1017bbf0593bb390863fde7" %}
[提供者特定詳細資訊](/technical-library/zh-tw/guan-li-yuan-zhuan-qu/third-party-integrations/zoom-calendaring-integration-explainer/provider-specific-details.md)
{% endcontent-ref %}

{% content-ref url="/pages/34227dfceed0e9f4e967c4496648f0e445a9e855" %}
[附錄](/technical-library/zh-tw/guan-li-yuan-zhuan-qu/third-party-integrations/zoom-calendaring-integration-explainer/appendix.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://library.zoom.com/technical-library/zh-tw/guan-li-yuan-zhuan-qu/third-party-integrations/zoom-calendaring-integration-explainer.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.