Zoom meetings
Akollo can read the details of meetings that have already ended in your Zoom account: when each meeting started and ended, how long it ran, how many people took part and which host held it. It never creates, changes or deletes a meeting and never touches registrants. Participant names and e-mail addresses are not read.
What is synced
| Data | Read by Akollo |
|---|---|
| Start and end time of ended meetings | Yes |
| Duration | Yes |
| Number of participants | Yes |
| Host who held the meeting | Yes |
| Meeting topic | Only when Store meeting topics is on (off by default) |
| Participant names and e-mail addresses | No |
| Registrants | No |
| Creating, changing or deleting meetings | Never |
What you need
- A Zoom account on the Pro plan or higher. The past-meeting report Akollo reads is not available on the free plan.
- A Zoom account administrator who can create an app in the Zoom App Marketplace.
Create the Zoom app
Start a Server-to-Server OAuth app
In the Zoom App Marketplace, choose Develop → Build App and pick Server-to-Server OAuth.
Name the app
Give the app a name, for example "Akollo meeting reader".
Add the scopes
Under Scopes, add exactly these two:
user:read:list_users:adminreport:read:list_meetings:admin
Activate the app
Activate the app. Note its Account ID, Client ID and Client secret.
Akollo signs in as this app. It does not ask any person to sign in to Zoom.
Connect it in Akollo
Store the client secret
Store the client secret in the Akollo vault for the Zoom connection.
Fill in the provider settings
Open Integrations → Connections, open the Zoom connection and fill in Provider settings:
- Zoom account ID and Client ID from the app.
- Vault reference: the vault id of the client secret.
- Store meeting topics: off by default. Meeting topics can contain customer names, so turn this on only if your policy allows it. When it is off, Akollo never keeps a topic.
- Days to read back: how far back the first read goes, 1 to 30 days (14 when empty).
Save
Save the settings. Changing the account ID or the client ID later needs the client secret again.
Warning
Your administrators must also allow zoom.us and api.zoom.us in the connector's network settings. Without both, Akollo sends nothing to Zoom.
How often it reads
Akollo checks for newly ended meetings every hour. Each check reads again from one day before the last meeting it saw. A meeting at a day boundary is therefore never missed, and a meeting read twice is not stored twice.
FAQ
No. The past-meeting report Akollo reads needs a Zoom account on the Pro plan or higher.
No. Akollo signs in as the Server-to-Server OAuth app and does not ask any person to sign in.
No. It reads how many people took part, not their names or e-mail addresses.
Store meeting topics is off by default, because topics can contain customer names. Turn it on only if your policy allows it.
As far as Days to read back says: 1 to 30 days, 14 when the field is empty.
Related pages
Connecting a BI tool over SQL
Let Power BI, Tableau or Excel read approved reporting datasets straight from the database, with its own read-only login.
Jira coexistence and transition
Define how Akollo works alongside Jira, or move selected work-management activities from Jira to Akollo with a reviewed transfer.