在创建或修改 Google 日历活动时,用户可以选择快速创建 Google Meet 会议并将其与活动相关联。
添加后,活动参与者只需点击一下,即可轻松加入关联的 Hangout。
不过,如果用户想使用第三方会议(例如 WebEx)而不是 Google Meet,则流程会更复杂。通常,这需要用户在 Google 日历之外创建会议,然后将会议代码复制到日历活动说明中。活动参与者随后必须按照一组特定的步骤,使用提供的代码加入会议。
Google Workspace 加购项可帮助用户避免这种复杂性。您可以构建一个 Google Workspace 插件,通过第三方会议解决方案来扩展 Google 日历的功能。
每添加一个会议解决方案,Google 日历活动就会新增一个会议选项,让用户可以直接从 Google 日历创建和加入这些会议。
如果您是会议服务提供商,可以创建 Google Workspace 加载项来定义 Google 日历与您的产品之间的连接。然后,您可以在 Google Workspace Marketplace 中发布该插件,以便用户和管理员发现并安装它。
会议解决方案
会议解决方案表示用户可以加入的第三方会议类型。每种解决方案都会显示为用户在创建或修改 Google 日历活动时可以选择的会议选项。
插件可能定义的会议解决方案示例包括:
标准视频会议
纯音频会议
个人会议
公开直播的会议
第三方服务提供的任何类型的会议都可以有相关联的解决方案,并且解决方案集合可以捆绑在一个 Google Workspace 加购项中。
会议解决方案的运作方式
将会议解决方案添加到 Google Workspace 插件后,无需为其提供详细的界面。相反,每当用户创建或修改 Google 日历活动时,用户已安装的 Google Workspace 加载项中定义的任何解决方案都会显示为会议选项。
当用户选择会议解决方案时,该插件会使用其 API 连接到第三方会议系统,并创建会议,同时在会议和 Google 日历活动之间同步数据。如果稍后更新或删除活动,插件会检测到此情况,并在会议系统中进行相应更新。将会议附加到活动后,参会者便可通过 Google 日历加入会议。
插件可以选择性地提供一个设置页面,以便用户控制特定的会议行为。
会议数据
为 Google 日历提供会议解决方案的 Google Workspace 加载项需要特定信息(即会议数据),才能让用户加入第三方会议。在插件中定义会议解决方案时,您需要指定一个用于构建和返回 ConferenceData 对象的 onCreateFunction。ConferenceData 对象必须包含 Google 日历所需的所有会议数据,或者包含一个 ConferenceError 对象,用于描述与第三方会议系统通信时发生的错误。
[null,null,["最后更新时间 (UTC):2025-08-29。"],[[["\u003cp\u003eGoogle Workspace add-ons allow you to integrate third-party conferencing solutions (like WebEx) directly into Google Calendar, simplifying the process for users.\u003c/p\u003e\n"],["\u003cp\u003eThese add-ons create new conferencing options within Calendar events, letting users easily create and join third-party conferences without manually entering codes.\u003c/p\u003e\n"],["\u003cp\u003eConference providers can build and publish these add-ons to the Google Workspace Marketplace, extending the functionality of Google Calendar for their users.\u003c/p\u003e\n"],["\u003cp\u003eAdd-ons leverage conference solutions to define various conference types (video, audio, etc.) and handle communication between Google Calendar and the third-party system.\u003c/p\u003e\n"],["\u003cp\u003eConference data, including entry points and conference IDs, is used by the add-on to enable seamless joining of third-party conferences directly from Calendar events.\u003c/p\u003e\n"]]],["Conference providers can build Google Workspace add-ons to integrate their third-party conferencing solutions with Google Calendar. These add-ons allow users to create and join conferences directly within Calendar. When a user selects a conference solution, the add-on uses the conferencing system's API to create it and sync data. The add-on must provide \"conference data,\" including a conference ID, entry points, and parameters. The add-on can also supply error messages. Attendees can join these third party conferences directly from their calendar.\n"],null,["# Third-party conferencing overview\n\n| **Note:** This functionality was built for conference providers specifically, and was originally available as *[Calendar conferencing add-ons](/workspace/add-ons/guides/glossary#calendar_conferencing_add-on)*.\n\nWhen creating or editing a Google Calendar event, users have the option to\nquickly create a Google Meet meeting and associate it with the event.\nOnce added, event attendees can easily join the associated Hangout with a\nsimple click.\n\nHowever, if a user wants to use a third-party conference (such as WebEx)\ninstead of Google Meet, the process is more complex. Typically this\nrequires the user to create the conference outside of Google Calendar and then\ncopy a conference code into the Calendar event description. Event attendees\nthen must follow a specific set of steps to enter the conference using the code\nprovided.\n\nGoogle Workspace add-ons can help users avoid this\ncomplexity. You can build a Google Workspace add-on\nthat extends Google Calendar with third-party\n[*conference solutions*](#conference_solutions).\nEach added conference solution adds a new conferencing option for Calendar\nevents, allowing users to create and join those conferences directly from\nGoogle Calendar.\n\nIf you are a conference provider, you can create a\nGoogle Workspace add-on to define a connection between\nGoogle Calendar and your product. You can then publish the add-on in the\n[Google Workspace Marketplace](https://workspace.google.com/marketplace/),\nwhere users and administrators can discover and install it.\n\nConference solutions\n--------------------\n\nA conference solution represents a type of third-party conference that users\ncan join. Each solution is shown as a conferencing option a user can choose\nwhen creating or editing a Google Calendar event.\n\nExamples of conference solutions an add-on might define include the following:\n\n- a standard video conference\n- an audio-only conference\n- a personal conference\n- a publicly streamed conference\n\nAny type of conference that the third-party service provides can have\nan associated solution, and collections of solutions can be bundled together\nin a single Google Workspace add-on.\n\n### How conference solutions work\n\nWhen a conference solution is added to a\nGoogle Workspace add-on, there is no need\nto provide a detailed UI for it. Instead, whenever a user creates or edits a\nGoogle Calendar event, any solutions defined in the\nGoogle Workspace add-ons the user\nhas installed appear as conferencing options.\n\nWhen a user selects a conference solution, the add-on connects to the\nthird-party conferencing system using its API and creates the conference,\nsyncing data between the conference and the Google Calendar event. If the\nevent is later updated or deleted, the add-on detects this and makes the\ncorresponding updates on the conferencing system. Once a conference is attached\nto an event, attendees can join the conference from Google Calendar.\n\nOptionally, the add-on can provide a settings page to allow users to control\nspecific conferencing behavior.\n\nConference data\n---------------\n\nGoogle Workspace add-ons that provide conference\nsolutions to Google Calendarrequire specific information---*conference\ndata* ---in order to let users join third-party conferences. When you define\na conference solution in your add-on, you specify an\n[`onCreateFunction`](/apps-script/manifest/calendar-addons#ConferenceSolution.FIELDS.onCreateFunction)\nthat builds and returns a\n[`ConferenceData`](/apps-script/reference/conference-data/conference-data)\nobject. The `ConferenceData` object must contain either all the conference data\nGoogle Calendar needs, or a\n[`ConferenceError`](/apps-script/reference/conference-data/conference-error)\nobject that describes an error that occurred when communicating with the\nthird-party conferencing system.\n\nThe table below describes each type of conference data your add-on can use and\nlists the [ConferenceData service](/apps-script/reference/conference-data)\nobject that represents it. Each\n[`ConferenceData`](/apps-script/reference/conference-data/conference-data)\nobject your add-on uses must have all elements marked as **Required**:\n\n| Component | Type | Description |\n|-----------------------|-------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Conference errors | ` `[ConferenceError](/apps-script/reference/conference-data/conference-error) | **Required if an error occurred, in which case no other data is needed.** Use this to report a problem that happened when the add-on tried to connect to the conferencing system. |\n| Conference ID | `string` | **Required if not an error.** Use this ID to identify the conference within the third-party conferencing system. |\n| Conference parameters | ` `[ConferenceParameter](/apps-script/reference/conference-data/conference-parameter)`[]` | Use these key-value pairs to pass any system-specific information to and from the third-party conferencing system. For example, the system may require the email of the conference moderator, or a meeting key. |\n| Conference notes | `string` | Use this to append a text notice to the conference. Typically you use these to add instructions for conference administrators or legal notices. |\n| Entry points | [EntryPoint](/apps-script/reference/conference-data/entry-point)`[]` | **Required if not an error, in which case at least one `EntryPoint` must be defined.** Use `EntryPoint`s to describe a specific way to join the conference (for example, by phone, video, or SIP). Each entry point requires a URI and an [EntryPointType](/apps-script/reference/conference-data/entry-point-type). |\n\nFurther reading\n---------------\n\nThe following documentation can help you learn more:\n\n- **Build a Google Workspace add-on with conference solutions.**\n [Build conference add-ons](/workspace/add-ons/calendar/conferencing/build-conference-addons)\n provides an overview of the steps required to build a\n Google Workspace add-on that implements third-party\n conference solutions.\n\n- **Get a closer look.** View the\n [source code of a conferencing Google Workspace add-on example](/workspace/add-ons/samples/conferencing-sample).\n\n- **Learn more about what Apps Script can do.** Review the\n [Google Apps Script documentation](/apps-script).\n\n- **Wondering what other developers have built?** Visit the\n [Google Workspace Marketplace for Google Calendar](https://workspace.google.com/marketplace/category/works-with-calendar)."]]