What to Do With Your tl;dv Recordings: Turn Calls Into Content

Last updated 2026-06-12 · Reviewed by Steven Ellis

The 3-step workflow

tl;dv records the call, transcribes it, and files it in your meeting library. When the session ends and the transcript is ready, a webhook fires to Voiceloop — or a Zapier trigger activates if that's the route you've set up. The transcript arrives in Voiceloop, gets run through a 22-format content extraction library, and produces a batch of roughly 33 posts: 22–30 short Threads posts drawn from distinct moments in the call, three long-form LinkedIn posts built around your session's insight anchors, and an optional Instagram carousel. Every post is written in the voice Voiceloop has calibrated from your transcript history — not a generic AI voice, but the specific way you explain things, frame problems, and challenge your clients. The batch lands in your approval queue. You skim, approve what belongs on your feed, and Voiceloop ships the approved posts to your connected platforms on the schedule you've set. tl;dv handled the internal record. Voiceloop handles the feed.

Why tl;dv users need this

tl;dv built its reputation on speed — fast transcripts, tight AI summaries, and a product that gives you your call notes before you've had a chance to forget what was discussed. For users who run a lot of calls, that internal efficiency matters. What it doesn't address is the external gap: everything you said in that call that should have reached a broader audience and didn't. The meeting summary is for you. Your audience needs the ideas, not the debrief.

The coaches and consultants who use tl;dv tend to be high-volume. Multiple calls a day, tight turnaround, heavy emphasis on using their time efficiently. That's exactly the profile where a content backlog grows fastest — because efficiency-focused operators don't have time to manually repurpose calls into posts. They're already time-optimized. Voiceloop is the system that closes the gap: it runs in the background, pulling content from every call without adding a task to your day.

The recording graveyard for tl;dv users is often enormous. Six months of meetings, each one a potential batch of 33 posts, all of it archived and inactive. Your clients got the summary. Your audience got nothing. That ratio flips the moment you connect the webhook.

Setup walkthrough

Via tl;dv webhooks

tl;dv supports outbound webhooks for meeting completion events. Setup:

1. Log into Voiceloop and go to Integrations → tl;dv. Copy your Voiceloop webhook URL.
2. In tl;dv, navigate to Settings → Integrations and find the Webhooks section. Add a new webhook and paste your Voiceloop URL.
3. Set the trigger to fire on meeting completion — when tl;dv has finished processing the transcript and the full recording is available.
4. Save. Every future tl;dv recording will automatically send its transcript to Voiceloop when it finishes.

Via Zapier

If you prefer Zapier or want more filtering control:

1. Create a new Zap with tl;dv as the trigger app and "Meeting Completed" (or equivalent) as the trigger event.
2. Connect your tl;dv account and test to confirm the trigger fires correctly on a real recording.
3. Add a Voiceloop action step using a webhook POST. Map the transcript data from tl;dv's output to your Voiceloop webhook URL.
4. Apply any filters you want — for example, only trigger on calls in your coaching workspace, not internal team meetings.
5. Turn the Zap on.

Zapier adds one layer of configuration overhead but gives you more granular control over which recordings route to Voiceloop.

Connect your social accounts

Before posts can ship, authorize Threads, LinkedIn, and/or Instagram in Voiceloop → Accounts. Set your preferred posting cadence. From this point forward, every tl;dv recording that matches your trigger criteria flows into your approval queue automatically.

Note: tl;dv connects to Voiceloop via webhook or Zapier — not a direct OAuth integration. If you're evaluating which recorder to standardize on for content output, Fathom is Voiceloop's native integration — the deepest available connection, with no middleware. If you're already committed to tl;dv, the webhook path works cleanly for this workflow.

What you get

Every tl;dv call that flows into Voiceloop produces a full content batch:

Threads posts (22–30 per call): Short posts from distinct moments in the session. The extraction library pulls across 22 formats — reply-style posts, authority statements, client perspective observations, story hooks, direct challenges — so your Threads feed reads like a person, not a content schedule. The variety is built into the extraction logic, not randomized. Different formats surface different types of value from the same call.

LinkedIn posts (3 per call): Long-form pieces for your professional audience. Each one anchors to a distinct high-value moment from the session — the framework you walked your client through, the market misconception you corrected, the decision criteria you laid out that most people in your space don't articulate clearly. These are the posts that compound: they're findable, shareable, and they establish expertise with people who haven't heard of you yet.

Instagram carousel (optional, 1 per call): Enable in Voiceloop settings if Instagram is part of your publishing strategy. One polished carousel per call, built around the session's core insight.

Voice calibration: Voiceloop builds a voice profile from your transcript data — your sentence rhythm, your vocabulary, how you open a point and close it. The profile refines with each batch. The output stops reading like AI and starts reading like you, usually within the first three to five calls.

Approval queue: Nothing ships without your explicit approval. The queue is fast to review — most coaches clear a full 33-post batch in under ten minutes. Skip anything that doesn't fit, hold posts for later, or delete a batch entirely if the call was internal.

Mini-FAQ

tl;dv already gives me AI summaries and action items. Why do I need Voiceloop too?

Different outputs, different audiences. tl;dv's AI summaries are internal tools — they make your internal workflow faster. Voiceloop's output is external — it builds your audience, establishes your authority with strangers, and creates a feed that represents your thinking at the level your clients already know it. They don't compete; they run off the same recording for different purposes.

Can I retroactively run past tl;dv recordings through Voiceloop?

The standard webhook integration is forward-looking — it captures new recordings as they complete. For processing historical recordings, contact the Voiceloop team at hello@voiceloop.app to discuss batch import options. Your library is the asset — it shouldn't stay archived.

---

Using multiple recorders? Every source can connect independently and feeds the same approval queue. See also: Fathom (native), Zoom, Grain, Circleback, Fireflies. For coaches specifically: /for/business-coaches/ and /for/sales-coaches/. Pricing at /pricing.

Frequently asked questions

Does tl;dv's integration with Voiceloop require a paid tl;dv plan?

tl;dv's webhook and Zapier integration features are available on certain plan tiers. Check tl;dv's current plan details to confirm webhook access before setting up the connection.

I use tl;dv for both sales calls and team meetings — will Voiceloop pull from all of them?

Voiceloop processes every transcript that comes through the connected webhook. If you want to limit which calls generate content batches, you can filter at the Zapier layer (e.g., only trigger on calls in specific workspaces) or review and discard batches from calls you don't want to publish from.

Other integrations