Integration

Avoma integration

Avoma is an AI meeting assistant that records, transcribes and summarizes sales and customer calls. Read meetings, recordings, transcripts, AI notes, insights, sentiments, segments, snippets, scorecards, engagement analytics and CRM timelines; push dialer calls in for transcription; make the bot leave a live meeting; manage note templates, smart categories, meeting types, outcomes and webhook subscriptions. Not exposed: the deprecated custom-category routes, the raw timeline-detail records, and the webhook signing-secret routes (they return or set a secret). Authentication is an API key an Avoma admin creates in Settings, Organization, Developer (its scope decides which meetings it sees), sent as a Bearer token; the API allows 60 requests per minute.

Connect Avoma How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Avoma.Built from the 47 Avoma tools below, on the connection you add once.

What you can do with Avoma

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Meeting outcome, 5 operations

create_meeting_outcomeCreate meeting outcomePOSTCreates a meeting outcome label for the whole organization, with a label and a description. Fails with 400 when the label already exists.
delete_meeting_outcomeDelete meeting outcomeDELETEDeletes a meeting outcome from the organization, by its uuid from list_meeting_outcomes. Permanent.
get_meeting_outcomeGet meeting outcomeGETReturns one meeting outcome (uuid, label, description), by its uuid from list_meeting_outcomes.
list_meeting_outcomesList meeting outcomesGETLists the meeting outcomes defined in the organization (labels such as Qualified that users set on a meeting), with their uuid, label and description.
update_meeting_outcomeUpdate meeting outcomePATCHRenames a meeting outcome or changes its description; send label, description or both. The uuid comes from list_meeting_outcomes.

Meeting type, 5 operations

create_meeting_typeCreate meeting typePOSTCreates a meeting type (purpose) for the whole organization, with a label and a description. Fails with 400 when the label already exists.
delete_meeting_typeDelete meeting typeDELETEDeletes a meeting type from the organization, by its uuid from list_meeting_types. Permanent.
get_meeting_typeGet meeting typeGETReturns one meeting type (uuid, label, description), by its uuid from list_meeting_types.
list_meeting_typesList meeting typesGETLists the meeting types (purposes such as Discovery Call) defined in the organization, with their uuid, label and description.
update_meeting_typeUpdate meeting typePATCHRenames a meeting type or changes its description; send label, description or both. The uuid comes from list_meeting_types.

Call, 4 operations

create_callCreate callPOSTPushes a dialer call into Avoma: it downloads recording_url (must be public) and transcribes it, or uses the transcript you send, then writes AI notes. Uses the license of user_email and creates a meeting the organization sees.
get_callGet callGETReturns one dialer call pushed to Avoma, found by the external_id it was created with, with its processing state, phone numbers and the Avoma meeting it became. Personal data.
list_callsList callsGETLists calls pushed to Avoma from a dialer (create_call) that started between from_date and to_date, optionally only inbound or outbound, with their processing state. Personal data: phone numbers and names.
update_callUpdate callPATCHChanges metadata of a pushed call once Avoma has processed it: caller and callee names, answered and voicemail flags, subject, meeting type, outcome, CRM links, additional details. Send only the fields to change.

Smart category, 4 operations

create_smart_categoryCreate smart categoryPOSTCreates a smart category for the organization's AI notes, with its keywords, prompts and settings (aug_notes_enabled, keyword_notes_enabled, prompt_extract_length, prompt_extract_strategy).
get_smart_categoryGet smart categoryGETReturns one smart category with its keywords, prompts and settings, by its uuid from list_smart_categories.
list_smart_categoriesList smart categoriesGETLists the organization's smart categories (the sections AI notes are sorted into) with their keywords, prompts and settings; their uuids feed create_template and list_notes.
update_smart_categoryUpdate smart categoryPATCHChanges a smart category's keywords, prompts or settings; send only what changes. The uuid comes from list_smart_categories.

Template, 4 operations

create_templateCreate templatePOSTCreates a note template from categories (uuids from list_smart_categories) for the given meeting types (uuids from list_meeting_types); it is inserted in the notes of those meetings.
get_templateGet templateGETReturns one note template (name, owner email, privacy, default flag, meeting types), by its uuid from list_templates.
list_templatesList templatesGETLists the organization's note templates: name, owner email, privacy, whether default, and the meeting types they apply to.
update_templateUpdate templatePUTReplaces a note template whole: send name, categories and meeting_type_uuids again, plus privacy, email and is_default (read them first with get_template), or values left out are reset.

Webhook, 3 operations

create_webhookCreate webhookPOSTSubscribes an HTTPS URL to an Avoma event (AINOTE when AI notes are ready, or a scheduler booking, cancel or reschedule); Avoma then POSTs each event there and retries a failure 5 times before deactivating.
delete_webhookDelete webhookDELETEDeactivates a webhook subscription (uuid from list_webhooks): no more events are sent to its URL. Avoma keeps the record with is_active false.
list_webhooksList webhooksGETLists the organization's active webhook subscriptions: event type, target type and uuid. The receiver URLs are not returned, since they may carry a token.

Engagement, 2 operations

get_user_engagementGet user engagementGETReturns one user's engagement broken down by participant between from_date and to_date: what they listened to, shared and commented for each participant (paginated). user_uuid comes from list_users.
list_engagementList engagementGETReturns per-user listening engagement between from_date and to_date: conversations and snippets listened, shared and commented, listening time and playback speed, one row per user (paginated, page_size up to 100).

Meeting, 2 operations

get_meetingGet meetingGETReturns one meeting by its uuid: subject, times, attendees, organizer, state, purpose and outcome, readiness of audio, video, transcript and notes, and its recording and transcription ids.
list_meetingsList meetingsGETLists meetings that started between from_date and to_date, newest first, with attendees, state, readiness of audio, video, transcript and notes, and the transcription and recording ids. Filters: call or video, internal, attendees, CRM ids.

Recording, 2 operations

get_meeting_recordingGet meeting recordingGETReturns signed download URLs (valid 5 days) of a meeting's audio and video recording, by meeting uuid. While the recording is still processing, Avoma answers with a message instead of URLs.
get_recordingGet recordingGETReturns signed download URLs (valid 5 days) of a recording's audio and video, by recording uuid (recording_uuid of get_meeting). While still processing, Avoma answers with a message.

Scorecard, 2 operations

get_scorecardGet scorecardGETReturns one scorecard template with its questions, question types, answer choices and tags, by its uuid from list_scorecards.
list_scorecardsList scorecardsGETLists the organization's scorecard templates with their questions and answer choices; their uuids filter list_scorecard_evaluations.

Summary, 2 operations

get_engagement_summaryGet engagement summaryGETReturns organization-wide engagement totals between from_date and to_date: conversations and snippets listened, shares, comments, listening time and average playback speed. Filters narrow the meetings counted.
get_user_engagement_summaryGet user engagement summaryGETReturns one user's engagement totals across all their participants between from_date and to_date: conversations listened, shares, comments, listening time, playback speed. user_uuid comes from list_users.

Transcription, 2 operations

get_transcriptionGet transcriptionGETReturns one transcript by its uuid (transcription_uuid of get_meeting): speakers, paragraphs with word timestamps and a signed VTT file URL. Personal data.
list_transcriptionsList transcriptionsGETLists meeting transcripts (speakers, paragraphs with word timestamps, VTT link) for meetings that started between from_date and to_date, paginated. For one meeting's transcript use get_transcription. Personal data.

User, 2 operations

get_userGet userGETReturns one Avoma user (name, email, position, role, status, teams), by the uuid from list_users.
list_usersList usersGETLists the users of the Avoma organization: name, email, position, role, status and teams. Their uuid feeds the engagement tools.

Drop, 1 operation

drop_meetingDrop meetingPOSTMakes the Avoma notetaker bot leave a meeting it is attending right now (acts on a live meeting). Fails with 406 when the bot is not in the meeting. Pass the meeting uuid from list_meetings.

Insight, 1 operation

get_meeting_insightsGet meeting insightsGETReturns AI insights of a completed meeting: AI notes with their speaker and time, tracked keywords per category and speaker, popular words, and the speakers. The meeting state must be completed.

Meeting segment, 1 operation

get_meeting_segmentsGet meeting segmentsGETReturns where each conversation segment (intro, agenda, demo, pricing, objection, next steps...) occurs in a meeting's recording, as [start, end] second ranges. Pass the meeting uuid.

Meeting sentiment, 1 operation

get_meeting_sentimentsGet meeting sentimentsGETReturns the sentiment of a meeting: an overall score and the score over time ranges of the recording. Pass the meeting uuid from list_meetings.

Note, 1 operation

list_notesList notesGETLists AI notes of meetings that started between from_date and to_date, as JSON, HTML or Markdown (output_format); pass meeting_uuid for one meeting, custom_category for one category. Paginated.

Scorecard evaluation, 1 operation

list_scorecard_evaluationsList scorecard evaluationsGETLists scorecard evaluations of meetings: who scored whom, the overall score and each question's answer and justification. Filter by date window, meeting, scorecard templates or evaluated users.

Snippet, 1 operation

list_snippetsList snippetsGETLists snippets (highlights) of meetings with title, description, start and end time and speakers. Pass meeting_uuid for one meeting, or from_date and to_date (at most 180 days apart). Paginated.

Timeline, 1 operation

get_revenue_timelineGet revenue timelineGETReturns engagement time series for CRM records of one type (opportunity, account, contact or lead): rep and customer meeting and call time, unrecorded meetings, emails sent. Beta.

Use Avoma from Claude Code, Cursor or Codex

Connect Avoma in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Avoma operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Avoma

Create your workspace
Sign up free. Nothing to install.
Connect Avoma once
Add your Avoma connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.