Connect tl;dv and point it at Veew

Connect

1. 1In tl;dv (tldv.io), open Settings → Personal settings → API keys and generate a key. Copy it right away. API keys need tl;dv's Pro or Business plan; there is no API on the free plan.
2. 2In Veew, go to Settings → Integrations. tl;dv is under Your connections: it is yours, not the workspace's, because a tl;dv key only sees the meetings of the person who made it. Paste the key and choose Connect tl;dv.
3. 3Your last 14 days of calls import straight away. The card now shows a Webhook URL and an Authorization header.

Point tl;dv at Veew

tl;dv has no way for an app to sign itself up for notifications, so you tell it where to send them. This is a one-time step; skip it and Veew still checks for new notes every few minutes.

1. 1Back in tl;dv, open Settings → Webhooks and click Configure new webhook.
2. 2Choose the MeetingReady event, at the User level so only your own meetings are sent. Paste the Webhook URL from the Veew card as the Endpoint URL.
3. 3Add a custom header named Authorization and paste the header value from the Veew card (it starts with Bearer). This is how Veew knows a delivery came from your tl;dv; a delivery without it is ignored. Save and activate.
4. 4From now on each finished set of notes arrives in Veew as soon as tl;dv is done with it.

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 tl;dv's AI notes, the topics and the points under them, never the recording or the transcript. What a key can read follows the plan of the meeting's organiser, so a call organised by someone on tl;dv's free plan may not come through even though you can see it in tl;dv. If you disconnect, delete the webhook in tl;dv too; already-synced notes stay on their deals.