TAMID

Using TAMID with Zoom

Connecting Zoom, scheduling a meeting, and what happens to the recording afterwards.

What the integration does

TAMID schedules donor meetings on your own Zoom account, lets Zoom invite the donor, and — if you chose to record — files the transcript on that donor's history so the conversation is not lost. TAMID never hosts on its own licence and never emails a donor.

Connecting

  1. Open any donor in TAMID and find “Schedule a meeting”.
  2. Choose Connect Zoom. Zoom asks you to approve the permissions listed below.
  3. You return to TAMID connected. TAMID checks whether the account can record and transcribe, and says so plainly if it cannot.

Scheduling a meeting

  1. Give the meeting a title, a time and a length.
  2. Optionally write an agenda and talking points. These are yours — they are never sent to Zoom and never appear in the donor's invitation.
  3. Decide about recording. It is off unless you switch it on. If you do, TAMID shows you the sentence to say at the start of the call and keeps a record that it showed you.
  4. Schedule. Zoom emails the donor the invitation and the calendar file. If your plan cannot do that, TAMID tells you and gives you the link to send yourself.

During and after

How the data flows

Every call to Zoom is made by TAMID's server. No Zoom credential or token ever reaches your browser, and TAMID cannot join a meeting — there is no recording bot.

Architecture of TAMID's Zoom integration. The fundraiser's browser talks only to TAMID's server; that server holds the OAuth tokens and makes every Zoom API call. Zoom sends the donor the invitation and notifies TAMID by signed webhook when a recording is ready. Transcripts are stored per organisation in PostgreSQL with row-level security, and are sent to the AI provider only when a fundraiser asks for them.

Open the diagram at full size. It is generated from this application's own source, so it stays true: every box in it is a real route or table.

Permissions TAMID asks for, and why

ScopeWhy it is needed
meeting:write:meetingCreate the meeting on your account.
meeting:delete:meetingCancel it. Without this a meeting could be created and never withdrawn, leaving the donor holding an invitation to a call you cancelled.
meeting:write:registrantRegister the donor so Zoom sends the invitation. This is what lets TAMID avoid emailing donors itself.
user:read:settingsRead whether the account can record and transcribe, so the recording option is offered only when it would work.
user:read:userRead the account email and identifier, to attach the connection to the right person.
cloud_recording:read:list_recording_filesFind the transcript file for a meeting you recorded.
cloud_recording:read:recordingRead that transcript.

TAMID asks for nothing beyond these. It does not read your other meetings, your contacts, or recordings of calls it did not schedule.

Disconnecting

In Zoom: Settings → Installed Apps → TAMID → Remove. Zoom notifies TAMID and the stored connection and both tokens are deleted. Meetings already on your Zoom account are unaffected.

More

Support · Privacy · Terms of use

Last updated 31 August 2026. Questions about anything on this page: admin@tamid.ai.