Tldv

Syncs meeting transcripts and highlights into your CRM, drafts follow up emails based on actual conversation data, and archives recordings to your cloud storage.

Try Tldv in Ceven

Ask Ceven anything
Standard

Why use Ceven?

  1. AI native Tldv integration

    • Describe the outcome and Ceven picks the right Tldv calls, fills the parameters, and checks the result.
    • Structured, agent friendly tool schemas so each call runs reliably instead of by guesswork.
    • Rich coverage for reading, writing, and querying your Tldv data, across all 7 of its actions.
  2. Managed auth

    • Built in OAuth with automatic token refresh and rotation.
    • One place to manage, scope, and revoke Tldv access.
    • Per user and per environment credentials instead of shared keys.
  3. Agent optimized design

    • Actions are tuned from real success and error rates so reliability climbs over time.
    • Full execution logs so you always know what ran in Tldv, when, and on whose behalf.
    • The agent pauses and asks when Tldv is unclear instead of plowing ahead.
  4. Enterprise grade security

    • Fine grained access so you control which agents and people can reach Tldv.
    • Least privilege by default, read scopes first and only the writes a workflow needs.
    • A full audit trail of every Tldv action to support review and sign off.

Supported tools

Every action Ceven's agents can run on Tldv, and when to use it.

Get meeting
Pull detailed metadata for a specific call including the name, date, duration, and organizer details.
Get meeting highlights
Retrieve human readable notes and key takeaways from a completed meeting by its ID.
Get meeting transcript
Pull the full text of a call with speaker names and timestamps for every segment.
List meetings
Retrieve a paginated list of all recorded meetings to find specific calls by date or organizer.
Download recording
Get a signed URL to download the actual video or audio file for external archiving.
Import meeting
Upload a recording from a public URL in formats like mp4 or mp3 to get it transcribed.
Check API health
Verify if the Tldv service is operational before starting a bulk transcription workflow.
Download Meeting Recording
Tool to download a meeting recording file. Returns the recording file by following the API's redirect to a signed download URL (valid for 6 hours). Use when you need to retrieve the actual recording content for a specific meeting.

8 actions · scroll to see them all

Frequently asked questions

Ceven polls the Tldv API to check the status of your recordings. It is important to know that transcripts and highlights are only returned once the Tldv processing engine has fully completed the transcription job. If a workflow triggers immediately after a call ends, the agent may find the transcript empty. To solve this, Ceven implements a retry logic that waits for the status to move to complete before attempting to pull the text. This ensures your summaries are based on the final version of the conversation and not a partial snippet. You can configure the wait time in your workflow settings if you have exceptionally long meetings that take more time to process.
Yes. Using the import meeting action, Ceven can take a publicly accessible URL pointing to a supported media file like mp4 or wav and send it to Tldv for processing. This is useful when you have recordings stored in a temporary bucket or a different tool that does not have a native Tldv integration. Once the import job is submitted, Ceven receives a job ID and monitors the progress. Once Tldv finishes the transcription, the agent treats it like any other native recording, allowing you to run the same summary and action item workflows you use for your live Zoom or Google Meet calls.
If a recording is deleted within the Tldv dashboard, the API will return a not found error the next time Ceven attempts to access that meeting ID. If you have already synced the transcript or highlights to a downstream system like Notion or Salesforce, that data remains intact because Ceven performs a copy of the text. However, the link to the video recording will break. We recommend setting up an archival workflow that uses the download recording action to move a copy of the video to your own secure cloud storage to prevent data loss from accidental deletions in the source tool.
Yes. Tldv imposes rate limits on their API endpoints to ensure platform stability. If your workflow attempts to pull transcripts for hundreds of meetings simultaneously, you may encounter a 429 too many requests error. Ceven manages this by implementing an exponential backoff strategy, which means the agent will automatically pause and retry the request after a short delay. For most users, this happens silently in the background. If you are running massive bulk imports or migrations, we suggest spacing out your workflow triggers to avoid hitting these limits and causing delays in your automation pipeline.
Ceven relies on the speaker diarization performed by Tldv. When the agent pulls a transcript, it receives a series of segments, each tagged with a speaker label and a timestamp. The agent uses these labels to distinguish between the host and the guest. If the Tldv recording has not had the speakers manually named in the dashboard, they will appear as Speaker 1 or Speaker 2. You can tell the Ceven agent to infer the names based on the introductory remarks of the call, or you can update the names in Tldv first to ensure the downstream summaries use the correct real names.
Ceven achieves this by listing your meetings and then iterating through the highlights or transcripts of each call. While Tldv provides the raw data, Ceven provides the intelligence to filter that data. You can ask the agent to find every time a specific competitor was mentioned across all calls in the last month. The agent will fetch the list of meetings, pull the text for each, and return a compiled list of quotes and links. This turns your Tldv library into a searchable knowledge base for your entire team without requiring you to open every single video.
No. The signed download URLs generated by the Tldv API are temporary and typically expire after six hours. This is a security measure to prevent unauthorized access to your private recordings. Because of this, Ceven cannot simply store the link for later use. If your workflow requires the actual video file, the agent must call the download recording action in real time to generate a fresh link and then immediately stream that file to your destination, such as an S3 bucket or Google Drive. Once the file is moved, you have a permanent copy that does not rely on the Tldv temporary token.
Ceven operates based on the permissions granted to the API token used for the connection. If the account connecting to Ceven has access to specific folders or meetings, the agent can see them. Tldv uses a permission model where visibility is tied to the user who authorized the app. If you want to limit what the agent can see, we recommend using a dedicated service account with restricted access to only the necessary meeting spaces. This ensures that sensitive HR or leadership calls remain private while still allowing the agent to process sales and product feedback calls for the rest of the organization.

Alternatives to Tldv

Other tools that solve a similar problem. Ceven supports these too, so you can switch or run more than one at once.

Try Ceven on your stack

Plug Ceven on top of the tools you already run. Connect Tldv and the rest of your stack, describe the outcome, and its agents handle the work end to end, days of it in minutes.

Get started for free