Avoma Connector for AI Agents

Tools your meeting agent reaches for on Avoma, scoped per user.

CALL ANY TOOL

List Avoma meeting notes, transcripts, scorecards, and recordings with a bearer token, scoped per user.

avoma_call_create

Create call

Ingest a call record into Avoma from an external dialer or CRM system, so Avoma can process its recording. Creates and returns a call record with its processing state; Avoma downloads the recording from the given URL and processes it like a meeting. Use avoma_call_create when a call happened outside Avoma (e.g. in HubSpot, Twilio, RingCentral) and you want Avoma to transcribe and analyze it; use avoma_call_update to change an existing call's metadata afterward. Requires an Avoma user's email (whose license processes the call) and a publicly downloadable recording_url.

Parameters

Name

Type

Required

Description

direction

string

Required

Direction of the call: 'Inbound' or 'Outbound'. One of: `Inbound`, `Outbound`.

external_id

string

Required

Unique id of the call from the external dialer/CRM system (e.g. HubSpot, Twilio, Zoom). Combined with 'source', this must be unique per organization, creating a call with a duplicate external_id/source pair fails. Example: 1234567890

frm

string

Required

Phone number the call was made from, in E.164-like format. Example: +11234567890

participants

array

Required

List of participants on the call. Put the prospect or lead the call was with first, Avoma uses the first entry to build the call's subject. Each participant needs an email, and may include a name and CRM associations. Example: [{"email": "prospect@customer.com", "name": "Jane Prospect"}]

recording_url

string

Required

Publicly reachable URL of the call recording. Avoma downloads the audio from this URL to transcribe and process the call, so it must be accessible without additional authentication. Example: https://example.com/recording.mp3

source

string

Required

Lowercase string identifying the dialer/system the call came from, e.g. zoom, zoomphone, twilio, phoneburner, ringcentral, aircall. Combined with 'external_id', this must be unique per organization.

start_at

string

Required

Start time of the call, as an ISO 8601 date-time. Example: 2024-01-15T14:30:00Z

string

Required

Phone number the call was made to, in E.164-like format. Example: +12234567890

user_email

string

Required

Email of the Avoma user who made or received the call. This must be an existing, active Avoma user in your organization with the dialer feature enabled, their license is used to process the call. Example: rep@company.com

additional_details

string

Optional

Additional metadata about the call, as a JSON-encoded string.

answered

boolean

Optional

Whether the call was answered.

crm_association

array

Optional

CRM records linked to this call as a whole (e.g. a Salesforce or HubSpot contact, account, or opportunity). Example: [{"crm_obj_id": "30447071570", "crm_obj_type": "account"}]

end_at

string

Optional

End time of the call, as an ISO 8601 date-time.

frm_name

string

Optional

Name of the caller who made the call.

is_voicemail

boolean

Optional

Whether this call is a voicemail. Defaults to false. Default: `false`.

to_name

string

Optional

Name of the person the call was made to.

avoma_call_get

Get call

avoma_call_update

Update call

Update metadata on an existing call record after Avoma has finished processing it. Returns the updated call record; only call-specific metadata fields can be changed (identifiers, timing, recording, and processing state cannot be changed). Use avoma_call_update to correct or enrich a call's details (names, voicemail/answered flags, meeting subject/type/outcome, CRM associations) after avoma_call_create; use avoma_call_get to check a call's current state first. Requires the call's external_id, and at least one field to update.

Parameters

Name

Type

Required

Description

external_id

string

Required

Unique id of the call to update, as assigned by the external dialer/CRM system that created it. Example: 1234567890

additional_details

string

Optional

Additional call metadata, as a JSON-encoded string. At least one updatable field must be provided in the request.

answered

boolean

Optional

Whether the call was answered. At least one updatable field must be provided in the request.

crm_association

array

Optional

CRM records to link to this call (e.g. a Salesforce or HubSpot contact, account, or opportunity). At least one updatable field must be provided in the request. Example: [{"crm_obj_id": "30447071570", "crm_obj_type": "account"}]

frm_name

string

Optional

Name of the caller (the 'from' participant). At least one updatable field must be provided in the request.

is_voicemail

boolean

Optional

Whether the call is a voicemail. At least one updatable field must be provided in the request.

meeting_outcome_uuid

string

Optional

UUID of the meeting outcome to associate with this call's meeting. At least one updatable field must be provided in the request.

meeting_purpose_uuid

string

Optional

UUID of the meeting purpose/type to associate with this call's meeting. At least one updatable field must be provided in the request.

subject

string

Optional

Subject/topic of the meeting associated with this call. At least one updatable field must be provided in the request.

to_name

string

Optional

Name of the callee (the 'to' participant). At least one updatable field must be provided in the request.

avoma_calls_list

List calls

avoma_engagement_metrics_list

List engagement metrics

List engagement analytics for every user in the organization over a date range. Returns paginated per-user metrics such as conversations listened, snippets listened, conversations shared and commented, total comments, and listened duration/percentage. Use this to compare engagement across the whole team; use avoma_user_engagement_list for metrics scoped to one user's participants, or avoma_engagement_summary_get for an aggregated organization-wide total instead of per-user rows.

Parameters

Name

Type

Required

Description

from_date

string

Required

Start of the date range (inclusive), as an ISO 8601 UTC datetime. Only meetings that started at or after this time are included. Example: 2024-01-01T00:00:00Z

to_date

string

Required

End of the date range (inclusive), as an ISO 8601 UTC datetime. Only meetings that started at or before this time are included. Example: 2024-01-31T23:59:59Z

is_call

boolean

Optional

Filter by meeting type: true for voice calls only, false for video meetings only. Leave unset to include both.

is_impromptu

boolean

Optional

Filter by whether the meeting was unscheduled/ad-hoc: true for impromptu meetings only, false for scheduled meetings only.

is_internal

boolean

Optional

Filter by attendee composition: true for internal-only meetings (no external attendees), false for meetings with at least one external attendee. Leave unset to include both.

meeting_outcome_uuid

array

Optional

Restrict results to meetings with one or more specific meeting outcome UUIDs. Each entry is sent as a repeated query parameter. Example: ["9c4b1e2e-4b8a-4b6b-9b1a-2f6a7e1c9d10"]

meeting_type_uuid

array

Optional

Restrict results to meetings with one or more specific meeting type UUIDs. Each entry is sent as a repeated query parameter. Example: ["7f2a1e2e-4b8a-4b6b-9b1a-2f6a7e1c9d10"]

string

Optional

Field to order results by. Prefix with '-' for descending order. One of: user_email, -user_email, conversations_listened, -conversations_listened, snippets_listened, -snippets_listened, conversations_shared, -conversations_shared, conversations_commented, -conversations_commented, total_comments, -total_comments, conversations_listened_duration, -conversations_listened_duration, conversations_listened_percent, -conversations_listened_percent. Example: -conversations_listened. One of: `user_email`, `-user_email`, `conversations_listened`, `-conversations_listened`, `snippets_listened`, `-snippets_listened`, `conversations_shared`, `-conversations_shared`, `conversations_commented`, `-conversations_commented`, `total_comments`, `-total_comments`, `conversations_listened_duration`, `-conversations_listened_duration`, `conversations_listened_percent`, `-conversations_listened_percent`.

page

integer

Optional

Page number to retrieve, starting at 1. Defaults to 1. Default: `1`.

page_size

integer

Optional

Number of user rows to return per page. Must be between 1 and 100. Defaults to 10. Default: `10`.

recording_duration__gte

number

Optional

Only include meetings whose recording duration is greater than or equal to this many seconds.

recording_duration__lte

number

Optional

Only include meetings whose recording duration is less than or equal to this many seconds.

shared_meetings_only

boolean

Optional

If true, only include meetings that were shared with others.

user_email

array

Optional

Restrict results to one or more specific user email addresses. Each entry is sent as a repeated query parameter. Example: ["rep@company.com"]

avoma_engagement_summary_get

Get engagement summary

Get an aggregated engagement summary across all users in the organization over a date range. Returns organization-wide totals such as total conversations, shares, and comments, rolled up into a single summary object. Use this for an overall organization total; use avoma_engagement_metrics_list for a paginated per-user breakdown, or avoma_user_engagement_summary_get for the equivalent summary scoped to one user.

Parameters

Name

Type

Required

Description

from_date

string

Required

Start of the date range (inclusive), as an ISO 8601 UTC datetime. Only meetings that started at or after this time are included. Example: 2024-01-01T00:00:00Z

to_date

string

Required

End of the date range (inclusive), as an ISO 8601 UTC datetime. Only meetings that started at or before this time are included. Example: 2024-01-31T23:59:59Z

is_call

boolean

Optional

Filter by meeting type: true for voice calls only, false for video meetings only. Leave unset to include both.

is_impromptu

boolean

Optional

Filter by whether the meeting was unscheduled/ad-hoc: true for impromptu meetings only, false for scheduled meetings only.

is_internal

boolean

Optional

Filter by attendee composition: true for internal-only meetings (no external attendees), false for meetings with at least one external attendee. Leave unset to include both.

meeting_outcome_uuid

array

Optional

Restrict the summary to meetings with one or more specific meeting outcome UUIDs. Each entry is sent as a repeated query parameter. Example: ["9c4b1e2e-4b8a-4b6b-9b1a-2f6a7e1c9d10"]

meeting_type_uuid

array

Optional

Restrict the summary to meetings with one or more specific meeting type UUIDs. Each entry is sent as a repeated query parameter. Example: ["7f2a1e2e-4b8a-4b6b-9b1a-2f6a7e1c9d10"]

recording_duration__gte

number

Optional

Only include meetings whose recording duration is greater than or equal to this many seconds.

recording_duration__lte

number

Optional

Only include meetings whose recording duration is less than or equal to this many seconds.

shared_meetings_only

boolean

Optional

If true, only include meetings that were shared with others.

user_email

array

Optional

Restrict the summary to one or more specific user email addresses. Each entry is sent as a repeated query parameter. Example: ["rep@company.com"]

avoma_meeting_drop

Meeting drop

avoma_meeting_get

Get meeting

avoma_meeting_outcome_create

Create meeting outcome

avoma_meeting_outcome_delete

Delete meeting outcome

avoma_meeting_outcome_get

Get meeting outcome

avoma_meeting_outcome_update

Update meeting outcome

avoma_meeting_outcomes_list

List meeting outcomes

avoma_meeting_recording_get

Get meeting recording

avoma_meeting_type_get

Get meeting type

avoma_meeting_types_list

List meeting types

avoma_meetings_list

List meetings

List meetings in the organization within a date range, optionally filtered by call type, internal/external attendees, or linked CRM records. Returns a paginated list of meeting records with subject, schedule, state, organizer, attendees, purpose/outcome, and readiness flags for transcript, audio, video, and notes. Use avoma_meetings_list to browse or search meetings by date range; use avoma_meeting_get to fetch a single meeting by its UUID. Requires a from_date and to_date range.

Parameters

Name

Type

Required

Description

from_date

string

Required

Retrieve meetings that started at or after this date-time (UTC), in ISO 8601 format. Example: 2024-01-01T00:00:00Z

to_date

string

Required

Retrieve meetings that started at or before this date-time (UTC), in ISO 8601 format. Example: 2024-01-31T23:59:59Z

attendee_emails

string

Optional

Comma-separated list of attendee email addresses to filter by. Meetings that include any of the listed attendees are returned. Example: john.doe@example.com,kelly@acme.com

crm_account_ids

string

Optional

Comma-separated list of CRM account external IDs to filter meetings by their linked account.

crm_contact_ids

string

Optional

Comma-separated list of CRM contact external IDs to filter meetings by their linked contact.

crm_lead_ids

string

Optional

Comma-separated list of CRM lead external IDs to filter meetings by their linked lead.

crm_opportunity_ids

string

Optional

Comma-separated list of CRM opportunity external IDs to filter meetings by their linked opportunity/deal.

include_crm_associations

boolean

Optional

Whether to include each meeting's linked CRM associations (CRM object type and id, e.g. a Salesforce or HubSpot contact, account, or opportunity) in the response. Defaults to false. Default: `false`.

is_call

boolean

Optional

Filter by meeting type: true returns only voice call meetings, false returns only video call meetings. Leave unset to return both.

is_internal

boolean

Optional

Filter by attendee composition: true returns only meetings where every attendee is from within the organization, false returns only meetings that include at least one external attendee. Leave unset to return both.

string

Optional

Ordering of the returned meetings by start time. 'start_at' sorts ascending (oldest first), '-start_at' sorts descending (newest first, the default). One of: `start_at`, `-start_at`. Default: `-start_at`.

page_size

integer

Optional

Number of meeting records to return per page. Maximum 100. Defaults to 10 if not provided. Default: `10`.

recording_duration__gte

number

Optional

Only return meetings whose recording duration (in seconds) is greater than or equal to this value. Setting this filter excludes meetings without recordings by default. Example: 300 (5 minutes).

avoma_recording_get

Get recording

avoma_revenue_intel_timeline_details_list

List revenue intel timeline details

avoma_scorecard_evaluations_list

List scorecard evaluations

avoma_scorecard_get

Get scorecard

avoma_smart_categories_list

List smart categories

avoma_smart_category_create

Create smart category

avoma_smart_category_get

Get smart category

avoma_smart_category_update

Update smart category

avoma_snippets_list

List snippets

avoma_transcription_get

Get transcription

avoma_transcriptions_list

List transcriptions

List Avoma meeting transcriptions within a date range, or fetch a single meeting's transcription directly by meeting UUID. Returns, per meeting, the transcription uuid, meeting_uuid, a signed transcription_vtt_url, the speakers array (id, name, email, is_rep), and the transcript array (per-paragraph text with speaker_id and word timestamps). When meeting_uuid is provided the response is that meeting's transcription; otherwise it is a paginated list (count, next, previous, results). Use avoma_transcriptions_list to browse or filter transcriptions by date range, attendee, or CRM association, or to fetch one meeting's transcription by meeting_uuid. Use avoma_transcription_get when you already have a transcription's own uuid. Either meeting_uuid, or both from_date and to_date, must be provided.

Parameters

Name

Type

Required

Description

attendee_emails

string

Optional

Comma-separated list of attendee email addresses to filter meetings by; meetings with any of these attendees are returned. Example: john.doe@example.com,kelly@acme.com

crm_account_ids

string

Optional

Comma-separated list of CRM account external IDs to filter transcriptions by.

crm_contact_ids

string

Optional

Comma-separated list of CRM contact external IDs to filter transcriptions by.

crm_lead_ids

string

Optional

Comma-separated list of CRM lead external IDs to filter transcriptions by.

crm_opportunity_ids

string

Optional

Comma-separated list of CRM opportunity external IDs to filter transcriptions by.

from_date

string

Optional

Return transcriptions for meetings that started at or after this date-time (UTC), in ISO 8601 format. Required together with to_date when meeting_uuid is not provided; ignored (may be omitted) when meeting_uuid is set. Example: 2024-01-01T00:00:00Z

meeting_uuid

string

Optional

Unique ID (UUID) of a specific meeting whose transcription should be returned directly, bypassing pagination and the date-range filters. Example: 3c1a1e2e-4b8a-4b6b-9b1a-2f6a7e1c9d10

page

integer

Optional

Page number for pagination. Only used when meeting_uuid is not provided. Starts at 1.

page_size

integer

Optional

Number of transcriptions to return per page (maximum 100). Only used when meeting_uuid is not provided.

to_date

string

Optional

Return transcriptions for meetings that started at or before this date-time (UTC), in ISO 8601 format. Required together with from_date when meeting_uuid is not provided; ignored (may be omitted) when meeting_uuid is set. Example: 2024-01-31T23:59:59Z

avoma_user_engagement_list

List user engagement

List participant-level engagement metrics for one specific user over a date range. Returns paginated rows showing that user's interaction with each participant: conversations listened, snippets listened, conversations shared and commented, total comments, average playback speed, and listened duration/percentage. Use this to drill into a single user's activity by participant; use avoma_engagement_metrics_list for a per-user breakdown across the whole organization instead. Requires a user uuid, typically obtained from avoma_users_list.

Parameters

Name

Type

Required

Description

from_date

string

Required

Start of the date range (inclusive), as an ISO 8601 UTC datetime. Only meetings that started at or after this time are included. Example: 2024-01-01T00:00:00Z

to_date

string

Required

End of the date range (inclusive), as an ISO 8601 UTC datetime. Only meetings that started at or before this time are included. Example: 2024-01-31T23:59:59Z

user_uuid

string

Required

UUID of the Avoma user to get engagement metrics for. Obtain this from avoma_users_list. Example: 3c1a1e2e-4b8a-4b6b-9b1a-2f6a7e1c9d10

is_call

boolean

Optional

Filter by meeting type: true for voice calls only, false for video meetings only. Leave unset to include both.

is_impromptu

boolean

Optional

Filter by whether the meeting was unscheduled/ad-hoc: true for impromptu meetings only, false for scheduled meetings only.

is_internal

boolean

Optional

Filter by attendee composition: true for internal-only meetings (no external attendees), false for meetings with at least one external attendee. Leave unset to include both.

meeting_outcome_uuid

array

Optional

Restrict results to meetings with one or more specific meeting outcome UUIDs. Each entry is sent as a repeated query parameter. Example: ["9c4b1e2e-4b8a-4b6b-9b1a-2f6a7e1c9d10"]

meeting_type_uuid

array

Optional

Restrict results to meetings with one or more specific meeting type UUIDs. Each entry is sent as a repeated query parameter. Example: ["7f2a1e2e-4b8a-4b6b-9b1a-2f6a7e1c9d10"]

string

Optional

Field to order results by. Prefix with '-' for descending order. One of: participant_email, -participant_email, conversations_listened, -conversations_listened, snippets_listened, -snippets_listened, conversations_shared, -conversations_shared, conversations_commented, -conversations_commented, total_comments, -total_comments, avg_playback_speed, -avg_playback_speed, conversations_listened_duration, -conversations_listened_duration, conversations_listened_percent, -conversations_listened_percent. Example: -conversations_listened. One of: `participant_email`, `-participant_email`, `conversations_listened`, `-conversations_listened`, `snippets_listened`, `-snippets_listened`, `conversations_shared`, `-conversations_shared`, `conversations_commented`, `-conversations_commented`, `total_comments`, `-total_comments`, `avg_playback_speed`, `-avg_playback_speed`, `conversations_listened_duration`, `-conversations_listened_duration`, `conversations_listened_percent`, `-conversations_listened_percent`.

page

integer

Optional

Page number to retrieve, starting at 1. Defaults to 1. Default: `1`.

page_size

integer

Optional

Number of participant rows to return per page. Must be between 1 and 100. Defaults to 10. Default: `10`.

participant_email

array

Optional

Restrict results to one or more specific participant email addresses. Each entry is sent as a repeated query parameter. Example: ["customer@example.com"]

recording_duration__gte

number

Optional

Only include meetings whose recording duration is greater than or equal to this many seconds.

recording_duration__lte

number

Optional

Only include meetings whose recording duration is less than or equal to this many seconds.

shared_meetings_only

boolean

Optional

If true, only include meetings that were shared with others.

avoma_user_engagement_summary_get

Get user engagement summary

Get an aggregated engagement summary for one specific user's participants over a date range. Returns summary statistics showing how that user engaged across all of their participants, rolled up into a single summary object. Use this for one user's overall total; use avoma_user_engagement_list for a paginated per-participant breakdown, or avoma_engagement_summary_get for the equivalent summary across the whole organization. Requires a user uuid, typically obtained from avoma_users_list.

Parameters

Name

Type

Required

Description

from_date

string

Required

Start of the date range (inclusive), as an ISO 8601 UTC datetime. Only meetings that started at or after this time are included. Example: 2024-01-01T00:00:00Z

to_date

string

Required

End of the date range (inclusive), as an ISO 8601 UTC datetime. Only meetings that started at or before this time are included. Example: 2024-01-31T23:59:59Z

user_uuid

string

Required

UUID of the Avoma user to get the participant engagement summary for. Obtain this from avoma_users_list. Example: 3c1a1e2e-4b8a-4b6b-9b1a-2f6a7e1c9d10

is_call

boolean

Optional

Filter by meeting type: true for voice calls only, false for video meetings only. Leave unset to include both.

is_impromptu

boolean

Optional

Filter by whether the meeting was unscheduled/ad-hoc: true for impromptu meetings only, false for scheduled meetings only.

is_internal

boolean

Optional

Filter by attendee composition: true for internal-only meetings (no external attendees), false for meetings with at least one external attendee. Leave unset to include both.

meeting_outcome_uuid

array

Optional

Restrict the summary to meetings with one or more specific meeting outcome UUIDs. Each entry is sent as a repeated query parameter. Example: ["9c4b1e2e-4b8a-4b6b-9b1a-2f6a7e1c9d10"]

meeting_type_uuid

array

Optional

Restrict the summary to meetings with one or more specific meeting type UUIDs. Each entry is sent as a repeated query parameter. Example: ["7f2a1e2e-4b8a-4b6b-9b1a-2f6a7e1c9d10"]

participant_email

array

Optional

Restrict the summary to one or more specific participant email addresses. Each entry is sent as a repeated query parameter. Example: ["customer@example.com"]

recording_duration__gte

number

Optional

Only include meetings whose recording duration is greater than or equal to this many seconds.

recording_duration__lte

number

Optional

Only include meetings whose recording duration is less than or equal to this many seconds.

shared_meetings_only

boolean

Optional

If true, only include meetings that were shared with others.

For more tools, view docs.

Build your Agent

Same bearer token vault and scoped tool list across LangChain, OpenAI, Anthropic, and Google ADK.

import { ScalekitClient } from \"@scalekit-sdk/node\";
import { DynamicStructuredTool } from \"@langchain/core/tools\";
const sk = new ScalekitClient(
  process.env.SCALEKIT_ENVIRONMENT_URL,
  process.env.SCALEKIT_CLIENT_ID,
  process.env.SCALEKIT_CLIENT_SECRET,
);
const page = await sk.tools.listScopedTools(\"user_123\", {
  filter: { connectionNames: [\"avoma\"], toolNames: [
    \"avoma_meetings_list\",
    \"avoma_transcription_get\",
    \"avoma_notes_list\",
  ]}, pageSize: 100,
});

import OpenAI from \"openai\";
import { ScalekitClient } from \"@scalekit-sdk/node\";
const sk = new ScalekitClient(
  process.env.SCALEKIT_ENVIRONMENT_URL,
  process.env.SCALEKIT_CLIENT_ID,
  process.env.SCALEKIT_CLIENT_SECRET,
);
const page = await sk.tools.listScopedTools(\"user_123\", {
  filter: { connectionNames: [\"avoma\"], toolNames: [
    \"avoma_meetings_list\",
    \"avoma_transcription_get\",
    \"avoma_notes_list\",
  ]}, pageSize: 100,
});
const openai = new OpenAI();

import Anthropic from \"@anthropic-ai/sdk\";
import { ScalekitClient } from \"@scalekit-sdk/node\";
const sk = new ScalekitClient(
  process.env.SCALEKIT_ENVIRONMENT_URL,
  process.env.SCALEKIT_CLIENT_ID,
  process.env.SCALEKIT_CLIENT_SECRET,
);
const page = await sk.tools.listScopedTools(\"user_123\", {
  filter: { connectionNames: [\"avoma\"], toolNames: [
    \"avoma_meetings_list\",
    \"avoma_transcription_get\",
    \"avoma_notes_list\",
  ]}, pageSize: 100,
});
const anthropic = new Anthropic();

import { ScalekitClient } from \"@scalekit-sdk/node\";
const sk = new ScalekitClient(
  process.env.SCALEKIT_ENVIRONMENT_URL,
  process.env.SCALEKIT_CLIENT_ID,
  process.env.SCALEKIT_CLIENT_SECRET,
);
const page = await sk.tools.listScopedTools(\"user_123\", {
  filter: { connectionNames: [\"avoma\"], toolNames: [
    \"avoma_meetings_list\",
    \"avoma_transcription_get\",
    \"avoma_notes_list\",
  ]}, pageSize: 100,
});

Try these prompts

Copy a prompt into your agent. Each one maps to Avoma meeting notes for the signed-in user.

Coaching and next steps

Copy the prompt

Copied

Which discovery calls last week have Avoma notes I can review?

Copy the prompt

Copied

Summarize talk ratio and questions asked on the last Acme meeting.

Copy the prompt

Copied

What scorecard evaluations ran on yesterday's Globex call?

Transcripts and recall

Copy the prompt

Copied

Pull the transcript for yesterday's Globex pricing call.

Copy the prompt

Copied

What did the buyer say about budget on the Initech meeting?

Copy the prompt

Copied

List Avoma meetings from the last 14 days.

Notes and snippets

Copy the prompt

Copied

Show AI notes from the last Acme discovery meeting.

Copy the prompt

Copied

Which snippets were saved from the Umratech call?

Copy the prompt

Copied

Get the recording URL for the latest Initech demo.

SEE HOW AUTH WORKS

Your users connect once. Their Avoma bearer tokens stay vaulted, every call is checked, and every action is logged.

Authorize

Your user connects

Avoma

once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access

Who:

user ‘A’

when:

Once per user

access:

Limited to user

Store

Their

Avoma

token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection

vault:

encrypted

scope:

per-user

tokens:

auto-refreshed

Resolve

When your agent calls a

Avoma

tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs

speed:

~40ms

check:

before every call

seen by:

nobody

Audit

Every

Avoma

tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it

history:

90 days

export:

SIEM-ready

logged:

every call

Test other agents

Reuse the same per-user bearer token vault and audit chain on other call intelligence and CRM connectors.

Support and Ops Teams

Meeting prep

Pulls agenda, participant context, and open action items before every meeting.

GTM and RevOps Teams

Sales call prep agent

Reads tomorrow's calls from Google Calendar, mines past Granola notes and Attio history for context, and delivers each rep a prep brief in Slack, scoped to the calls that rep actually owns.

GTM and RevOps Teams

Deal intelligence agent

Pulls recent Gong calls, scores deal risk with an LLM, cross-references the record in Attio, and DMs each owner their at-risk deals in Slack. Every read is scoped to that rep's own access.

GTM and RevOps Teams

Revenue forecast commentary

Pulls open pipeline from Salesforce and HubSpot, calculates coverage against quota, flags at-risk stages, posts commentary to Slack, and logs every snapshot to Google Sheets.

Why Scalekit

Secure your agent's access. Connectors ship in minutes

01.

Shared tokens break per-user analytics

A shared Avoma bearer token makes every transcript lookup look like a bot. Scalekit resolves the credential of the actual user who triggered the agent, never a shared bot.

// shared key
audit → bot_acct

// scalekit
audit → user_abc ✓

02.

Authentication is not authorization

03.

Multi-tenancy is architectural

04.

Avoma today. Others tomorrow.

“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”

Venu Madhav Kattagoni

Head of Engineering / Von

FAQs

Frequently Asked Questions

Does the agent access Avoma as the user or a shared key?

Per-user resolution. Each tool call uses the signed-in user's Avoma bearer token, so meeting notes and transcripts attribute to that user in the audit log.

Where is the Avoma token stored?

In Scalekit's AES-256 vault, namespaced per tenant. You revoke access from one dashboard without rotating a shared secret across every agent.

Can I limit what the agent does in Avoma?

Yes. Filter tool names in listScopedTools (for example avoma_meetings_list only) and Scalekit checks that scope before the API call.

What happens when a user revokes access?

The next Avoma tool call fails closed for that user. Other users and other connectors are unaffected. The revoke is logged.

Does the agent see every recording in the workspace?

Only the meeting notes and recordings the authorized Avoma bearer token can already read. Scalekit does not broaden that access; it vaults and scopes the existing token.