Connectorstl;dv

Connect tl;dv

Connect tl;dv with an API key for the organization or yourself, see which meetings Gurusup reads, bring in past meetings, and fix a key that tl;dv refuses.

Admins connect tl;dv for the organization, and each person can connect their own key while an admin lets members do so. From each finished meeting Gurusup learns what was said, who was there and what the notes capture, so you can ask "Which objections came up in this month's demos, and what does our pricing page say about them?" and get the transcript joined with your docs. Gurusup reads text only: no video and no audio. Gurusup only reads tl;dv and adds nothing there.

At a glance

TopicDetails
Who can connectAdmins, always, for the organization. Any member or admin with their own key, while Let members connect their own account is on.
What you needA tl;dv API key. tl;dv gives API access on its Pro and Business plans.
What Gurusup readsEvery meeting the key can read once tl;dv has a transcript: details, notes and transcript
How changes arriveGurusup checks about every 15 minutes
Past contentImport history, from last week to last year
Knowledge accessDefault access, Restricted or Private, per key. A personal key starts as Private, an organization key as Default access. See Who can read it.

Before you start

  • To connect your own key, Let members connect their own account is on. If it is not, an admin turns it on: see Let members connect their own key. Admins can connect for the organization without it.
  • Your tl;dv plan includes API access. Gurusup's error says tl;dv's Pro and Business plans do.
  • Use your own key. Which meetings a key can read depends on the permissions of the person who owns it in tl;dv.
  • Each person has one connection of their own. The organization can have several, each with its own Knowledge access.

A key brings in every meeting its owner can read, and Gurusup shares what it learns according to its knowledge access. A personal key starts as Private, so only you read those meetings until you choose otherwise. An organization key starts as Default access: choose Restricted before you connect to limit who reads it.

Let members connect their own key

Admins only. Organizations with an active tl;dv key were turned on automatically.

Open tl;dv

In the sidebar, open Sources, then Catalog, and open tl;dv. The page says "Personal source".

Turn the switch on

Under Members, switch on Let members connect their own account. The row adds "Each person chooses who can read what they add."

Switch it off to stop members connecting. With personal keys connected, Gurusup asks "Stop members connecting their own tl;dv?" and says "This disconnects N personal accounts. Organization connections keep working, and what Gurusup already learned stays. People can connect again if you turn it back on." Click Turn off and disconnect. With none connected, it turns off at once. While it is off, Your accounts is hidden for anyone with no account there, and admins can still connect for the organization.

Connect tl;dv

Admins click Connect for the organization. Anyone else, admins too, clicks Connect for their own key.

Open tl;dv

In the sidebar, open Sources, then Catalog, and click Connect on tl;dv. Its page opens and says "Personal source". It lists Organization accounts ("Your team uses these accounts; administrators manage them.") and, while members may connect their own key, Your accounts.

Create the key

For the organization, click Connect for the organization next to Organization accounts: the dialog is Connect tl;dv for the organization. For your own key, click Connect next to Your accounts: the dialog is Connect tl;dv. Below the fields, click Show steps, then Open tl;dv, and in tl;dv open Integrations > API, generate a key and copy it.

Paste it and check the count

Paste the key in API key (the hint reads "A key like 3e892937-…"). Gurusup says "Reading the meetings this key reaches in tl;dv…" and then shows What this key reads: "This key lists N meetings" and one row per folder. Connect stays off until the check passes.

Choose who can read it

Under Knowledge access, a personal key starts as Private: "Only you. Administrators can't read it either." Choose Restricted and pick people to share the meetings with them ("You and the people you choose"), or Default access to let everyone read them according to what they are already allowed to see.

Connect

Click Connect. A message says "tl;dv connected." and the connection shows with a Connected badge. Its name is "tl;dv - " followed by the name of the person who connected it, or the part of their email before the @ if they have no name, with " 2", " 3" and so on added if that name is taken, up to 110 characters. You can rename it: see Rename a connection.

The count shows a + from 10,000 meetings. The folders are information only, not a filter: Gurusup reads every meeting the key lists.

What Gurusup reads

Each meeting becomes one document, added only once tl;dv has finished a non-empty transcript.

PartWhat Gurusup keeps
DetailsTitle, date, duration, organizer, invitees with their email, folders and the link "Open in tl;dv"
Notestl;dv's notes. When a meeting has no written notes, its topics and their summaries.
TranscriptLine by line, with the speaker and the minute of each line

What Gurusup does not read

  • Video and audio.
  • Meetings the key cannot read in tl;dv.
  • A meeting with no finished transcript yet. Gurusup looks again at its next check.

How changes arrive

EventWhat Gurusup does
A meeting gets its transcriptAdds it at the next check, as long as it was held after you connected and in the last 7 days
A meeting has no transcript yetSkips it and looks again at each check for 7 days
tl;dv refuses or fails to give one meeting's transcriptSkips that meeting for this check. The other meetings in the same check still come in, and Import history keeps going.
Gurusup could not finish its checks for more than 7 days, for example because tl;dv kept failingAt the next check it starts from the last check that finished, never before you connected, so meetings held during the gap come in
Several keys of your organization can read the same new meetingKeeps one copy, but only when the people allowed to read each key are exactly the same. If they differ, each key keeps its own copy, so nobody loses access. Import history does not merge past meetings.
The key that held the copy no longer serves the same readers, for example its access changed or it was disconnectedThe key that skipped it reads the meeting itself at its next check
Someone edits the notes laterNothing. Gurusup adds each meeting once.
A meeting is deleted in tl;dvNothing. What Gurusup learned stays.
A meeting was held before you connected, or became available more than 7 days after it was heldNot read. Use Import history.

Gurusup checks about every 15 minutes, which is how often it looks, not a delivery promise. When you connect, only new meetings come in. The History section says "Only new content comes in until you import past content." Follow each meeting on Follow ingestion.

Import past work

Open Import history

Open your tl;dv page from Sources. Under History, click Import history.

Pick how far back

Pick Last week, Last month, Last 3 months, Last 6 months or Last year. Gurusup counts the meetings in that window and shows what the import would use out of what you have left this month, in euros.

Import

Click Import. When it finishes, the row reads, for example, "Imported the last month".

A window you already imported shows "Already imported", and you can always pick a longer one. What happens when the import costs more than you have left, or stops, is in Import history.

Who can read it

Each tl;dv key is its own source, with its own access.

Knowledge accessWho reads it in Brain
Default accessEveryone, according to what they are already allowed to see: admins every category, members and agent accounts the categories an admin granted them.
RestrictedOnly the people you pick. Administrators are not included unless you pick them.
PrivateOnly you. Administrators are not included.

Gurusup does not copy who can see a meeting in tl;dv. Set the access before you connect and it applies before Gurusup reads anything. To change it later, open the key's page and change Access mode under Knowledge access; it saves as soon as you change it. Restricting later only covers meetings that arrive after that. See Restrict a source to specific people.

Who sees a personal key

  • Only you manage your connection and its key. An admin can disconnect it but cannot open it: asking for its folders returns "This tl;dv connection doesn't exist."
  • Only you can reconnect it. Anyone else gets "Only the person who connected this tl;dv account can reconnect it." Reconnecting replaces the key of that same connection and never changes its owner.

Organization keys

A key added with Connect for the organization has no owner. Admins manage it under Organization accounts (Rename and Manage settings are in each row's menu): they reconnect it, import history and disconnect it there. It keeps working while Let members connect their own account is off.

Check that it worked

Check the badge

On Sources, the tl;dv row under Personal sources (Company sources for an organization key) reads Connected. Open it to see the account under Organization accounts or Your accounts.

Hold a meeting

Record a short meeting in tl;dv and wait until it has a transcript.

Follow it

Open Ingest and pick the tl;dv source in the filter. The meeting moves to Learned within about 15 minutes of its transcript.

Reconnect

If tl;dv stops accepting a key, the connection shows Needs reconnect. Click Reconnect on the account's row and paste a new key.

Only the person who connected a personal key can reconnect it. Create a new key in tl;dv and click Reconnect on your account. Gurusup replaces only the key; the connection, owner, access and progress stay. An admin reconnects an organization key from its page. A plan without API access, or tl;dv being busy or down, does not mark a connection as needing a reconnect.

Disconnect

Open your tl;dv page and choose Disconnect in the menu of your account, or in the Danger zone. It removes only that connection: Gurusup deletes the key it stored, and what it learned stays. An admin can disconnect someone's personal key too, or all of them by switching off Let members connect their own account. The key stays valid until you delete it in tl;dv. See Remove, disconnect and what stays.

If it does not work

These show under the key while Gurusup reads it, or after "Could not connect tl;dv." when you click Connect:

MessageWhat to do
"This key isn't valid. Generate a new one in tl;dv: Integrations > API."Generate a new key and paste it.
"tl;dv refused this key. Check the key is active and that your tl;dv plan includes API access (Pro or Business)."Check the key is active in tl;dv and that your plan includes the API.
"We couldn't read your tl;dv workspace because of a problem on our side. Nothing was connected. We have logged the problem. Contact support for help."Contact support.
"We couldn't connect tl;dv because of a problem on our side. Nothing was connected. Try again in a few minutes, and contact support if it keeps failing."Try again later. Contact support if it keeps happening.
"We couldn't read your tl;dv folders because of a problem on our side. Your connection is unchanged. We've logged the problem. Contact support for help."The connection still works. Contact support if it keeps happening.
"This tl;dv connection was removed. Add a new connection with your API key."Connect again from your tl;dv page.
"An admin has to make tl;dv available before you can connect your account."Under the key while you paste it. Ask an admin to turn on Let members connect their own account.
"This application is disabled for your organization. Ask an administrator to enable it."When you manage or reconnect your own key after an admin switched the setting off. Ask an admin to turn it on.
"Connecting your own account to this app is turned off. Ask an administrator to let members connect their own account."You are a member and Let members connect their own account is off. Ask an admin to turn it on.
"Connecting your own account to this app is turned off. Connect it for the organization, or turn on Let members connect their own account in the app's settings."You are an admin and it is off. Click Connect for the organization, or turn the switch on.
"To connect your own account, turn on “Let members connect their own account” above."The hint on the off Connect button for admins. A member's hint reads "Ask an administrator to let members connect their own tl;dv account."
"Only the person who connected this tl;dv account can reconnect it."Ask the person who connected it, or disconnect it (admins) and let them connect again.
"This tl;dv connection doesn't exist."You asked for the folders of a connection that is not yours or no longer exists.
"The import didn't finish. Try again, and contact support if it keeps failing."Click Try again. If it keeps failing, contact support.
Meetings stop arrivingWhat to do
The badge reads Needs reconnectSee Reconnect.
The meeting has no finished transcriptWait. Gurusup looks again for 7 days after the meeting.
tl;dv failed several times in a row during an Import historyThe import stops with "The import didn't finish." Click Try again.
The meeting is older than the connectionUse Import history.
The key's owner cannot read the meeting in tl;dvUse a key from someone who can.
An admin switched off Let members connect their own accountPersonal keys stop capturing. Ask an admin to turn it back on and connect again. Organization keys keep working.
Ingestion paused, Demo Mode, or the item Paused on IngestSee Connector troubleshooting.

Still stuck? Contact support with the meeting's title and when it was held.