On this page
INTEGRATIONS · ZOOM
Connect Zoom meetings
Connect a Zoom user through an app your organization owns. Assign the connection to personas for meeting tasks. Choose live meeting context and event-driven work separately.
Have the Zoom account ready
You need permission to create a General app in the Zoom App Marketplace. Your Zoom account owner or administrator can grant developer access. Keep the app private to your Zoom account. This setup does not provide distribution to other organizations.
Live context also needs Zoom Developer Pack credits and your account’s permission to share realtime meeting content. Meeting tools can work without live context. Review Zoom’s live-content prerequisites before enabling it.
1. Choose access
- Open Integrations → Services → Zoom.
- Choose Connect Zoom. Enter a Connection name.
- Under Zoom app, choose Create a new private app or your workspace’s existing app when offered.
- Start with reading access. Enable meeting management only if your personas should change meetings or use meeting controls.
- Enable live context only when you need incoming transcript, public meeting chat, or meeting events.
- Choose Continue.
Access follows the connected Zoom user and its granted permissions. Reading can cover that user’s authorized meetings. There is no selected-meeting access restriction in this setup. It does not grant account-administrator access.
2. Create your Zoom app
For a new app, review Required Zoom permissions. Choose Download Zoom setup file before opening the Zoom Marketplace.
- Choose Open Zoom App Marketplace. Sign in to the Marketplace with developer access.
- Choose Developer → Develop → Build from an app manifest.
- Choose Choose file. Upload the setup file from PersonaStack.
- Choose Create. Keep the app user-managed.
The setup file supplies the app settings and requested permissions. It contains no credentials. Live-event configuration happens after authorization. Importing the file alone does not enable incoming content. See Zoom’s manifest guide if your Marketplace layout differs.
Reuse an app or expand its access
For an existing app, compare Required Zoom permissions with the app’s configured scopes. Open that app in the Zoom Marketplace. Under Scopes, choose Add Scopes. Add and save any newly required permissions before choosing Authorize Zoom in PersonaStack. This also applies when you enable meeting management or live context on an existing connection.
Renewed consent does not add scopes to the Zoom app. They must already be configured there. See Zoom’s scope setup guidance. You do not need to create another app just to update scopes.
3. Authorize the Zoom user
- In your Zoom app, open Basic Information → App Credentials. Copy the Client ID and Client Secret into PersonaStack’s setup fields.
- If incoming content is selected, open the app’s Features → Access section. Zoom’s webhook documentation calls this the Add Feature page. Copy its Secret Token into PersonaStack’s Webhook Secret Token field.
- Choose Save credentials.
- Choose Authorize Zoom. Review and approve the requested permissions in Zoom.
- After returning, check the displayed Zoom user and account before continuing.
See Zoom’s app credentials guidance and webhook secret guidance if the labels differ. Copying the webhook secret does not require adding a manual event subscription. PersonaStack configures the user-specific subscription after authorization.
Keep app secrets in these fields. Do not put them in persona instructions, chat, shared templates, or support messages. Saved panels show whether secrets are configured without revealing their values.
To connect another user in the same Zoom account, select the existing app under Zoom app. You do not need to create that private app again. Each connection authorizes one user separately. Personas sharing a connection act as that Zoom user. They do not become separate Zoom users. Reconnecting must keep the same user and account. Create another connection for a different identity.
4. Complete live-content setup when selected
In Zoom, open Settings → Zoom Apps → Auto-start apps that access shared realtime meeting content. Choose your app and save. Start with meetings you own. Choosing attended or external meetings is a separate Zoom-side decision. An administrator may need to enable Share realtime meeting content with apps. The host can require approval. See Zoom’s host and admin controls.
Confirm I enabled auto-start for this app in Zoom. Choose Configure live events. PersonaStack configures events for this connected user. If Zoom rejects the setup, follow the displayed repair reason. Do not replace it with a manual account-wide subscription.
Choose Continue with meeting tools if live setup cannot finish now. This lets you finish the connection for separately authorized meeting tools. Live context and event wakes remain unavailable until their setup succeeds.
Authorization, event validation, and saved auto-start settings do not prove that a meeting is streaming. Check the live status during an eligible meeting. Missing credits or host approval can keep live context unavailable while separately authorized meeting tools remain usable.
5. Finish and assign personas
Choose Finish and check the saved identity and status. Open Persona Settings for each persona that should use the connection.
In Persona Settings, choose Integrations → Add integration. Search for the saved Zoom connection and click it. Wait for save feedback. Configuration and wake controls stay below the assigned connection. Leave Wake on incoming events off for personas that only need tools. A persona can use more than one connection. Name the intended Zoom user when a task could use several. Start with a small read-only meeting task before allowing changes.
Choose which events start work
When live receiving is ready, enable Wake on incoming events for each persona that should respond. Choose the supported meeting-started, meeting-ended, summary-ready, transcript-ready, or public-chat-prefix triggers. Wake is off by default. Assigning a connection alone does not start work.
Select the public-chat-prefix trigger and enter the prefix before testing it. Wait for the save feedback. A public-chat prefix is text you choose for that persona. It is not a native Zoom mention or spoken-name detector. A message from the connected human user can trigger it. Transcription packets do not each start a run. Paused personas do not catch up on missed events when resumed.
Understand the available context
- Meeting summaries, retained transcripts, and recordings depend on what Zoom generated and what the connected user can access. An unavailable asset is not evidence that the meeting had no content.
- Live context includes attributed transcript text, public everyone-chat messages, and participants observed by the live stream. It does not provide private chat or a complete attendance or invitation list.
- The rolling transcript holds at most five minutes and 64 KiB per active meeting. Chat includes up to 15 messages within the same five-minute rolling window. A connection supports up to 10 simultaneous live meetings. Check freshness, truncation, and gap notices.
- Live context is temporary. It does not provide a full archive or replay missed content. Content included in persona work follows the normal conversation and run-history rules.
- Voice or video participation, sending into meeting chat, Zoom Team Chat, and webinars are unavailable.
To request live context, use the exact meeting UUID supplied in the Zoom wake context. A meeting number or join link is not a substitute. The live-context tool does not list active sessions or discover their UUIDs. If that UUID is missing, do not guess it.
Repair or disconnect a connection
Read the saved connection’s attention reason. Use Resume setup for an incomplete draft. Use Replace credentials when the app credentials need replacement. Leave a saved secret empty to keep it. Changing shared app credentials affects every connection using that registration. Reconnect those users after replacement. For broader permissions, add the required scopes to the existing app before renewing Zoom consent.
For live-content problems, check credits, account controls, auto-start settings, the connected user’s presence, and host approval. An offline stream is not current context. Inspect uncertain meeting changes in Zoom before repeating them.
Choose Disconnect on the saved connection and confirm the named connection. Disconnecting a user connection stops its PersonaStack actions and incoming collection. Other users sharing the app registration keep their own grants. Zoom’s persistent auto-start settings remain in Zoom. Review them there when you want to stop Zoom from automatically starting the app.
To remove the saved app registration, use Private Zoom apps → Remove app. Review the affected connections. Disconnect every listed connection first. Removing the registration from PersonaStack does not delete the app in Zoom.
If you need help, share the connection name, time, and displayed error. Exclude app secrets, tokens, and private meeting content. See integration troubleshooting.
Need a hand? Contact the PersonaStack team.