Avoma MCP integration for AI agents.
Connect AI agents to Avoma through 9 structured actions, including get meeting, get meeting insights, and get recording. Review authentication, inputs, workf…
- ACTION CONTRACTS
- 9
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Avoma integration exposes
The Avoma Agent App exposes 9 provider-backed actions for ai, communication, and data work. Its current contract lets an authorized agent get a single avoma meeting by uuid, get ai notes, keywords, speakers, and related insights for a completed avoma meeting, and get avoma recording download urls by recording uuid when the recording is ready. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Avoma account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Avoma capabilities.
Showing 9 of 9 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_meetingREADGet a single Avoma meeting by UUID.
INPUTS: meetingUuid / includeCrmAssociations
get_meeting_insightsREADGet AI notes, keywords, speakers, and related insights for a completed Avoma meeting.
INPUTS: meetingUuid
get_recordingREADGet Avoma recording download URLs by recording UUID when the recording is ready.
INPUTS: recordingUuid
get_recording_for_meetingREADGet Avoma recording download URLs for a meeting UUID when the recording is ready.
INPUTS: meetingUuid
get_transcriptionREADGet a single Avoma transcription by UUID.
INPUTS: transcriptionUuid
get_userREADGet a single Avoma user by UUID.
INPUTS: userUuid
list_meetingsREADList Avoma meetings within a UTC date range, with optional attendee, CRM, and meeting filters.
INPUTS: fromDate / toDate / page / pageSize / recordingDurationGte
list_transcriptionsREADList Avoma transcriptions for meetings within a UTC date range, with optional attendee and CRM filters.
INPUTS: fromDate / toDate / page / pageSize / attendeeEmails
list_usersREADList Avoma users visible to the API key.
INPUT CONTRACTS
Know what the action needs before it runs.
get_meeting
meetingUuidREQUIRED- Unique ID of the Avoma meeting.
includeCrmAssociationsOPTIONAL- Whether Avoma should include CRM associations.
get_meeting_insights
meetingUuidOPTIONAL- Unique ID of the Avoma meeting.
get_recording
recordingUuidOPTIONAL- Unique ID of the Avoma recording.
get_recording_for_meeting
meetingUuidOPTIONAL- Unique ID of the Avoma meeting.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Meeting
Get a single Avoma meeting by UUID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_meetingVerify with Get Meeting Insights
Get AI notes, keywords, speakers, and related insights for a completed Avoma meeting. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_meeting_insightsSAFETY BOUNDARY
Operate Avoma with explicit limits
- Authorize Avoma with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Avoma data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Avoma rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Avoma task completed successfully.
CONNECTION MODEL
API key
Avoma API key sent as a Bearer token. Admins can create or copy scoped API keys in Avoma under Settings > Organization > Developer: https://help.avoma.com/api-integration-for-avoma.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 9
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Avoma.