Avoma
for LuumenAI

Read meeting transcripts, notes, and scorecards, and submit outside calls for analysis

Connect Avoma and your meeting record becomes something the agent can read. Pull a meeting's processing state, its AI insights and speaker segments, notes for a date range, scorecard evaluations, and per-user engagement metrics. When a call was recorded somewhere else, the agent can submit it to Avoma for processing as an approved step.

The Avoma toolbox

16 tools: 15 read, 1 write. Reads answer instantly. Writes require approval by default. Everything is logged.

  • ReadGet CallRetrieve one externally ingested Avoma call by the dialer system's external ID.
  • ReadGet Engagement SummaryAggregate Avoma engagement metrics across visible users for a required UTC date range and optional meeting and user filters.
  • ReadGet MeetingRetrieve one meeting by UUID, including processing/readiness state and optionally CRM associations.
  • ReadGet Meeting AnalysisReturn Avoma's AI insights, topical and speaker segments, and sentiment records for one processed meeting in a single read-only invocation.
  • ReadGet RecordingGet time-limited audio and video URLs for a meeting recording.
  • ReadList CallsList externally ingested calls in a required UTC date range, optionally filtered by inbound or outbound direction.
  • ReadList Configuration ResourcesList one Avoma configuration catalog: custom categories, smart categories, scorecards, templates, meeting types, or meeting outcomes.
  • ReadList Engagement MetricsList per-user Avoma engagement metrics over a required UTC date range with meeting and user filters.
  • ReadList MeetingsFind meetings visible to the connected Avoma user within a required UTC date range, with optional attendee, CRM, call-type, privacy-context, duration, and ordering filters.
  • ReadList NotesRetrieve Avoma notes for meetings in a required UTC date range, optionally narrowed to a meeting or custom category and rendered as JSON, HTML, or Markdown.
  • ReadList Scorecard EvaluationsList Avoma scorecard evaluations, optionally filtered by UTC date range, scorecard templates, meeting, or evaluated users.
  • ReadList SnippetsFind user-created or AI-generated meeting snippets by meeting UUID or by a UTC date range of at most 180 days.
  • ReadList TranscriptionsFind full meeting transcriptions by meeting UUID or by a UTC date range, with attendee and CRM filters.
  • ReadList UsersReturn users visible in the Avoma organization, including their UUID, email, role, teams, and active status.
  • ReadList WebhooksAudit the connected organization's active Avoma webhook subscriptions without reading signing secrets.
  • WriteCreate CallSubmit an externally hosted call recording to Avoma for asynchronous processing. Approval by default

One prompt, start to finish

What a governed Avoma run looks like inside Luumen.

Questions

How does LuumenAI connect to Avoma?

Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.

Can LuumenAI change things in Avoma on its own?

Read actions answer immediately. Anything that writes — create call — is shown as a plan and requires approval by default. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.

Who gets access to the integration?

You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.

Is there an audit trail?

Every call to Avoma — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.

Put Avoma to work with Luumen

Connect in minutes. Every action scoped, approved, and audited from day one.