Provider guides
Avoma
What’s supported
Supported actions
This connector supports:- Read Actions, including full historic backfill and incremental read.
- Write Actions.
- Proxy Actions, using the base URL
https://api.avoma.com.
Supported Objects
The Avoma connector supports reading to the following objects:- calls
- custom_categories
- meetings
- notes
- scorecard_evaluations
- scorecards
- smart_categories
- transcriptions
- template
- users
Example integration
For an example manifest file of a Avoma integration, visit our samples repo on Github.Using the connector
This connector uses API Key authentication, so you do not need to configure a Provider App before getting started. (Provider Apps are only required for providers using the OAuth2 Authorization Code grant type.) To integrate with Avoma: Create a manifest file similar to the example above. Deploy it using the amp CLI. Embed the InstallIntegration UI component, which will prompt the customer for an API key.- Start using the connector!
- If your integration has Read Actions, you’ll start getting webhook messages.
- If your integration has Write Actions, you can start making API calls to our Write API.
- If your integration has Proxy Actions, you can start making Proxy API calls.