Zoom Integration Guide

Overview

GetReal Protect integrates with Zoom through the Zoom Meeting SDK. The integration centers on the Bot App, a backend service that joins each in-scope meeting as a participant, streams the audio and video to GetReal Protect for forensic analysis, and surfaces findings in real time. The pieces fit together as follows:

• Zoom meeting — Host and participants join as normal.
• GetReal Bot — Joins via the Meeting SDK and streams audio and video to GetReal Protect.
• GetReal Protect — Performs forensic analysis on those streams.
• Alerts — Appear in the GetReal Protect console and route to the destinations defined in your integration configuration. If the optional Panel App is deployed, hosts also see alerts in-meeting.

Your security and fraud teams see results while the meeting is still running. The analysis works on the audio and video themselves, rather than inferring risk from how a participant behaves.

Setup is performed by a Zoom administrator working with your GetReal account team. Plan for 60–90 minutes of focused work once tenant registration is complete. Steps 4 and 6 apply only if you are deploying the optional in-meeting Panel App — skip them if you are deploying the Bot alone.

Prerequisites

Zoom side

• Zoom Business or Enterprise plan — required for Meeting SDK access and for real-time meeting data, including participant details.
• A Zoom administrator with full access to the Zoom Admin Portal and Zoom App Marketplace.
• Account-level and user-level settings configured (Step 2).

GetReal side

• Tenant provisioned by GetReal (Step 1).
• A GetReal administrator account.
• A list of users to monitor.

Setup

Step 1 — Register your tenant with GetReal

Your organization must be registered with GetReal before you configure any Zoom apps. Contact your GetReal account team and provide:

• Organization name
• Primary administrator email
• Intended Zoom account domain

GetReal will confirm when your tenant is provisioned. Do not begin Step 3 until you have received that confirmation.

Step 2 — Configure your Zoom account settings

Apply the following at the account level (Admin Portal), then again at the user level for each host whose meetings will be monitored.

Account-level settings act as the default for every host. Individual hosts can override them in their own user settings, but most never touch them — so in practice the account-level setting holds. If the Bot has trouble joining for a specific user, check that user's settings.

Recording & Transcript. Under Account Settings › Recording & Transcript › General, enable Record to computer files. The Bot requires this to access participant audio and video streams. Apply the same setting under each host's personal Settings › Recording › General.

Meeting security. Under Meeting › Security, disable both of the following, at the account level and again for each monitored host:

• Only authenticated meeting participants and webinar attendees can join meetings and webinars
• Only authenticated users can join meetings from Web client

These settings must be off because the Bot joins meetings without login credentials.

Scope the authentication change narrowly. Apply the change at the user or group level for the hosts you intend to monitor — avoid applying it organization-wide — and document it as part of your internal security review.

Step 3 — Create the Bot App in Zoom App Marketplace

Sign in to marketplace.zoom.us as a Zoom administrator. Under Develop › Build App, create a General App with the following configuration:

Scopes — the following five are required. The integration will not function if any are missing.

If you are also deploying the GetReal Outlook calendar plugin, add two more scopes to the Bot App. These are not needed for Zoom monitoring alone.

Scope	Purpose
meeting:write:meeting:admin	Create a meeting for a user.
meeting:delete:meeting:admin	Delete a meeting.

When the app is saved, copy the Client ID and Client Secret and paste them straight into the GetReal Protect console under Integrations › Zoom, then click Update — no need to store the secret anywhere in between. Step 5 covers the authorization that follows.

Zoom authorization requirement. Zoom requires apps that join meetings hosted outside their own account to be authorized. The standard deployment monitors meetings hosted by users inside your own Zoom account, where this typically does not apply. If you plan to monitor meetings hosted outside your account, confirm the authorization approach with your GetReal account team before going live.

Step 4 — Create the Panel App in Zoom App Marketplace (optional)

The Panel App provides an in-meeting interface for hosts. It is optional — if you are deploying the Bot only, skip to Step 5.

Create a second General App with the following configuration:

Domain allow list

• getreallabs.com
• app.getreallabs.com
• integration-api.getreallabs.com
• protect-api.getreallabs.com

Zoom App SDK APIs (under Features › Surface › In-client App Features, enable the Zoom App SDK and add):

• openUrl
• getMeetingContext
• getUserContext
• getMeetingJoinUrl
• getMeetingUUID
• getMeetingChatContext

Confirm URLs before submitting. The redirect, home, and domain values above match the standard production GetReal Protect deployment. Confirm them with your GetReal account team if you are deploying into a non-standard or regional environment.

Step 5 — Authorize the integration in GetReal Platform

In the GetReal Protect console, go to Integrations › Zoom. If you already pasted the Client ID and Client Secret and clicked Update in Step 3, they will be saved here — otherwise enter them now and click Update. Then complete the OAuth authorization flow when prompted and click Allow to grant the app.

Step 6 — Test the Panel App with a host (optional)

Skip this step if you did not deploy the Panel App in Step 4.

Before rolling the Panel out, use Zoom's Local Test flow to grant it to one or two hosts and confirm it appears in-meeting. The Panel is user-managed, so each host authorizes it once.

1. Open the Panel App in Zoom App Marketplace and go to the Local Test section.
2. Copy the Authorization URL.
3. Share the URL with a test host.
4. The host opens the URL and completes the grant flow.

After authorization, GetReal Trust Advisor appears in that host's Zoom Apps menu during meetings. Once you have confirmed it works, use the same authorization URL to grant the Panel to the remaining hosts you plan to monitor.

Step 7 — Assign the app in Zoom

The Bot App is admin-managed, so you control which users it applies to from the Zoom Admin Portal. Decide whether to make it available tenant-wide or to a specific set of users or groups, then assign it accordingly:

• Tenant-wide — the app applies across the entire Zoom account. Use this when you intend to monitor broadly.
• Specific users or groups — the app applies only to the users or groups you select. This is the usual starting point: begin narrow and expand as you build confidence. Common first scopes are talent acquisition hosts (candidate interviews), executive assistants scheduling on behalf of leadership, and finance or treasury teams running wire transfer or vendor calls.

You set this under the app's management settings in the Zoom Admin Portal, where availability can be set to all users or restricted to named users and groups. Zoom's exact menu labels shift over time, so confirm the current path in your Admin Portal, and coordinate the final list with your GetReal account team.

Support

GetReal Support. Open a ticket from the GetReal Protect console or contact your assigned customer success engineer. Include your tenant name and the time window of any session in question.

Zoom-side issues. For app creation, OAuth, or Meeting SDK issues on the Zoom side, engage Zoom Support in parallel and share the case number with your GetReal contact.

Need to Disconnect?

Removing the Bot App from Zoom App Marketplace, or deactivating the integration in GetReal Platform, stops the Bot from joining new meetings. If the Panel App was deployed, removing it ends host access to the in-meeting interface. Findings already in the GetReal Protect console are retained per your policy.