> For the complete documentation index, see [llms.txt](https://docs.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.distro.so/integrations/zoom.md). # Zoom Zoom is a personal integration. Each host who needs their Zoom account opens **Settings → My Integrations → Zoom** and authorizes it. ## Use Zoom for meetings Select Zoom as the supported location on the event type. Ensure the intended host has a usable calendar connection as well as Zoom. Make a controlled booking and inspect the created conference link and calendar invitation. Connecting Zoom alone does not set every event's location. ## Register a webinar attendee Where available, the **Zoom Webinar** workflow action registers a prospect for the configured webinar. Choose the webinar host, then the webinar, and map the required attendee fields from the lead. Meeting conferencing and webinar registration are different operations. A successful meeting link does not prove the connected Zoom user can register attendees for a particular webinar. ## Troubleshoot Check the Zoom authorization, host account, webinar ownership and required provider permissions. Reauthorize if tokens are missing or expired. For workflow registration, inspect the provider result and registration details in Logs. A simulated registration is sample output; verify a controlled live attendee in Zoom before launching a campaign. Changing a conferencing connection does not retroactively prove all existing invitations have been updated. Inspect the affected booking if the provider changed after it was created. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.distro.so/integrations/zoom.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 `build a script that syncs our docs to a CMS` 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.