Connect Zoom
Create a Server-to-Server OAuth app in your Zoom account and connect it to Bottega, so attendance syncs automatically after every live.
On this page8 sections
Bottega reads attendance from Zoom through a small private app that you create in your own Zoom account. Zoom calls this type of app a Server-to-Server OAuth app. It is never published, and attendees never see it. You do this once per Zoom account, and it takes about 15 minutes.
- A Zoom account on the Pro plan or higher. Bottega's attendance comes from Zoom's participant reports, and Basic (free) accounts can't use reports or require registration.
- Your lives are hosted by a paid user in that account. Zoom only creates reports for meetings a paid account hosts.
- The Zoom Webinars add-on, but only if your lives run as Zoom Webinars rather than Zoom meetings.
- In Bottega, a role that can edit Settings › Zoom.
Who can create the app
Zoom account admins can create the app. Anyone else needs a role that allows it, which an admin grants in the Zoom web portal.
Tick View and Edit for Server-to-Server OAuth app. The person who builds the app also needs role permission for every scope they add, and the scopes Bottega uses are admin-level. If you aren't an admin, it is usually quicker to ask one to build the app.
If the app owner's role changes later, the scopes in the app change with it. Build the app under an account that will stay an admin.
Sign in to the Zoom App Marketplace
Go to
marketplace.zoom.usand sign in with the Zoom account that hosts your lives. The Zoom App Marketplace link in Bottega's Settings › Zoom goes to the same place.Open Build an app
Open Develop and choose Build an app.
Choose Server-to-Server OAuth app
Pick Server-to-Server OAuth app and press Create. Other app types won't work, because Bottega signs in with the app's own credentials rather than a person's.
The app has five pages, which you work through in order: App credentials, Information, Feature, Scopes and Activation.
The App credentials page shows three values. Each one has a field with the same name in Bottega.
| Zoom shows | Bottega field | What it is |
|---|---|---|
| Account ID | Account ID | Your Zoom account. It isn't your Zoom user ID. |
| Client ID | Client ID | The app itself. |
| Client secret | Client secret | The app's password. Bottega stores it encrypted and never shows it again. The field says Saved instead. |
Paste the three values
Copy each value from Zoom and paste it into the matching field in Settings › Zoom.
Press Save & test
Save & test appears in the save bar as soon as you change a field. Bottega saves the values and asks Zoom for access. At this point the test fails with a message that the Zoom app is switched off. That's expected, because you activate the app on the last page. Leave Bottega open and carry on in Zoom.
If you create a new Client secret in Zoom later, paste it here and save again. To keep the saved secret, leave the field empty.
Zoom asks for a few details about the app, such as its name, a short description, your company name and a developer contact. Name the app “Bottega” and describe it as something like “Attendance sync for our webinars”. Zoom needs the developer contact name and email before it lets you activate the app.
The Feature page is where you turn on event subscriptions, which power the live viewer count on Home. It's optional. You can follow Show the live viewer count now or once the connection works.
Scopes are the permissions the app has. On the Scopes page, add each scope below. Searching for the exact name is the quickest way to find it, and each name here has a copy button.
Required for Zoom meetings
| Scope | What Bottega uses it for |
|---|---|
meeting:read:meeting:admin | Checks that the meeting behind each live exists in your account. |
meeting:read:list_past_instances:admin | Finds each live's meeting after it ends. |
report:read:list_meeting_participants:admin | Reads who joined, when, and for how long. |
Optional
| Scope | Add it if you want |
|---|---|
meeting:read:participant:admin | The live viewer count. It goes with event subscriptions. |
meeting:write:registrant:admin | Personal join links. Bottega uses it to register each person with Zoom. |
Only if you host Zoom Webinars
Zoom Webinars is a paid add-on, separate from meetings. If your lives run as Zoom Webinars (the join link has /w/ in it rather than /j/), add these as well.
| Scope | Needed for |
|---|---|
webinar:read:webinar:admin | Required. Checks the webinar behind each live. |
webinar:read:list_past_instances:admin | Required. Finds each live's webinar after it ends. |
report:read:list_webinar_participants:admin | Required. The webinar participants report. |
webinar:read:participant:admin | Optional. The live viewer count. |
webinar:write:registrant:admin | Optional. Personal join links. |
Apps made before 2024
New apps use the granular scope names above. An app made before 2024 may still use Zoom's older classic names, such as meeting:read:admin. If your app's Scopes page shows those, add the classic scope that covers each job.
| Classic scope | Covers |
|---|---|
meeting:read:admin | Meeting details and past meetings. Required. |
report:read:admin | Participant reports for meetings and webinars. Required. |
meeting:write:admin | Personal join links for meetings. Optional. |
webinar:read:admin | Webinar details and past webinars. Zoom Webinars only. |
webinar:write:admin | Personal join links for Zoom Webinars. Optional. |
Activate the app in Zoom
Open Activation and activate the app. If Zoom won't let you, go back to Information and fill in the developer contact name and email.
Test the connection in Bottega
Back in Settings › Zoom, press Test connection. Bottega asks Zoom for access, then checks each thing it will do. The badge next to the Zoom heading changes to Connected.
A successful test shows “Connected as” followed by the Zoom account email, then a list of checks. Each check calls Zoom the way Bottega will after a real live, using a meeting that can't exist, so nothing in your Zoom account is created or changed.
| Line | What it checks | If it isn't green |
|---|---|---|
| Find each live's meeting after it ends | Bottega can look up past meetings. Attendance needs it. | Add meeting:read:list_past_instances:admin (meeting:read:admin on older apps), then test again. |
| Read who joined and for how long | Bottega can read participant reports. Attendance needs it. | Add report:read:list_meeting_participants:admin (report:read:admin on older apps), then test again. |
| Create personal join links | Bottega can register people for a meeting. | Grey means the scope isn't there, which is fine unless you use personal join links. If you do, add meeting:write:registrant:admin (meeting:write:admin on older apps). |
| Zoom link on each upcoming live | Every upcoming live has a Zoom link in Bottega. | Add the missing links on the webinar's Setup tab. Without one, attendance and the live count can't be matched to that live. |
| Night 1: meeting found in this Zoom account | One line per upcoming live. The meeting in that live's link exists in this Zoom account. With personal join links on, it also checks the meeting requires registration with automatic approval. | Follow Prepare a Zoom meeting for Bottega, then test again. |
The test looks at your next 10 lives, including any that started in the last 6 hours. It doesn't check the Zoom Webinars scopes or the live viewer count. The live count gets its own check when Zoom validates the endpoint.
If the top line reads “Connected. Add user:read:user:admin to show the account email here.”, the connection works. That scope only lets Bottega show the account email, and nothing else needs it.
Check that it worked
- Settings › Zoom says “Zoom is connected” and “Attendance syncs as soon as each live ends, then again at 6 and 24 hours.”
- The first two checks are green, and each upcoming live shows its meeting as found.
- After your next live, the date's attendance label reads Zoom API · synced.
Read next
Something here out of date? Tell us and we'll fix the guide.