Create meetings and import Zoom transcripts
Manage upcoming meetings in the Room’s Meetings view. Use the Zoom import action in Terasu AI for transcripts that have already arrived. For capture during a meeting, see Live transcription.
Create a meeting from a Room
Open the Room’s meeting creation form and enter the title, start, end and participants. Check these details before creating an external meeting or sending invitations. See Zoom integration for recording requirements and Google Calendar integration for synchronization and Room matching.
Turn a received Zoom transcript into minutes
- Open Terasu AI in the destination Room
- Choose the Zoom import action from the input’s add menu
- Find the meeting in the Zoom meetings card using its title or date range
- Confirm the meeting and destination, then import it
- Open the resulting meeting-minutes page
The list contains meetings whose transcripts have reached Terasu from your connected Zoom accounts. It is not a list of every historical Zoom meeting. If a meeting is absent, check cloud recording, transcription and connection status.
Minutes are saved with internal-only visibility in the Room’s transcript folder. They contain a summary, decisions, ToDos and transcript. If the meeting was already imported, open its existing minutes rather than trying to create another copy.
Link a calendar event to a Room
Use the Room-linking action on a meeting card in Today. You can also remove an automatic match. Calendar synchronization settings may exclude events without meeting URLs.
Troubleshooting
| State | Check |
|---|---|
| Meeting is absent | Whether its Zoom transcript arrived, and whether filters match |
| Connection expired | Reconnect the affected Zoom account |
| Import failed | Read the reason and check for existing minutes before retrying |
| Transcript unavailable | Check the host’s Zoom connection and cloud recording |
Retention policies apply to transcripts and minutes. Import does not grant unrestricted sharing across Rooms.
List, create, and link meetings through MCP
MCP additions not included in the first release:
create_room_meeting、link_meeting_to_room、list_my_meetings、list_room_meetings、prepare_create_room_meeting、prepare_link_meeting_to_room. These additions are planned for a later release. Existing screen operations remain available.
Use list_my_meetings with rooms:read and ISO-date input.from/to, covering a positive range of at most 31 days. It returns meetings you organize or attend and meetings in your Rooms. Specific-Room tokens include only their permitted Rooms, excluding unlinked personal meetings. list_room_meetings takes input.roomId and includes transcript status and minutes-page metadata. Both default to limit: 25, with a maximum of 50; pass nextCursor back as cursor to continue. Optional Room suggestions report suggestionsStatus: unavailable_budget when their lookup budget is exceeded.
For creation, call prepare_create_room_meeting with input.roomId/title/startsAt/endsAt, optional participantEmails, requestRecording, and recordingConsentAcknowledged, plus a UTC-dated idempotencyKey: YYYY-MM-DD:UUID. Titles must contain non-whitespace text and fit 4096 UTF-8 bytes. At most 50 participant emails are accepted, each at most 254 characters. Creation requires rooms:write and active internal Room membership. Recording requests retain the existing Workspace policy and consent requirements.
Preparation does not save or contact providers. Review externalEffects for planned Zoom creation and Calendar invitations. Within ten minutes, call create_room_meeting with the same input and key, plus confirmation containing the returned operationId/payloadHash/approverUserId/expiresAt. Execution uses your active connections. Missing connections or Calendar write scope produce a local meeting without the corresponding meeting URL or invitations. Requesting recording does not mean recording has started or transcription is complete.
To link, call prepare_link_meeting_to_room with input.meetingId and destination input.roomId (null to unlink), plus the same key format. After review, pass identical input/key and the returned confirmation to link_meeting_to_room. Current organizer authority or membership in the original Room is required, along with destination Room membership. The server observes the update timestamp during preparation; you do not supply it. An unchanged link returns wasChanged: false.
For an unknown result, inspect get_mcp_operation using rooms:read, and check Zoom or Calendar when necessary. Zoom creation and the first local save may succeed while the Calendar invitation outcome is unknown. current: null does not prove non-execution. Do not automatically resubmit. Prepared writes do not overwrite concurrent changes to participants, Room links, cancellation, or deleted meetings. See Operate through MCP for the input format.
Create minutes from the recorder window
MCP additions not included in the first release:
create_meeting_recording、create_room_meeting、prepare_create_meeting_recording. These additions are planned for a later release. Existing screen operations remain available.
Use live transcription for audio captured during a meeting. Through MCP, prepare_create_meeting_recording then create_meeting_recording creates an unstarted session. Its creator opens the returned appPath to use that same session in the authenticated recorder window. Review both meeting scheduling through create_room_meeting and the person’s audio-capture steps.
Sync and import Zoom meetings through MCP
MCP additions not included in the first release:
import_zoom_meeting_transcript、list_my_zoom_meetings、prepare_import_zoom_meeting_transcript、prepare_sync_my_calendar_events、sync_my_calendar_events. These additions are planned for a later release. Existing screen operations remain available.
Use prepare_sync_my_calendar_events → sync_my_calendar_events for your calendar, and list_my_zoom_meetings → prepare_import_zoom_meeting_transcript → import_zoom_meeting_transcript for received Zoom transcripts. Review each preparation before confirming with identical input and the same operation key.
Sync requires rooms:write on an all-Room token. Its five-minute interval is shared across your workspaces; a skip does not mean the destination is up to date. Zoom listing requires files:read; import and its operation lookup accept files:write. Internal editing access to the destination Room is required. Import acceptance, analysis, and Page completion are separate states. Reconcile unknown outcomes with get_mcp_operation without resending.
Connections require personal browser consent. See Google Calendar integration and Zoom integration for connection inspection and operation requirements.