Meeting action items (Zoom, Google Calendar, GitHub)
A user asks: “Pull the transcript from yesterday’s sprint planning and put the
action items on our board.” The agent finds the meeting on the user’s Google
Calendar, downloads the Zoom cloud-recording transcript, drafts one task per
action item, shows the list, and once the user confirms opens each as an issue
in the repository they name and places it on the GitHub Projects board with its
fields set (Status: Triage, Source: Meeting by default).
Three first-party tool families do this. Each calls the vendor’s API directly with the user’s own OAuth token, obtained through the same connector flow the platform already uses for OAuth-gated MCP servers. Nothing is stored on the platform: no transcripts, no vendor tokens outside the AgentCore Identity vault.
| Catalog tool (grant per role) | Tools the agent sees | Vendor API |
|---|---|---|
google_calendar_meetings |
list_calendar_meetings |
Google Calendar v3, calendars/primary/events |
zoom_meeting_transcripts |
list_zoom_recordings, get_zoom_transcript |
Zoom v2, users/me/recordings, meetings/{id}/recordings, transcript download |
github_issues_local |
list_github_projects, list_github_repositories, create_project_tasks |
GitHub REST user/repos, repos/{owner}/{repo}/issues; GitHub GraphQL projectV2, addProjectV2ItemById, updateProjectV2ItemFieldValue |
The three are independent. Grant only Zoom + GitHub to a team that does not use Google Calendar; the agent asks for the meeting id instead.
1. Create the connectors (Admin → Connectors)
Section titled “1. Create the connectors (Admin → Connectors)”Create one connector per vendor. Each needs an OAuth app registered at the vendor with the callback URL the connector page shows after you create it as an authorized redirect URI.
| Connector | Provider type | Scopes to configure | Vendor-side notes |
|---|---|---|---|
| Google Calendar | https://www.googleapis.com/auth/calendar.readonly |
Custom OAuth parameters access_type=offline and prompt=consent, or Google issues no refresh token and users reconnect hourly. An existing Google connector (for example the Drive connector used by folder attachments) can be reused by adding this scope to it — every user is then re-prompted once for the widened scope. |
|
| Zoom | Zoom | Granular: cloud_recording:read:list_user_recordings, cloud_recording:read:list_recording_files. Classic: recording:read |
A user-managed OAuth app in the Zoom App Marketplace. Cloud recording and audio transcription must be enabled for the account, or no recording ever has a transcript. |
| GitHub | GitHub | repo (private repositories) or public_repo, and project |
A GitHub OAuth App. project is what lets the tool read boards and add items to them; without it the write opens the issues but reports every task as “created but not placed on the board”. Organizations with OAuth App access restrictions must approve the app before it can open issues in their repositories or see their boards. |
2. Bind each tool to its connector (Admin → Tools)
Section titled “2. Bind each tool to its connector (Admin → Tools)”Open each of the three catalog entries and set Required OAuth provider to the matching connector. This is the link the runtime uses: the tool calls the vendor with a token from that connector, and the user is asked to connect it the first time a tool runs. A tool left on “None” still appears for granted users but answers every call with “no connector configured”, so the gap is visible rather than silent.
Only the three meeting tools read this field on a built-in tool; leave it on “None” for every other built-in tool.
3. Grant the tools to roles (Admin → Roles)
Section titled “3. Grant the tools to roles (Admin → Roles)”All three rows are seeded enabledByDefault: false and not public. Grant them
to the roles that should have them. Users then turn them on in the composer’s
tool picker like any other tool, and the picker shows the “connect” affordance
until they have connected the vendor.
4. Turn the feature on
Section titled “4. Turn the feature on”Set CDK_MEETING_TASKS_ENABLED=true in the GitHub environment and run the
platform deploy. The flag reaches the AgentCore Runtime only; with it off the
tools are never built, whatever the catalog says.
What users see
Section titled “What users see”- The first call to a vendor pauses the turn on the standard consent card (“Connect Zoom”). After the popup completes, the turn resumes where it paused. Connections are managed under Settings → Connectors.
get_zoom_transcriptreturns the transcript as[HH:MM:SS] Speaker: textlines, with consecutive lines from one speaker merged. A transcript over 60,000 characters (roughly a 60–90 minute meeting) is cut, and the result says so.create_project_tasksis a two-step write. The first call reads the board, validates the repository, every task and every field value, and returns a preview that also lists the board’s single-select fields and their options; the model shows it and calls again withconfirm=trueonly after the user agrees in the conversation. The result links each issue it opened and says whether it landed on the board.
Board fields
Section titled “Board fields”The board is given as owner/number (my-org/7) or its URL; list_github_projects
returns both for an organization or user. Each task becomes an issue in the
repository the user picks (a board usually spans several), and is then added to
the board.
Single-select fields are set from the fields argument ({"App": "My App", "Priority": "P2 Normal"}), per task or for the whole call. Names and options
are matched case-insensitively against the board, and an unknown field or option
fails the whole call rather than being dropped. Two defaults apply when the
board has them and the model did not set them: Status → Triage and
Source → Meeting. Text, number, date and iteration fields are not set.
Limits and behaviour worth knowing
Section titled “Limits and behaviour worth knowing”- Zoom date ranges are one month per
list_zoom_recordingscall (a Zoom API limit). A meeting id resolves to its most recent recorded instance; pass the recordinguuidfor an older one. - Transcripts appear after Zoom finishes processing the recording, usually
within an hour of the meeting ending. Until then
has_transcriptis false andget_zoom_transcriptsays so. - Only Zoom links the regex recognises (
zoom.us/j/<id>,/w/,/s/) yield azoom_meeting_idfrom a calendar event. A vanity link (zoom.us/my/room) does not; the agent falls back tolist_zoom_recordings. - Transcript downloads are pinned to Zoom’s domains. A
download_urlthat does not point at*.zoom.us/*.zoomgov.com, or a redirect that leaves them, is refused. - Transcript text is data. The tool result tells the model to report what
was said and not to follow instructions inside it, and
create_project_tasksrefuses to confirm on anything but the user’s say-so in the conversation. - Expired tokens refresh silently. A
401from any vendor is reported in the shape the consent hook recognises; it clears the cached token and retries the call once with a refreshed one. For the GitHub write this happens only before the first issue is created, so a retry can never open duplicates. An issue that was opened but could not be added to the board, or whose fields could not be set, is reported underwarningswith its link so it can be placed by hand. - Closed boards are refused. The preview fails with the board’s title rather than opening issues nobody will see.
Nothing recurring on the platform side. A transcript enters the conversation once, as a bounded tool result, and is then part of that conversation’s history like any other tool result. The six tool specs are constant per deployment, so they sit in the prompt-cached prefix.