# Avoma

> Work with your Avoma meeting recordings and AI notes: find meetings by date, attendee, or type, read a transcript with each speaker marked as your side or the customer's, pull the AI notes as markdown or structured JSON, and look up your team and smart categories.

App · Meeting Notes · 6 actions. Web page: https://docs.lodol.com/docs/integrations/avoma

## Actions

### Get Avoma meeting

Get one meeting by its UUID: the attendees, the purpose and outcome, and whether the recording, transcript, and notes are ready.

**Inputs**

- Meeting uuid (`meeting_uuid`, text, required): The meeting's Avoma UUID. You can get this from the List Avoma meetings action.

**Outputs**

- `meeting` (object)

**Example output**

```json
{
  "meeting": {
    "attendees": [
      {
        "email": "ada@example.com",
        "name": "Ada Lovelace",
        "response_status": "accepted",
        "uuid": "123e4567-e89b-12d3-a456-426614174000"
      }
    ],
    "audio_ready": true,
    "created": "2026-01-28T15:46:12Z",
    "duration": 2700.0,
    "end_at": "2026-01-28T15:45:00Z",
    "is_call": false,
    "is_internal": false,
    "is_private": false,
    "modified": "2026-01-28T15:52:04Z",
    "notes_ready": true,
    "organizer_email": "ada@example.com",
    "outcome": {
      "label": "Qualified",
      "uuid": "8e7d6c5b-4a39-2817-06f5-e4d3c2b1a099"
    },
    "processing_status": "completed",
    "purpose": {
      "label": "Discovery",
      "uuid": "9f8e7d6c-5b4a-3928-1706-f5e4d3c2b1a0"
    },
    "recording_uuid": "5b1e2a3c-4d5e-6f70-8192-a3b4c5d6e7f8",
    "start_at": "2026-01-28T15:00:00Z",
    "state": "completed",
    "subject": "Acme Corp: discovery call",
    "transcript_ready": true,
    "transcription_uuid": "6c2f3b4d-5e6f-7081-92a3-b4c5d6e7f809",
    "type": {
      "label": "External",
      "uuid": "7d6c5b4a-3928-1706-f5e4-d3c2b1a09988"
    },
    "url": "https://app.avoma.com/meetings/095be615-a8ad-4c33-8e9c-c7612fbf6c9f",
    "uuid": "095be615-a8ad-4c33-8e9c-c7612fbf6c9f",
    "video_ready": true
  }
}
```

### Get Avoma transcript

Get a meeting's transcript: who spoke, what they said, and when in the recording. Speakers are marked as your side or the other side, so a workflow can pull out just the customer's words.

**Inputs**

- Meeting uuid (`meeting_uuid`, text, required): The meeting's Avoma UUID. You can get this from the List Avoma meetings action.
- From date (`from_date`, date and time, required): Only include meetings that started at or after this moment, as a UTC ISO 8601 timestamp such as 2026-01-01T00:00:00Z. Avoma requires a date range on this endpoint.
- To date (`to_date`, date and time, required): Only include meetings that started at or before this moment, as a UTC ISO 8601 timestamp such as 2026-01-31T23:59:59Z. Avoma requires a date range on this endpoint.

**Outputs**

- `transcription` (object)

**Example output**

```json
{
  "transcription": {
    "meeting_uuid": "095be615-a8ad-4c33-8e9c-c7612fbf6c9f",
    "segments": [
      {
        "end_time": 3.12,
        "speaker_id": 0,
        "start_time": 0.77,
        "transcript": "Thanks for making the time today."
      }
    ],
    "speakers": [
      {
        "email": "ada@example.com",
        "id": 0,
        "is_rep": true,
        "name": "Ada Lovelace"
      }
    ],
    "uuid": "6c2f3b4d-5e6f-7081-92a3-b4c5d6e7f809",
    "vtt_url": "https://api.avoma.com/transcriptions/6c2f3b4d.vtt"
  }
}
```

### List Avoma meetings

List meetings that started in a date range, with who attended and whether the transcript and notes are ready yet. Returns the meeting UUIDs the transcript and notes actions take.

**Inputs**

- From date (`from_date`, date and time, required): Only include meetings that started at or after this moment, as a UTC ISO 8601 timestamp such as 2026-01-01T00:00:00Z. Avoma requires a date range on this endpoint.
- To date (`to_date`, date and time, required): Only include meetings that started at or before this moment, as a UTC ISO 8601 timestamp such as 2026-01-31T23:59:59Z. Avoma requires a date range on this endpoint.
- Attendee emails (`attendee_emails`, text): Comma-separated email addresses. Only meetings with at least one of these attendees are returned.
- Is call (`is_call`, true/false): True for dialer calls only, false for video meetings only. Leave blank for both.
- Is internal (`is_internal`, true/false): True for meetings where everyone is from your organisation, false for ones with an outside guest. Leave blank for both.
- Recording duration gte (`recording_duration_gte`, number): Only meetings whose recording runs at least this many seconds, which is a good way to skip no-shows.
- Ordering (`ordering`, text): Sort by start time, oldest or newest first. Defaults to Avoma's own order. One of: `start_at` (Oldest first), `-start_at` (Newest first).
- Page size (`page_size`, number): How many records to return per page, 1 to 100.

**Outputs**

- `count` (number): Number of meetings on this page.
- `meetings` (list): Meetings on this page.
- `next_url` (text): Avoma's URL for the next page. Null on the last page. Avoma pages with opaque URLs rather than page numbers.
- `previous_url` (text): Avoma's URL for the previous page. Null on the first page.
- `total` (number): How many records match in total, across all pages.

**Example output**

```json
{
  "count": 1,
  "meetings": [
    {
      "attendees": [
        {
          "email": "ada@example.com",
          "name": "Ada Lovelace",
          "response_status": "accepted",
          "uuid": "123e4567-e89b-12d3-a456-426614174000"
        }
      ],
      "audio_ready": true,
      "created": "2026-01-28T15:46:12Z",
      "duration": 2700.0,
      "end_at": "2026-01-28T15:45:00Z",
      "is_call": false,
      "is_internal": false,
      "is_private": false,
      "modified": "2026-01-28T15:52:04Z",
      "notes_ready": true,
      "organizer_email": "ada@example.com",
      "outcome": {
        "label": "Qualified",
        "uuid": "8e7d6c5b-4a39-2817-06f5-e4d3c2b1a099"
      },
      "processing_status": "completed",
      "purpose": {
        "label": "Discovery",
        "uuid": "9f8e7d6c-5b4a-3928-1706-f5e4d3c2b1a0"
      },
      "recording_uuid": "5b1e2a3c-4d5e-6f70-8192-a3b4c5d6e7f8",
      "start_at": "2026-01-28T15:00:00Z",
      "state": "completed",
      "subject": "Acme Corp: discovery call",
      "transcript_ready": true,
      "transcription_uuid": "6c2f3b4d-5e6f-7081-92a3-b4c5d6e7f809",
      "type": {
        "label": "External",
        "uuid": "7d6c5b4a-3928-1706-f5e4-d3c2b1a09988"
      },
      "url": "https://app.avoma.com/meetings/095be615-a8ad-4c33-8e9c-c7612fbf6c9f",
      "uuid": "095be615-a8ad-4c33-8e9c-c7612fbf6c9f",
      "video_ready": true
    }
  ],
  "next_url": "https://api.avoma.com/v1/meetings/?page=2",
  "previous_url": null,
  "total": 37
}
```

### List Avoma notes

Get Avoma's AI meeting notes over a date range, or for a single meeting. Ask for markdown or HTML to get something you can post straight into Slack or an email, or JSON to work through the sections in a workflow.

**Inputs**

- From date (`from_date`, date and time, required): Only include meetings that started at or after this moment, as a UTC ISO 8601 timestamp such as 2026-01-01T00:00:00Z. Avoma requires a date range on this endpoint.
- To date (`to_date`, date and time, required): Only include meetings that started at or before this moment, as a UTC ISO 8601 timestamp such as 2026-01-31T23:59:59Z. Avoma requires a date range on this endpoint.
- Meeting uuid (`meeting_uuid`, text): Narrow to a single meeting. Leave blank for every meeting in the date range.
- Output format (`output_format`, text): How the notes come back. JSON gives structured sections; markdown and HTML give ready-to-post text. One of: `json` (JSON (structured)), `html`, `markdown`.
- Custom category (`custom_category`, text): Only notes filed under this smart category, by its UUID. You can get this from the List Avoma smart categories action.
- Page size (`page_size`, number): How many records to return per page, 1 to 100.

**Outputs**

- `count` (number): Number of note sets on this page.
- `next_url` (text): Avoma's URL for the next page. Null on the last page. Avoma pages with opaque URLs rather than page numbers.
- `notes` (list): One entry per meeting's notes.
- `previous_url` (text): Avoma's URL for the previous page. Null on the first page.
- `total` (number): How many records match in total, across all pages.

**Example output**

```json
{
  "count": 1,
  "next_url": null,
  "notes": [
    {
      "created": "2026-01-28T15:52:04Z",
      "data": "## Next steps\n- Send the pricing sheet by Friday.",
      "modified": "2026-01-28T15:52:04Z"
    }
  ],
  "previous_url": null,
  "total": 12
}
```

### List Avoma smart categories

List the smart categories Avoma uses to tag what was discussed, such as pricing or competitors, with the keywords and prompts behind each. Their UUIDs can filter the notes action.

**Inputs**: None.

**Outputs**

- `categories` (list): The organisation's smart categories.
- `count` (number): Number of categories returned.

**Example output**

```json
{
  "categories": [
    {
      "is_default": true,
      "key": "pricing",
      "keywords": [
        "discount",
        "budget"
      ],
      "name": "Pricing",
      "prompts": [
        "What is your budget?"
      ],
      "uuid": "2b3c4d5e-6f70-8192-a3b4-c5d6e7f80912"
    }
  ],
  "count": 1
}
```

### List Avoma users

List the people in your Avoma organisation with their email, role, and status. Useful for routing a meeting's follow-up to the right person.

**Inputs**: None.

**Outputs**

- `count` (number): Number of users returned.
- `users` (list): Everyone in the organisation.

**Example output**

```json
{
  "count": 1,
  "users": [
    {
      "email": "ada@example.com",
      "first_name": "Ada",
      "job_function": "Sales",
      "last_name": "Lovelace",
      "position": "Account Executive",
      "role": "Admin",
      "status": "active",
      "teams": "Enterprise Sales",
      "uuid": "4a3b2c1d-0e9f-8a7b-6c5d-4e3f2a1b0c9d"
    }
  ]
}
```