Connect tl;dv¶
Outcome¶
Threadory will receive selected meetings, transcripts, summaries, and action items from a tl;dv workspace.
Before you begin¶
- an administrator or owner role in the Threadory project;
- a tl;dv workspace API key, available to a workspace administrator on an eligible tl;dv plan;
- a safe meeting filter defined in advance.
The API key applies to the entire workspace, which makes filtering especially important. Do not ingest every meeting by default when the project needs only a subset.
Connection profile¶
| Item | Minimum or expected behavior |
|---|---|
| Credential | Use a dedicated tl;dv workspace API key created by a workspace administrator. The key is not per-user. |
| Minimum access | tl;dv API keys have no granular scopes and can read the workspace. Meeting filters are therefore a required data boundary, not an optional convenience. |
| Identity | Synchronization uses the shared workspace credential. It is not attributed to each meeting participant. |
| Direction and entities | Inbound only: user, meeting, transcript_segment, and meeting_summary entities. No verified write-back to tl;dv is documented. |
| Delivery mode | Incremental polling runs every 60 minutes and is the verified baseline. Do not rely on the optional meeting.processed webhook unless a platform operator has validated provider signing in this deployment. |
Steps¶
- In tl;dv, open Settings → API & Integrations and create an API key.
- In Threadory, open Connectors → Add connector → tl;dv.
- Enter the tl;dv API Key.
- Select a transcript storage mode. Start with Truncate if the workflow does not require the full text.
- Configure Which meetings to ingest by participant, domain, title, calendar, or a combination of these filters.
- Use Preview filter and confirm that unrelated meetings are excluded. Preview does not save any data.
- Complete the installation and select Sync now.
Verify the result¶
- preview shows only the expected meetings;
- synchronization completes successfully in Activity;
- the meeting appears in Knowledge with a summary or transcript preview;
- action items are available in Reports.
Common problems¶
| Symptom | Cause | What to do |
|---|---|---|
| The API key is rejected | The key is inactive or does not belong to the workspace | Create a new workspace key and revoke the incorrect one |
| Preview is empty | There are no recent meetings or the filter is too narrow | Relax one filter and preview again |
| Unrelated meetings appear | All is selected or the filter is too broad | Stop synchronization, narrow the filter, and follow the data deletion procedure |
| The full transcript is missing | Truncate or Omit is selected | Change the setting only after reviewing access and cost implications |
Safe disconnection¶
Disconnecting stops future meeting imports but does not automatically remove meetings, transcript segments, summaries, or derived action items already stored in Threadory.
- Stop workflows that depend on newly imported meetings.
- Export required project data.
- Disconnect the tl;dv connector in Threadory.
- Revoke the workspace API key in tl;dv if it was dedicated to this connector.
- Apply the documented retention process to imported meeting data that must be removed.
Verify that the connector card is gone and no new tl;dv sync appears in Activity after the previous polling window. To recover, create a new workspace key, reconnect with the same reviewed filters, use Preview filter, and only then run Sync now. Data removed by retention can be recovered only from an approved export or operator-managed backup.
Next step¶
Complete your first closed loop.