Connect Avoma

Before you start

Avoma's API is on its Organization and Enterprise plans, not Startup. Only an Avoma admin can create API keys, so if that is not you, send this guide to whoever administers Avoma for your team.

Create the key

1. 1In Avoma (app.avoma.com), an admin opens Settings → Organization → Developer and clicks Add API Key.
2. 2Choose the scope User – limited access and pick the person the key is for. That key sees only that person's meetings, which is what you want: each Veew member connects their own so calls are filed under the right name. User – full access adds their private meetings. Avoid Organization – limited access: it would file everyone's calls under one person.
3. 3Copy the whole key string, CLIENT_KEY:CLIENT_SECRET, and pass it to the person it belongs to.

Connect

1. 1In Veew, go to Settings → Integrations. Avoma is under Your connections: it is yours, not the workspace's. Paste the key and choose Connect Avoma.
2. 2Your last 14 days of customer calls import straight away. Veew also registers a webhook with Avoma, so from then on each meeting's AI notes arrive as soon as Avoma has written them. If Avoma refuses the webhook (the key's scope or the plan does not allow it), Veew still checks for new notes every few minutes.

What Veew does with a call

Calls with someone from outside your company file themselves against the matching deal by the people and company on the invite; a call that does not match sits on Home until you attach it to a deal or dismiss it. Internal meetings are skipped.

Veew reads Avoma's AI notes, never the recording or the transcript. Disconnecting removes Veew's webhook from Avoma; already-synced notes stay on their deals.