Meetings

When you need to recover a decision or prepare for a call, use meeting transcripts together with related messages, files and notes. Your agent can turn those sources into a brief with references showing what was said, when and in which meeting.

A transcript is the text of a conversation; a recording is its audio or video. Meeting information also includes the date, title and available participant records. Zoom supplies these sources through its API or transcript files you import. You attend calls in Zoom; the command-line tool gives your agent access to the saved information.

Find a discussion or decisionCopy Anchor Link

Ask your agent to identify the right meeting before summarising it:

Find meetings about Research Example from the last month. Show dates and the passages about the launch decision, with source references. Distinguish recorded attendees from people only mentioned. Tell me which transcripts are missing.

The agent checks meeting information, searches available transcripts and opens the matching passages. A useful answer gives the meeting, date, quotation or faithful paraphrase and its source reference. A missing transcript or an empty search result does not establish that the discussion never happened. Search and evidence explains word search, source references and index coverage; search by meaning needs a configured search component.

Connect meetings to your other sourcesCopy Anchor Link

Use one project for the same work across meetings, messages and documents. Keep its short key and explicit aliases together rather than creating a new project for every spelling. Tags are labels for finding related material; notes hold your own context. A person link connects an observed participant to a person you selected; matching names alone do not establish identity.

Collect the meetings for Research Example, including its existing project aliases. Check the canonical project and current tags before proposing labels. Show possible tag synonyms for review. Combine passages with linked people, my notes, related messages and imported Google Drive documents. Cite every conclusion and propose uncertain links before saving.

The agent selects the canonical project and searches its stored name, key and explicit aliases for cited meeting candidates, including meetings that have not been linked yet. It also reads confirmed membership and related labels alongside the other available sources. Review the cited passages before accepting a project association. The alias search reads the existing index; after importing new transcripts, run ordinary word search to index them first. You review uncertain links and new labels. If you start with one meeting and do not know its project, suggest existing projects from its title and cited transcript evidence. Use the search hit’s meeting field as the parent reference; a transcript ref identifies a passage. Suggestions remain unconfirmed until reviewed.

Use Memo for notes, tags, facts and project records, organising sources for the common approach, and Google Drive to import the documents you want included. An existing calendar event can be linked explicitly; an upcoming Zoom meeting is not itself a synchronised Google or Outlook calendar.

Prepare for the next meetingCopy Anchor Link

Find my next Zoom meeting with Alice Example. Prepare a brief from earlier meetings in the series, linked project sources and participant context. List confirmed decisions, open questions and possible follow-ups with evidence. If a project or person is uncertain, show candidates and reasons. Keep the meeting and stored links unchanged.

The agent first discovers a bounded page of candidate series in Zoom, then verifies the selected series and searches stored context. Old or missing inventory dates are hints, not proof of a future call. This list does not include every calendar invitation. Check that the brief names the intended meeting and separates confirmed decisions from suggestions. Ask it to show missing periods, transcripts or documents. Upcoming Zoom meetings covers schedule and invitation reads; your agent assembles the brief from the sources you choose. For a recurring series, confirm the actual next occurrence; its original start date alone does not verify the next call. If permissions prevent that check, mark the date as unverified.

For one selected series, prepare cited context with zm personal meetings prepare <series-id> --json. It reads the upcoming time from Zoom and joins bounded stored prior calls, observed people, confirmed projects, accepted facts and directly sourced tasks. It also includes related stored calls through existing person links or confirmed projects, within the selected account and history window. Use the provider's numeric series ID, not the internal stored meeting ID. knowledge.items adds accepted facts about those linked people and confirmed projects, including decisions recorded outside the meetings. Keep their fact: references so the agent can retrieve and check the evidence. notes.items separately adds owner-written notes and annotations about included earlier calls and those linked people/projects, retaining note: references, meeting associations, revisions and coverage. A meeting-scoped note must link to an included call in this account; sharing a project alone does not include another meeting's notes. Keep these comments distinct from accepted facts, and check notes.coverage for omitted notes and sources that were not rechecked.

For one existing project you choose, add --project RES using its saved name, key or alias. project_evidence.pages then adds cited word matches from this account and history window, including unlinked meetings, separately from confirmed project membership. Repeated passage refs across aliases are the same evidence. Check pending indexing, output limits and project_evidence.continuation; continue with the existing project-evidence search even after an empty page when more remains. This does not infer or confirm the upcoming call's project. You can also choose stored message accounts, mail accounts and document folders for this profile. Ask the agent to include those sources with a literal word query; no source is selected automatically. A grant covers a whole account or folder, so choose the scope you intend. Preparation returns the excerpts separately in communications.items; communications.coverage keeps the selected identities, dates, indexing gaps, read limits and continuation. Conflicting dated statements stay separately cited rather than silently becoming a new accepted decision.

Documents, mail and messages are not searched unless explicitly requested through those configured sources. Unselected project vocabularies are not searched; the agent can investigate them separately. Preparation neither fills missing indexes nor downloads absent transcripts, and matching names never creates a person link. See source limits and continuation when the brief has gaps.

Keep useful findings afterwardsCopy Anchor Link

Ask for a reviewable list of decisions, promises, important statements and follow-up tasks, each with a meeting passage. Check who actually attended and which person a speaker represents before saving an identity link. Reuse an existing project and label when they fit.

With terminal access, your agent can stage the meeting's decisions and follow-up tasks as a review batch in Memo. The meeting must already have a confirmed project link. Staging creates no facts or tasks: read the cited passages and the preview, then personally confirm the candidates you want to keep. The other new candidates are rejected together.

An exact retry reuses its receipt and accepted records. If the transcript or project links change before review, ask for a new preview. An inferred follow-up stays distinguished from an explicit commitment, and unknown dates or assignees stay absent. See Review meeting findings in Memo for the owner commands and limits.

More controlCopy Anchor Link

Read saved meetings and list the upcoming Zoom schedule. Replace personal with your profile name and 1 with an ID from your list, and replace the fictional passage reference with a transcript search hit's ref. The project key RES and identity ID 12 are also fictional; select existing records from Memo and participant results.

zm personal meetings list --json
zm personal meetings show 1 --json
zm personal meetings transcript 1 --json
zm personal search meetings "launch decision" --json
zm personal meetings projects evidence RES 'identity_id:12 started_at:[2026-09-14 TO 2026-10-14]' --limit 20 --json
zm personal meetings projects scan meeting:1/2 --cues 20 --json
zm personal meetings passage meeting:3/15/20/4 --before-n 3 --after-n 4 --format markdown
zm personal meetings scheduled --limit 20 --json

Search uses the data available in the selected profile. If it is missing, pull or import the required transcripts before relying on the answer. zm personal meetings passage shows the surrounding stored lines with source references; it does not fetch missing Zoom data.

Related guidesCopy Anchor Link

Start with Zoom setup, or continue with connecting and organising your sources once the meeting passages are available.