Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Avoma

Avoma is an AI Meeting Assistant that automatically records, transcribes, and summarizes your meetings.

CategoryOther
Authenticationcustom
Version0.1.7
Published scopes0 published scopes
Last updatedSeptember 19, 2026

Overview

Connect Avoma with Flows360

Avoma is an AI Meeting Assistant that automatically records, transcribes, and summarizes your meetings.

Use the Avoma connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 3 actions and 4 triggers.

Available actions

  • Create Call
  • Get Meeting Recording
  • Get Meeting Transcription

Available triggers

  • New Note
  • New Meeting Scheduled
  • Meeting Rescheduled
  • Meeting Cancelled

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Avoma
  • Package: @activepieces/piece-avoma@0.1.7
  • Exact artifact digest: sha256:9cd0f8f38e12eedc4b4b42fb5e242c362f01868a831457c7769348469a5e8af3
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

SECRET TEXT. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Create Call (create_call), Creates a new call in Avoma Classification: read.
  • Get Meeting Recording (get_meeting_recording), Returns video and audio recording URLs for a given meeting Classification: read.
  • Get Meeting Transcription (get_meeting_transcription), Returns transcription with speakers, timestamps, and VTT file URL Classification: read.

Trigger contracts

  • New Note, webhook.
  • New Meeting Scheduled, webhook.
  • Meeting Rescheduled, webhook.
  • Meeting Cancelled, webhook.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects7
Supported actions3
TriggersNone published

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Create Call Yes No Creates a new call in Avoma
Get Meeting Recording Yes No Returns video and audio recording URLs for a given meeting
Get Meeting Transcription Yes No Returns transcription with speakers, timestamps, and VTT file URL
New Note Yes No webhook trigger declared by the pinned package.
New Meeting Scheduled Yes No webhook trigger declared by the pinned package.
Meeting Rescheduled Yes No webhook trigger declared by the pinned package.
Meeting Cancelled Yes No webhook trigger declared by the pinned package.

Supported actions

Create Call · Read

Creates a new call in Avoma

create_call · Risk: low · Retry: safe

Inputs

  • external_id · string · Required, Unique id of the call from the dialer system like hubspot, twilio, zoom, etc.
  • user_email · string · Required, Email of the user who made or received the call. This should be an Avoma user's email.
  • source · string · Required, Source of the call
  • direction · string · Required, Direction of the call
  • start_at · string · Required, Start time of the call
  • frm · string · Required, Phone number from which call was made (e.g., +11234567890)
  • to · string · Required, Phone number to which call was made (e.g., +12234567890)
  • recording_url · string · Required, URL of the recording of the call. This should be a public URL that Avoma can access.
  • participants · array · Required, List of participants in the call. First entry should be the prospect/lead.
  • end_at · string · Optional, End time of the call
  • frm_name · string · Optional, Name of the caller who made the call
  • to_name · string · Optional, Name of the person to whom call was made
  • answered · boolean · Optional, Whether the call was answered
  • is_voicemail · boolean · Optional, Indicates if the call is a voicemail
  • additional_details · string · Optional, Additional details of the call (JSON object as string)
Get Meeting Recording · Read

Returns video and audio recording URLs for a given meeting

get_meeting_recording · Risk: low · Retry: safe

Inputs

  • meeting_uuid · string · Required, Select a meeting from your Avoma account
Get Meeting Transcription · Read

Returns transcription with speakers, timestamps, and VTT file URL

get_meeting_transcription · Risk: low · Retry: safe

Inputs

  • transcription_uuid · string · Required, Select a transcription from your Avoma meetings

Setup

Setup

  1. Add the Avoma connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-avoma@0.1.7; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 3 actions and 4 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Avoma connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-avoma@0.1.7 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com