How to connect Loom to Slack so the video replaces the meeting

Async video works when it replaces a meeting. It fails when it becomes a second channel of things people feel obliged to watch on top of everything else, and the difference is almost entirely about whether the right people know a specific video is for them.

A link dropped into a general channel has neither of those properties. Getting it right means routing by audience, making the content skimmable before anybody commits eight minutes, and knowing whether the people who needed to watch actually did.

What we'll cover

• When a video is the right format
• The problem with a link in a channel
• Building it with CodeWords
• Making a video skimmable
• Routing by audience
• Closing the loop on whether it was watched
• Video as a record, not just a message
• Replying, and keeping the conversation together
• Making it survive
• Limits worth knowing about
• What to set up first
• Frequently asked questions

When a video is the right format

Worth being honest about, because the integration only helps if the videos are worth watching.

Showing something on a screen. A bug, a design, a flow — things that take four paragraphs to describe and ten seconds to show.

Explaining reasoning behind a decision, where tone carries information that text loses.

A walkthrough somebody will refer back to, which is a recording that earns its production cost over many viewings.

Not for anything requiring a decision from several people, which needs discussion rather than broadcast.

Not for anything short. A video that says what two sentences would say wastes the viewer's time in a way text does not, because text can be skimmed and video cannot.

Not as a status update to a group, which is where async video most often goes wrong — a weekly recorded update that nobody watches after the third week.

The problem with a link in a channel

It is addressed to nobody, so everybody assumes somebody else is the audience.

There is no indication of length, and length is the first thing a viewer wants to know.

There is no indication of subject beyond a title, which is often whatever Loom defaulted to.

It competes with text, which can be read in the channel while a video requires leaving it.

It has no deadline, so watching it is always something to do later, and later does not arrive.

Each of those is fixable in the message itself, which is most of what a good integration does here.

Building it with CodeWords

CodeWords connects to more than 3,000 integrations, and the connection is made once and reused.

1. Open CodeWords and start a new automation.
2. Describe what should happen in plain language to Cody, the automation builder: which recordings, who the audience is, and what the message should say.
3. Authorize the connection to Loom and to your Slack workspace.
4. Describe the exceptions: a video with no transcript yet, a private recording, a workspace member who cannot be mapped.
5. Test with your own recordings into a test channel before anything reaches the team.

You describe the outcome; Cody builds it, connects it, and deploys it. The free plan covers light use, with Pro at $39 per month and Business at $100 per month as usage grows; details are on the pricing page.

Making a video skimmable

The single biggest improvement available, and it is all about what surrounds the link.

State the length first. Three minutes and eighteen minutes are different propositions, and the viewer decides on that before anything else.

Summarise in two sentences from the transcript, so somebody can tell whether it is for them without watching.

Say who it is for and what they should do after. "Engineering — no action, context for Thursday's decision" is a complete instruction.

Include the key points as text where the video is a walkthrough, so the searchable version exists. Six months later, nobody finds a video by searching for what was said in it unless the text is there too.

Timestamp the sections for anything long, so a viewer can go to the part that concerns them rather than watching all of it or none.

Keep the message short. A summary longer than the video's usefulness defeats the purpose.

Routing by audience

Ask the recorder who it is for, rather than inferring. A prompt at share time costs seconds and determines whether the routing is right.

Send to the team channel, not a general one. A video in a company-wide channel is a video for nobody.

Direct message where one person needs it, particularly for a reply to a specific question.

Use a tag or folder convention in Loom so routing is derivable rather than guessed, and agree it once with the people recording.

Default to fewer recipients. A video sent to fifteen people who do not need it teaches all fifteen to ignore the next one.

Closing the loop on whether it was watched

The part that makes async video work as a meeting replacement rather than a hope.

A video replacing a meeting has an expected audience, and whether they watched is a fact worth having.

Nudge the people who have not, privately, once, before the point where it matters.

Report view rates to the recorder, so they learn what works. A recorder who never finds out whether anybody watched will keep making the same eighteen-minute videos.

Watch for the pattern. Consistently low view rates on one series mean the format is wrong, not that the team is disengaged, and that is a useful thing to discover early.

Do not make it a compliance exercise. A public list of who has not watched is a different culture from a quiet reminder, and not a better one.

Video as a record, not just a message

Worth building, because it is where the value compounds.

Attach the video to the thing it is about — the ticket, the document, the pull request — rather than leaving it only in a channel.

Save the transcript alongside it, which is what makes it findable, since nobody searches video.

Link from the knowledge base. A walkthrough referenced from documentation is watched for years; the same video in a channel is watched for a day.

Record what it superseded. A video replacing a recurring meeting should say so, so the meeting stays cancelled.

Prune. Videos describing processes that changed are as misleading as stale documentation and are harder to spot, so a periodic review by age is worth having.

Replying, and keeping the conversation together

A video prompts responses, and where those land decides whether the exchange is worth anything later.

Keep replies in one thread. Comments on the recording and messages in the channel split the discussion in half, and neither half makes sense alone.

Pick one as canonical and say which in the message. Either works; having both without a convention does not.

Bring Loom comments into the thread if people use them, so the channel version is complete.

A video that generates a long discussion was the wrong format. That is useful feedback for the recorder — the topic needed a conversation, and the recording delayed it by a day.

Summarise the outcome back into the thread. A video plus twenty replies has a conclusion somewhere in it, and writing it down is what makes the exchange readable later.

Record the decision somewhere durable if one was reached. A channel thread is not a record, and the whole point of replacing a meeting is that the reasoning survives.

Making it survive

Make it idempotent, keyed on the recording, so a retried webhook does not post twice.

Wait for the transcript, which is not available the instant a recording finishes, and post once it is rather than posting twice.

Handle the private recording. Not everything shared internally should be routed automatically, and the default should be conservative.

Map Loom users to Slack users, reporting failures rather than dropping messages.

Report the outcome. Recordings posted, audiences routed to, and anything skipped.

Limits worth knowing about

Transcripts take time to generate after a recording ends, so anything depending on one has to wait.

Transcription accuracy varies with audio quality and accent, so a generated summary can be wrong in ways worth a glance before it reaches a wide audience.

API availability depends on your plan, and capabilities differ between tiers.

Sharing permissions matter. A link posted to a channel is only useful if the recipients can actually open it, and workspace sharing settings decide that.

Slack unfurls video links inconsistently, so the message should carry the useful information rather than relying on a preview.

What to set up first

Length, a two-sentence summary from the transcript, and the audience, posted with every shared recording into the right team channel. It is a small amount of building and it changes the view rate more than anything else, because it lets somebody decide in five seconds whether the video is for them.

Two habits make the difference. Put the length first, since that is the question every viewer has and the one a bare link never answers. And ask the recorder who it is for at share time rather than inferring, because the routing is the half that determines whether the right people ever see it.

Frequently asked questions

Why does nobody watch our shared videos?

Usually because the message does not say how long it is, what it covers, or who it is for. A bare link in a general channel is addressed to nobody, and watching it is always something to do later.

What should the Slack message include?

Length first, a two-sentence summary from the transcript, the intended audience, and what they should do afterwards. Timestamps for anything long. That is enough for a five-second decision, which is all you get.

Should videos go to a general channel?

No. A video in a company-wide channel is a video for nobody. Route to the team that needs it, or direct message one person, and default to fewer recipients rather than more.

Can I tell whether people watched?

Where view data is available, yes, and it is worth using — a quiet reminder to the people who have not, before it matters, and view rates reported back to the recorder so they learn what format works.

Is async video a good replacement for standup?

Rarely, and it is the most common attempt. A recorded status update to a group is watched for about three weeks. Video works for showing something on a screen and for explaining reasoning, not for routine status.

Why wait for the transcript?

Because it is what makes the video skimmable and searchable, and it is not available the instant recording stops. Post once, when it is ready, rather than posting a bare link and following up.

How do I stop old videos misleading people?

Review by age, particularly anything describing a process. Stale video is harder to spot than stale documentation because nobody skims it, and a walkthrough of a flow that changed is worse than no walkthrough.

Should people reply in Loom or in Slack?

Pick one and say which in the message. Comments on the recording and replies in the channel split the discussion in half, and neither half makes sense on its own six months later.

What does a long reply thread tell you?

That the topic needed a conversation rather than a broadcast. It is useful feedback for the recorder: the video delayed the discussion by a day instead of replacing it, which is the opposite of what async video is for.

Related reading

• Automating Zoom meeting summaries
• Loom and CodeWords
• CodeWords integrations and templates