> ## Documentation Index
> Fetch the complete documentation index at: https://developers.arg.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Avoma

> Read recorded meetings, transcripts, and AI notes from Avoma.

Avoma connects two ways under one tile. The **MCP connector** signs each person in to their own Avoma account, so the agent sees only the meetings that person can see. The **API key** is org-wide and powers the `avoma_*` actions in chat, apps, and automations. Everything is read-only - nothing in Avoma is changed.

## What you can do

**Actions** - list meetings, get a meeting, get a meeting's AI insights, list transcripts, get a transcript, list AI notes, list users.

**Triggers** - **Meeting completed**: starts an automation when a meeting has ended and its transcript and AI notes are ready, optionally only for meetings with given attendees or only internal/external ones. Polled, so it fires within about 15 minutes of the notes being ready. Triggers run on the API-key connection.

## Connect with the MCP connector

<Steps>
  <Step title="Open Integrations">
    In arg.ai, go to **Settings → Integrations** and click **Connect** on **Avoma**.
  </Step>

  <Step title="Sign in to Avoma">
    Approve the request on Avoma's consent screen. Each teammate connects their own account.
  </Step>
</Steps>

## Connect with an API key

<Steps>
  <Step title="Get a key">
    An Avoma admin generates one in Avoma's organization settings. If your plan doesn't show it,
    Avoma's [API docs](https://dev.avoma.com/) say to ask Avoma support to issue one.
  </Step>

  <Step title="Paste the key">
    On the **Avoma** tile in **Settings → Integrations**, paste it into the API key field. arg.ai
    checks the key by listing your Avoma users before saving.
  </Step>
</Steps>

## Use it

* **In chat:** *"Summarize every external call I had last week and the next steps from each."*
* **In an automation:** start from the **Avoma - Meeting completed** trigger, read the meeting's notes with **Avoma: get meeting insights**, and write a follow-up into `/calls`.

## How the data fits together

A **meeting** is the starting point - list them for a date range, optionally filtered by attendee email (pass your own for "my meetings"), internal vs external, recorded length, or a linked CRM account, opportunity, contact, or lead. Each meeting carries a `transcription_uuid` for **get a transcript**, and its uuid opens **get meeting insights** (AI notes, keywords, per-speaker talk stats).

Date ranges are required on every list. A bare date like `2026-08-31` covers that whole day in UTC, on both ends of the range.

## Permissions

An Avoma API key reads across the whole organization, not just the person who asked. Use the MCP connector when access should follow each person's own Avoma permissions.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.