From ebb1f29cbfe264374323bb354b40e240805dd286 Mon Sep 17 00:00:00 2001 From: charitra-prem Date: Tue, 3 Nov 2026 13:17:28 +0530 Subject: [PATCH] Add Zoom integration guide Needed for the Zoom App Marketplace submission of the Fluso Zoom app: Zoom requires a guide on our domain covering how to add, use and remove the app. Adds /integrations/zoom to App setup and links it from Apps & MCP. --- AGENTS.md | 2 +- content/docs/features/mcp.mdx | 2 +- content/docs/integrations/meta.json | 2 +- content/docs/integrations/zoom.mdx | 95 +++++++++++++++++++++++++++++ 4 files changed, 98 insertions(+), 3 deletions(-) create mode 100644 content/docs/integrations/zoom.mdx diff --git a/AGENTS.md b/AGENTS.md index 934b98a..0697edd 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -13,7 +13,7 @@ The navigation keeps Home first and sorts the top-level sections alphabetically. Agents follows the user journey. Other sections keep their existing order: - **Agents (Beta)** - `/developers/*`. Start with a familiar task, then improvement and scheduling. Keep Examples and More about Agents (`/developers/guides/*`) collapsed by default. Introduce features when they help the reader's current task. Keep prompts natural and explain terms before using them. -- **App setup** - `/integrations/{github, gmail, google-calendar, slack}`. Per-app permissions and prompts, not feature pages. All of them connect through the Apps tab of the Add MCP dialog. +- **App setup** - `/integrations/{github, gmail, google-calendar, slack, zoom}`. Per-app permissions and prompts, not feature pages. All of them connect through the Apps tab of the Add MCP dialog. - **Deployment models** - `/deployment-models`. Current availability and operating boundaries for Fluso Cloud, dedicated AWS VPC, planned Azure VNet, and scoped on-premises deployments. - **Features** - `/features/*`. Approvals and permissions, Apps and MCP servers, Chat, Confidential mode, Imports, Memory, Projects, Skills, and Tasks. - **Fluso API** - `/api/*`. Start with access and a first request. Keep Cloud and daemon credentials and administration separate. Document shared workflows once under Use the API. Lead with a useful task, runnable requests, and the expected result. Reuse the deployment's example helpers. Put protocol details and recovery rules beside the step that needs them. Each deployment's `/docs` and `/v1/openapi.json` own exact request and response schemas. Keep endpoint tables collapsed after the workflow. Preserve old API URLs with redirects. diff --git a/content/docs/features/mcp.mdx b/content/docs/features/mcp.mdx index 0a4a81e..293c66f 100644 --- a/content/docs/features/mcp.mdx +++ b/content/docs/features/mcp.mdx @@ -160,4 +160,4 @@ Each row shows the connection's status. The three-dot menu holds the two actions ## Next -Per-app setup and prompts: [Gmail](/integrations/gmail), [Google Calendar](/integrations/google-calendar), [Slack](/integrations/slack), [GitHub](/integrations/github). For capabilities that shape *how* Fluso works rather than what it can reach, see [Skills](/features/skills). +Per-app setup and prompts: [Gmail](/integrations/gmail), [Google Calendar](/integrations/google-calendar), [Slack](/integrations/slack), [GitHub](/integrations/github), [Zoom](/integrations/zoom). For capabilities that shape *how* Fluso works rather than what it can reach, see [Skills](/features/skills). diff --git a/content/docs/integrations/meta.json b/content/docs/integrations/meta.json index 2008d59..2c10cca 100644 --- a/content/docs/integrations/meta.json +++ b/content/docs/integrations/meta.json @@ -1,3 +1,3 @@ { - "pages": ["github", "gmail", "google-calendar", "slack"] + "pages": ["github", "gmail", "google-calendar", "slack", "zoom"] } diff --git a/content/docs/integrations/zoom.mdx b/content/docs/integrations/zoom.mdx new file mode 100644 index 0000000..5660a23 --- /dev/null +++ b/content/docs/integrations/zoom.mdx @@ -0,0 +1,95 @@ +--- +title: Fluso for Zoom +sidebarTitle: Zoom +icon: video +description: Add, use, and remove the Fluso app for Zoom. Permissions, data handling, and support. +--- + +Connect Zoom and you can run your meetings from chat. Fluso schedules and moves calls, tells you who attended, reads the AI Companion summary, and finds the recording. This page covers how to add the app, use it, and remove it. + +## What it does + +Once Zoom is connected, you can ask Fluso to: + +- Schedule, reschedule, or cancel your Zoom meetings. +- Show your upcoming and past meetings and webinars, with participants and registrants. +- Read Zoom AI Companion meeting summaries. +- Find your cloud recordings. +- Add a registrant to a meeting or webinar. + +## Adding the app + + + + Open the Fluso app and sign in. If you don't have it yet, download it from [fluso.ai/download](https://fluso.ai/download). + + + Open **Plugins** in the sidebar and click **Add MCP**. You can also ask in chat: *"Connect Zoom."* Fluso then shows an access card with an **Authorize** button. + + + Click **Connect** on **Zoom** (or **Authorize** on the access card). + + + Sign in to Zoom and approve the requested permissions. + + + Zoom returns you to Fluso, and Zoom shows as connected. + + + +## Using the app + +Ask in plain words: + +> *"Schedule a 30-minute Zoom with sam@example.com tomorrow at 3pm."* + +> *"What meetings do I have this week?"* + +> *"Summarise yesterday's design review."* + +> *"Find the recording of Monday's standup."* + +In **Ask me first** mode, Fluso shows an approval card before it creates, changes, or deletes anything in Zoom. The card shows the Zoom tool and its arguments, so you can check them before you click **Allow once**. A saved **Always allow this tool** rule or **Allow everything** mode skips the card for that tool. See [Approvals and permissions](/features/approvals). + +## Permissions and data + +Zoom asks you to approve these scope groups when you connect: + +| Scope group | What Fluso can do | +| --- | --- | +| User | Read your profile and settings | +| Meetings and webinars | Read; create, update, and delete meetings; add registrants | +| Cloud recordings | List recordings; delete only when you ask | +| Contacts | Read | + +Fluso fetches Zoom data on demand to answer your request. It does not keep a copy of your Zoom content. OAuth tokens are stored encrypted and are deleted when you disconnect. + +The full policies are the [privacy policy](https://fluso.ai/privacy) and the [terms of service](https://fluso.ai/terms). + +## Removing the app + + + + In **Plugins**, open the Zoom row's three-dot menu and click **Disconnect**. This deletes the tokens Fluso stored for your Zoom account. + + + Sign in to the [Zoom App Marketplace](https://marketplace.zoom.us). Go to **Manage → Added Apps**, find **Fluso**, and click **Remove**. + + + +After removal, Fluso can no longer access your Zoom data. To request deletion of any associated data, email [privacy@premai.io](mailto:privacy@premai.io). + +## Support + +For help with the Zoom app, see [fluso.ai/support](https://fluso.ai/support). + +## See also + + + + How connections work, and connecting from chat. + + + Prep, notes, and follow-up around a meeting. + +