Zoom
Connect your company's Zoom account and every recorded Zoom meeting hosted by a member of one team becomes a Markdrop meeting in that team: the transcript, a summary, detailed notes of the whole call, decisions and action items, the people who joined, and everything else Meetings do (the Slack post, Team briefs and memory, Jira drafts, Ask). You can also bring in past Zoom meetings.
- One team. Pick the team, for example Sales. Only meetings whose host is a member of that team come in. Meetings hosted by anyone else are ignored, and Markdrop doesn't keep anything about them.
- Visible to that team. A Zoom meeting lands in the team, so the team's members can read it, and so can workspace admins, as with all team content. If the team is open, everyone in the workspace can read its meetings: the Zoom card suggests making it private.
- The host's meeting. Each meeting is imported as its host's, with the host as organizer. It isn't restricted to its attendees, so the whole team sees it.
- The host has a say. Personal meetings never come in, and a call where everyone is from your company waits for its host to decide. See Choose which meetings come in.
- Who joined. The meeting's attendees come from Zoom's participants list, with each person's email address when Zoom gives one (usually people in your Zoom account and signed-in guests). Addresses are used to recognise your workspace's members and, with HubSpot, to find attendees' contacts; they aren't shown on the meeting.
Zoom meetings need a cloud recording. The transcript comes from, in this order:
- Zoom's own audio transcript, when Zoom made one;
- else Zoom's closed captions, when the meeting had them;
- else, if a workspace admin turned on Transcribe and keep recordings, Markdrop transcribes the meeting's audio.
A meeting with none of these shows as No transcript with how to turn transcripts on.
Connect with one click
#The Markdrop app for Zoom connects your whole Zoom account in one step. You need a Markdrop workspace admin (or the owner) and a Zoom account admin, who may be the same person.
- In Markdrop, open Workspace settings › Integrations › Zoom.
- Pick the team Zoom meetings go to, for example Sales. You can change it later.
- Choose Connect Zoom. Zoom opens and asks a Zoom account admin to approve the Markdrop app for the account. If you aren't a Zoom admin, sign in to Zoom as one, or ask your Zoom admin to do this step.
- Zoom sends you back to the Zoom card, which now says Connected.
- Turn on transcripts. In the Zoom web portal, open Account Management › Account Settings › Recording. Turn on Cloud recording and, in its advanced settings, Create audio transcript. Lock both so every host has them.
You can also start from the Zoom App Marketplace: find Markdrop, choose Add, and approve it. Zoom then sends you to Markdrop, which asks which of your workspaces to connect. Pick one and choose Connect Zoom to this workspace, then pick the team in the Zoom card.
The app asks Zoom for read-only access:
| Permission | What Markdrop uses it for |
|---|---|
user:read:user:admin | Know which Zoom account approved the app, so its meetings reach your workspace and no other. |
user:read:list_users:admin | See the account's users, to know who hosted a meeting. |
cloud_recording:read:list_user_recordings:admin | List each team member's cloud recordings, for Import past meetings. |
cloud_recording:read:list_recording_files:admin | Read a meeting's recording files and download its transcript. |
meeting:read:list_past_participants:admin | Who joined each meeting, for its attendees. |
Markdrop never changes anything in Zoom. It downloads audio or video only if a workspace admin turns on Transcribe and keep recordings. One Zoom account connects to one Markdrop workspace.
If the card says Reconnect Zoom, Zoom stopped accepting the connection (for example, the app was removed in Zoom without telling Markdrop). Choose Reconnect Zoom and approve the app again.
Advanced: your own Server-to-Server app
#If your company prefers to create its own app in Zoom, or one-click connect isn't available, connect a Server-to-Server OAuth app instead. Imports, the team, and privacy work the same way. In the Zoom card, choose Advanced: use your own Server-to-Server app.
You need two people, who may be the same person:
- a Zoom account admin, or someone whose Zoom role has View and Edit for Server-to-Server OAuth app (Zoom web portal › User Management › Roles), who creates the app in Zoom;
- a Markdrop workspace admin or the owner, who pastes the app's details into Markdrop.
Zoom's Server-to-Server OAuth apps are available on paid Zoom plans; the participants list needs Pro or higher.
Set up the Zoom app
#Open Workspace settings › Integrations in Markdrop, choose Details on the Zoom card, and keep that page open: it shows the same steps, the scopes with copy buttons, and your workspace's own endpoint URL.
Do the steps in this order. Zoom only accepts the credentials of an activated app, and Zoom's Validate only works once the app is saved in Markdrop.
-
Create the app. Sign in to the Zoom App Marketplace as a Zoom account admin. Choose Develop › Build App, pick Server-to-Server OAuth App (not General App), and name it "Markdrop".
-
Fill in Information. Add a short description, the company name and a developer contact: Zoom requires them before it activates the app.
-
Add the scopes. On Scopes, choose Add Scopes and add these:
Scope What Markdrop uses it for user:read:list_users:adminSee the account's users, to know who hosted a meeting. cloud_recording:read:list_user_recordings:adminList each team member's cloud recordings, for Import past meetings. cloud_recording:read:list_recording_files:adminRead a meeting's recording files and download its transcript. meeting:read:list_past_participants:adminOptional: who joined each meeting, for its attendees. Without it, Markdrop uses the people who spoke in the transcript. Markdrop never asks for scopes that change anything in Zoom. It downloads audio or video only with Transcribe and keep recordings on.
-
Activate the app. On Activation, choose Activate your app. It must say the app is activated before you go on.
-
Copy four values. From App Credentials: the Account ID, Client ID and Client Secret. From the top of the Feature page: the Secret Token. The Secret Token and the Client Secret are different values.
-
Save them in Markdrop. In the Zoom card, paste the four values, pick the team, and choose Connect and check. The card says Connected.
-
Turn on Event Subscriptions, then validate. Back on Feature in Zoom, turn on Event Subscriptions and add a subscription named "Markdrop".
- Event notification endpoint URL: copy it from the Zoom card in Markdrop. It looks like
https://api.markdrop.in/api/v1/zoom/webhook/<your workspace id>. - Events: under Recording, add Cloud recording transcript files have completed (
recording.transcript_completed) and All recordings have completed (recording.completed). - Press Validate next to the endpoint URL. It turns to Validated. Save the subscription.
- Event notification endpoint URL: copy it from the Zoom card in Markdrop. It looks like
-
Turn on transcripts. In the Zoom web portal, open Account Management › Account Settings › Recording. Turn on Cloud recording and, in its advanced settings, Create audio transcript. Lock both so every host has them.
When you choose Connect and check, Markdrop asks Zoom for an access token with the app's credentials and makes a test call. If Zoom refuses the credentials, the card says so and nothing is saved. If a scope is missing, the card lists it: add it in Zoom, then save again (blank secret fields keep the saved ones).
If something doesn't work
#| What you see | What to do |
|---|---|
| Zoom didn't accept the Account ID, Client ID or Client Secret when you save | Check that the app is activated (step 4) and that it is a Server-to-Server OAuth app. Copy the three values again from App Credentials, without spaces, and check you didn't paste the Secret Token as the Client Secret. If someone regenerated the Client Secret in Zoom, paste the new one. |
| Zoom's Validate fails | Save the app in Markdrop first (step 6): Markdrop answers Zoom's check with the saved Secret Token. Check that the endpoint URL is the one in your Zoom card, ending in your workspace ID. If the Secret Token was regenerated in Zoom, choose Change credentials in the Zoom card and paste the new one, then validate again. |
| Activate your app is greyed out | Zoom still needs something on Information (description, company name, developer contact) or at least one scope on Scopes. |
| Build App or Server-to-Server OAuth App is missing | Your Zoom role can't build these apps. Ask a Zoom account admin to do the Zoom steps, or to give your role View and Edit for Server-to-Server OAuth app. |
| The card lists a missing scope | Add it on Scopes in Zoom, then save again in Markdrop (blank secret fields keep the saved ones). |
The Zoom card
#| The card shows | What it means |
|---|---|
| Not set up yet | Zoom isn't available on this Markdrop server. Nothing is wrong with your workspace. |
| Connect Zoom, or the setup steps and the form | This workspace isn't connected. Members who aren't admins see "A workspace admin connects Zoom here." |
| Connected | The team meetings go to, how many came in and when, whether Zoom has checked the endpoint, and the latest meetings from Zoom with their state. |
Each meeting from Zoom shows one state:
| State | What it means |
|---|---|
| Imported | It's a meeting in the team now. Choose it to open it. |
| Already here | It was imported before. Markdrop never makes the same Zoom meeting twice. |
| Transcribing | Markdrop is transcribing it from its recording, or waiting a few minutes for Zoom's own transcript first. It comes in on its own, and if Markdrop restarts while importing a meeting, it picks it up again within about 20 minutes. |
| No transcript | Zoom recorded it without a transcript or captions. Turn on Create audio transcript (step 8 of the Server-to-Server setup, or step 5 of one-click connect), or Transcribe and keep recordings; if Zoom makes the transcript later, the meeting comes in then. |
| Didn't import | Something went wrong, with the reason. Zoom meetings that didn't import can be brought in with Import past meetings. |
Meetings waiting for their host, and meetings that weren't brought in, aren't listed: the card only counts them (waiting for their hosts, not brought in). Their topics are their hosts' business. If some of your own meetings wait for you, the card says so, with Review.
Admins can change the team or Disconnect Zoom. With your own Server-to-Server app, they can also Change credentials (for example after rotating the Client Secret in Zoom).
Choose which meetings come in
#Each host decides what happens to their recorded meetings, and a few rules apply to everyone. For each recorded meeting, Markdrop checks, in this order:
- The topic says it's personal. If the Zoom topic has the word "personal" or "private" (any capitals), the meeting never comes in. Markdrop keeps only Zoom's ID for it, so it isn't looked at again.
- The host chose "Never bring them in". The meeting doesn't come in.
- Someone from outside your company was on it. The meeting comes in for the team. Outside means an email address that isn't a workspace member's and isn't at your company's domain (the domains of your members' addresses, never public ones like gmail.com).
- Everyone on it is from your company. The meeting waits for its host to decide.
- Otherwise (Zoom gave no address for someone, or no participant list): the host's choice decides.
The choice is When my Zoom meetings are recorded, in Settings › Account › Zoom (shown to members of the Zoom team):
| Choice | What happens |
|---|---|
| Share automatically (the default) | Meetings come into the team on their own, except internal-only calls, which wait for you. |
| Ask me first | Markdrop asks you before a meeting comes in, unless someone from outside the company was on it. |
| Never bring them in | Your recorded meetings never come in. |
Workspace admins can set it for each member of the Zoom team in the Zoom card (When each host's meetings are recorded).
Meetings waiting for you
#While a meeting waits, Markdrop keeps only its topic, time, duration and the names of the people who joined. It doesn't download the transcript, captions, audio or video, and nobody else sees it, not even workspace admins. You get one notification in your Markdrop inbox and, if your Slack account is linked to Markdrop, a Slack message with three buttons:
- Share with your team: the meeting comes in like any other Zoom meeting, into the team.
- Keep it just for me: the meeting comes in, but private to you. Nobody else can open it, not even its other attendees. You can share it later from the meeting.
- Skip: the meeting doesn't come in, and Markdrop keeps only Zoom's ID for it.
The same choices are on the To review tab of Meetings (the sidebar's Meetings shows how many wait for you) and on Zoom meetings to review (from the notification, the Zoom card's Review, or Settings › Account › Zoom). Only the meeting's host can decide; the Slack buttons only work for the person they were sent to. A meeting nobody decides about within 30 days is forgotten: Markdrop deletes what it kept. The recording stays in Zoom.
Meetings that came in before these rules stay as they are.
Import past meetings
#Workspace admins and the team's leads can bring in meetings recorded before Zoom was connected. In the Zoom card, choose Import past meetings:
- Pick Last 30 days, Last 90 days or Custom dates (up to a year).
- Markdrop lists the recorded meetings hosted by the team's members: the topic, date and time, duration, host, and where the transcript comes from: Transcript, Captions, Will transcribe (Transcribe and keep recordings is on) or No transcript. Meetings already in Markdrop show Open.
- The meetings that can come in are selected. Change the selection, then choose Import.
Meetings marked Will transcribe come back Transcribing and appear in Meetings a few minutes later. With Transcribe and keep recordings on, a meeting already in Markdrop without its recording shows Add recording: select it and choose Import to add the recording.
Past meetings come in like any other Zoom meeting, into the team, but as history: nobody is notified and they aren't posted to Slack on their own.
Past meetings follow the same rules. Meetings that won't come in are listed as Not brought in and meetings waiting for their host as Waiting for its host, both without their topic, and can't be selected. Importing an internal-only meeting puts it in its host's Zoom meetings to review, and the host gets one inbox notification for all of them (no Slack messages). A team member Zoom doesn't know by their email address is listed under the meetings so you can check their Zoom account.
Transcribe and keep recordings
#Off by default. A workspace admin turns it on in the Zoom card (Transcribe and keep recordings), and it applies to this workspace only. If the switch isn't in your card, it isn't available on this Markdrop server yet.
With it on:
- Meetings without a transcript are transcribed. When Zoom made no transcript and no captions, Markdrop sends the meeting's audio (never the video) to its speech-to-text provider, and deletes the downloaded audio right after. Speakers get names from Zoom's active-speaker timeline when Zoom provides it. When it doesn't, Markdrop AI works out who is speaking from the call itself (the meeting's topic, its host, the people who joined, introductions and people addressing each other by name), and names a speaker only when it is sure, and only with a name from the meeting itself; anyone else shows as "Speaker 1", "Speaker 2". Name them in a couple of clicks: the meeting asks everyone who can edit it, and its host gets one notification. With AI off for the workspace, speakers keep their numbers. For a meeting that just ended, Markdrop first waits a few minutes, because Zoom's own transcript often arrives a little after the recording, and Zoom's transcript is always preferred.
- Recordings are kept with their meetings. After a Zoom meeting comes in, Markdrop copies its video (shared screen with the active speaker when Zoom has it) and the meeting page's bar gets a Recording button that plays it right there.
- Captions and chapters. The recording plays with captions made from the meeting's transcript, each line marked with its speaker; turn them off with CC or C. When a speaker is renamed, the captions follow on the next play. Chapters come from the notes: each part of the call in Details (or each topic, without Details) marks the progress bar where it begins, and the current part's name next to the time opens the list. Both are made from what the meeting already has, so meetings imported earlier get them too, with nothing transcribed or summarised again.
- Times play the recording. On a meeting with a kept recording, select a time in the notes (like 12:34 next to a decision or an action item) or a line's time on its Transcript page, and the recording plays from that moment. Scrolled down the page, the player floats in the corner so you keep your place. Without a recording, times open the transcript as before.
- The same people as the meeting. Only people who can read the meeting can play its recording, through a link that expires after a few hours. If the meeting is restricted or its team private, so is the recording.
- On the workspace's own domain too. On a custom domain, a meeting page shows the same Recording button to signed-in readers who can read the meeting, with captions, chapters and the domain's accent color, and a line's time on the Transcript page plays from that moment. The meeting's other tools (Ask, attendees) stay on markdrop.in.
Transcribing and keeping recordings happen in the background, within fair-use limits; past the day's limit, meetings wait and continue the next day.
A meeting's stored video is deleted when the meeting is deleted (also with Disconnect Zoom… › Also delete the meetings imported from Zoom), when its page is deleted for good from the Trash, or when the person who imported it or a workspace admin chooses Recording › Remove recording. Turning the switch off stops new transcriptions and copies; recordings already stored stay with their meetings until removed. The recording in Zoom is never touched.
Removing the app
#You can disconnect from either side.
In Markdrop: in the Zoom card, choose Disconnect Zoom…. Markdrop deletes its access to your Zoom account and the Zoom import log, and stops bringing in meetings. With the Markdrop app for Zoom, it also removes the app from your Zoom account. To delete the meetings already imported too, tick Also delete the meetings imported from Zoom: they go to the workspace's Trash, where they can be restored for a while before they're gone for good.
In Zoom: a Zoom account admin signs in to the Zoom App Marketplace, opens Manage › Added Apps (or Apps on Account), finds Markdrop and chooses Remove. Zoom tells Markdrop, which right away deletes:
- Zoom's access and refresh tokens;
- the Zoom account's ID and the name and email of the admin who approved the app;
- the Zoom import log (topics, dates, hosts and states of the meetings it handled).
Meetings already imported are pages in your workspace, like any other meeting: they stay until a workspace admin or the person who owns them deletes them. To remove them all at once later, connect again and disconnect with Also delete the meetings imported from Zoom, or delete them one by one from Meetings. Deleting the workspace deletes everything in it.
After removing the app, the Zoom card says Zoom was disconnected. Choose Connect Zoom to connect again.
Privacy
#- Markdrop stores Zoom's access and refresh tokens, and a Server-to-Server app's Client Secret and Secret Token, encrypted. Only workspace admins see the card's setup details, and never the secrets.
- Every request from Zoom is checked with Zoom's signature. Requests that aren't signed by the Markdrop app for Zoom (or your own Zoom app) are refused, and each one reaches only the workspace connected to its Zoom account.
- Only meetings hosted by the team's members are read. For other meetings, Markdrop keeps nothing, not even the topic.
- A meeting waiting for its host keeps only its topic, time, duration and participants' names, seen only by the host, for at most 30 days. Nothing of it is downloaded until the host shares it. A personal or skipped meeting keeps only Zoom's ID.
- Markdrop downloads the transcript, or the closed captions when there is no transcript. It downloads audio or video only when a workspace admin turns on Transcribe and keep recordings: then only the audio of meetings without a transcript goes to the speech-to-text provider (and the downloaded copy is deleted right after), and each meeting's video is stored privately with the meeting.
- The transcript of an imported meeting is used to write its summary, decisions and action items, as for any meeting. See Removing the app for what is deleted and when, and the privacy policy for the whole picture.
- Questions or a problem? See Get help.
From an AI app
#With the MCP server, an assistant can check the connection (zoom_status, which also gives a workspace admin a one-click link to connect Zoom, and says whether Transcribe and keep recordings is on) and list and import past Zoom meetings (import_zoom_meetings, with where each one's transcript comes from, and adding recordings to meetings already here). With zoom_review, you can list your meetings waiting for your decision, decide one (share, private or skip), and read or change your choice (auto, ask or never). Imported meetings work with the meeting tools like any other meeting (get_meeting says has_recording and, with a kept recording, lists its recording_chapters). The switch itself is turned on in the Zoom card.