The Slack integration sends meeting data from tl;dv into Slack — to a channel or as a direct message — automatically. Build workflows that post meeting notes, transcripts, recordings, or a custom-formatted summary the moment a recording is ready. Each workflow runs on every new recording that matches the conditions you set.
Workflow types
When you open the Slack integration, you choose between two workflow scopes:
Workflow type | Applies to |
Individual workflow | Only meetings recorded by you |
Team workflow | Meetings recorded by your team members (excludes team admins and billing group admins) |
Use an individual workflow for personal experiments, and a team workflow when you want consistent automation across the team.
The two actions
The Slack integration offers two actions. Setup is identical for both — the only difference is the destination.
Action | What it does |
Send recording to a Slack channel | Posts the message to a specific channel |
Send recording as a Direct Message | Sends the message as a DM to a user |
Before you build: disconnect any legacy Slack integration
🚨 If you've previously connected Slack to tl;dv, disconnect the legacy integration before building a new workflow. The legacy and new setups can interfere with each other and cause inconsistent message delivery. You'll reconnect Slack during the new workflow setup (see Step 5).
In tl;dv, click Integrations in the left sidebar.
Open the My workflows tab or Team workflows where the legacy integration was set up.
Find the Slack workflow row and click Edit.
Scroll to the bottom of the configuration panel and click Disconnect integration.
⚠️ Don't open the Slack tile from the Marketplace tab to disconnect — that path now leads to the new integration setup, not the legacy one.
Build a workflow
1. Open the Slack integration
In tl;dv, click Integrations in the left sidebar, then click the Slack tile in the Marketplace tab.
2. Choose a workflow type
Select Individual workflow or Team workflow, then click Confirm.
3. Pick an action
Choose Send recording to a Slack channel or Send recording as a Direct Message, then click Try it now.
4. Set the trigger and conditions
Under Trigger this workflow when, select A new meeting recording is ready.
(Optional) Click Add condition to limit when the workflow runs. Available criteria include Meeting type, Role, Personal attendance, Meeting title, Participant email, and Email domain.
If you add multiple conditions, choose All (every condition must match) or Any (one match is enough).
Click Continue.
💡 Use conditions to route meetings to the right place. For example, send external sales calls to #sales-wins and internal team meetings to #team-updates by creating separate workflows with different domain conditions.
5. Connect your Slack account
The first time you build a workflow, click Connect to Slack. A Slack OAuth popup opens — choose the workspace you want to link and click Allow to authorize the tl;dv app. You only need to do this once per tl;dv account.
Sending to a private channel
Private channels don't appear in the Slack channel dropdown by default. To make a private channel available:
Open Slack and go to the private channel you want to use.
Click the channel name at the top to open channel details, then click the Integrations tab.
Click Add apps, search for tl;dv, and add the app to the channel.
Return to tl;dv — the private channel will now appear in the channel selector.
💡 You only need to do this once per private channel. Public channels work out of the box without this step.
6. Configure the message
Account shows the connected Slack workspace. If you manage multiple workspaces, you can switch from the menu next to it.
Pick the destination:
For the channel action: choose a Slack channel from the dropdown.
For the DM action: choose a Slack user from the dropdown.
In Content — what should be added to the message?, decide how to fill the message:
Insert tl;dv data — click the variable chips below the field (Meeting title, AI Notes, Transcript, Participants email) or open More data for Meeting date, Meeting URL, and Participants name.
Custom prompt — switch on the Custom prompt toggle in the top-right of the field, then write a free-text instruction. tl;dv runs the prompt against the meeting and posts the result in Slack.
7. Test the workflow
Click Continue to reach the Test step.
Select a recent meeting and click Test workflow. tl;dv runs the workflow once so you can verify the message in Slack before going live.
When the test completes successfully, click Activate workflow. The toggle in the top right becomes active and the workflow runs on every matching recording from now on.
8. (Optional) Rename your workflow
Click the workflow title at the top of the page (e.g., Integration for Slack) and rename it to something descriptive like Sales — Wins channel or CS — Account updates DM. This makes the workflow easier to find later in My workflows or Team workflows.
Use custom prompts effectively
Custom prompts let you generate exactly the message you want for Slack. They are useful when the default AI Notes are too long, too detailed, or not formatted the way your team reads.
💡 Slack messages have a per-message length limit of around 3,000–4,000 characters, and long AI Notes can get cut off. A custom prompt is the cleanest fix — you can cap the output (e.g., "keep under 3,000 characters") and control the format in one place.
Example: A Slack-optimized summary under 1,000 characters
Generate concise, scannable meeting notes optimized for Slack sharing. Keep total output under 1,000 characters.
Rules:
- Lead with decisions and outcomes, not discussion recap
- Every action item must have an owner and deadline
- Skip pleasantries, greetings, and off-topic discussion
- If a decision was not reached, say so explicitly
- Use plain language. No corporate jargon or filler
- Do not speculate. Only include what was actually said
Output format:
📋 Meeting: [name]
📅 Date: [date]
✅ Decisions: [bulleted list]
🎯 Action items: [bulleted list with owner and deadline]
Tips for writing prompts:
Be specific about format. Tell the prompt to use bullets, emoji headers, or a fixed template — Slack readers scan, so structure matters.
Constrain length. Without an instruction, output can run long. Add "keep under 1,000 characters" or "3 bullets maximum".
Handle empty cases. Tell tl;dv what to write when the topic isn't discussed (e.g., "If no decisions were made, write 'No decisions this meeting.'").
Common questions
Why didn't my workflow run on a meeting?
Check that:
The workflow toggle at the top right of the workflow page is ON.
The meeting matches the conditions you set.
The recording's creator is in scope for the workflow:
Individual workflows only trigger on meetings recorded by you.
Team workflows only trigger on meetings recorded by team members. They don't apply to team admins or billing group admins, so if you're an admin, your own meetings won't trigger a team workflow.
A private channel isn't showing up in the channel dropdown. What do I do?
Private channels need the tl;dv app added from Slack first. Open the private channel in Slack → click the channel name → Integrations tab → Add apps → search for tl;dv and add it. The channel will then appear in the tl;dv channel selector.
Can I send the same meeting to multiple channels?
Yes. Create one workflow per destination — Slack workflows don't fan out to multiple channels from a single workflow. Using conditions, you can also route different meeting types to different channels.
The AI Notes are getting cut off in Slack. What do I do?
Slack's per-message limit is around 3,000–4,000 characters, and long meetings can produce notes that exceed it. Switch on Custom prompt for the Content field and instruct tl;dv to keep the output under a specific character count (for example, "keep under 3,000 characters"). See the Use custom prompts effectively section for an example.
Will the recording link be clickable in Slack?
Yes. When you insert the Meeting URL variable, Slack renders it as a clickable link to the tl;dv recording.