How to send meeting notes to Slack

To send Wispr Notetaker meeting notes to Slack, copy the summary from the Summary tab and paste it into a channel, copy the whole meeting as Markdown, or share a note by link. Nothing posts on its own, and the route you pick decides whether the transcript goes with it.

What actually gets sent to Slack, and what stays with you

Wispr Notetaker does not post to Slack on its own. You choose what leaves the meeting, every time. That means there are four routes into a channel, and they carry different amounts of the meeting.

The summary is the usual thing people paste. It's topic-based, with next steps for everyone in the meeting, and it's built from the refined final transcript, so it inherits the quality of the capture. Speaker names show as you assigned them.

Everything else stays where it is unless you move it. Your own notes in My Notes, the full transcript, the Brief you read before the call: none of that lands in Slack because you pasted a summary. You set a note's visibility. There are three levels: Private, Shared with team, or Anyone with the link, and you can set which one new notes start at.

Note typeWhat lands in SlackRoute typeBest use
Summary, pastedTopic-based summary plus next steps, as text in the channelManual copy and pasteThe standing recap in a project or team channel
Copy to Markdown, pastedMeeting info and attendees, summary, Brief, your notes, chat messages, and the full transcriptManual export, copy and pasteA handoff where someone needs the exact wording
Share link, pastedA link; recipients who open it see the summary onlyManual link pasteWide channels where the transcript should stay out
Email invite, link pasted aftern/aEmail invite, not native to SlackA small group that needs to check who said what; the summary and full transcript reach the people you invited by email, not the channel
Ask Anything answer, pastedWhatever you asked for, with sources you can clickManual copy and pasteAnswering a question in-thread a month later

How to paste a summary into a channel

This is the fastest route and the one most people settle on.

  1. Open the meeting in the Wispr Notetaker hub or the standalone notepad. Summaries generate after you stop recording, and a notification tells you when yours is ready.
  2. Name any unidentified speakers first. Assigning a name updates the summary, the transcript, search results, and the hub previews. Named speaker labels are only available for Google Meet meetings, and not every meeting or segment gets them. You can only assign names on meetings you own.
  3. Open the Summary tab and use its copy action. That copies the summary alone, not the whole meeting.
  4. Paste it into the Slack channel or thread and add a line saying why you're posting it.

If the meeting was very short, you may see a Generate summary button instead of a finished summary, and a recording that was too short ends with no summary at all. Resuming a meeting that already has a summary lets you regenerate it from the full recording. That replaces any edits you made. Copy your hand-written lines before you click Update Summary.

When to copy the whole meeting as Markdown

Copy to Markdown is the first item in the ⋯ menu, in both the standalone notepad and the hub's meeting detail view. It copies the whole meeting to your clipboard as one Markdown document: meeting info and attendees, the summary with its toggle sections flattened into headings, the Brief, your own notes, chat messages, and the full transcript including in-progress text.

Markdown pastes into Slack as plain text, so a long transcript will flood a channel. Two ways around that. Paste it into a thread rather than the channel, or trim to the part that matters before you send. For a genuinely long meeting, upload it as a file or snippet instead of a message.

Two details worth knowing before you copy. Copy to Markdown stays grayed out until the Brief finishes loading, so you can't copy a version without it. Speaker names export as assigned, your own entry shows your profile name rather than "You," and anyone unnamed keeps a default label like "Speaker 1 (Alex)."

Share links versus email invites

A share link carries the recap. An email invite carries the transcript too.

A share link shows the summary only. Copy Link confirms with "Summary link copied" and a second line reminding you that transcript access comes from an email invite. That makes the link the right thing to drop in a wide channel: people get the recap, and the transcript stays out of a room you can't fully see.

An email invite is different. Invitees can view the summary and the full transcript. Type an address, press Enter or comma, and each address becomes a chip you can remove. Removing a chip revokes that person's access. Re-adding someone who is already a recipient doesn't resend the email, so remove them first, then invite again.

Sharing controls appear only on notes you own, and recipients always get viewer access. Set a default visibility for new notes in Settings, Data and Privacy, Notes sharing. Existing notes keep the visibility they already had.

Slack gotchas to check before you send

Restricting a note after the link is out. Pulling a note back from "Anyone with the link" shows a warning, because people who already have the old link may lose access. In Slack that link lives in the channel history forever. Decide the visibility level before you paste, not after.

Google Meet transcripts can carry real names. For Google Meet meetings, the transcript and summary may label speech with participants' real names, so recipients can see who said what. Read the note before you share it, especially for anything with candidates, customers, or a performance conversation in it.

New links resolve to a 404 at first. A share link is prepared when a meeting finalizes and syncs to your devices, but it stays a 404 for everyone but you until you copy it or invite someone. It goes live at your chosen visibility after that.

Shared notes don't all refresh the same way. Automatic live updates apply to people you invited by email. Notes shared by domain link or anyone-with-link do not update automatically the same way, so a channel link may show an older summary than the one you're looking at.

Nothing leaves the meeting unless you send it

Nothing joins the call, so the meeting looks normal to everyone in it. That's about keeping the conversation natural, not recording people without their knowledge. Always tell everyone on the call that you're recording.

The same principle runs through sharing. Nothing posts to a channel on its own. You copy something, set a visibility level, or invite a person by name.

Slack also arrives from the other direction. You can connect Slack to Wispr Notetaker, which is how a Brief pulls context from your own threads before a call, with each line linking back to the source it came from. And you can ask about your meeting history and the threads, emails, and events around it. Ask "what did we promise them in March" and the answer comes with a source you can click. Record your next meeting with Wispr Notetaker and pick the route that fits the room.

Where this fits and where it doesn't

Good fit: you run meetings on a Mac and a handful of people in Slack need the recap, the decisions, and occasionally the exact words. You want to read the note before anyone else does. You want to read the summary yourself before it goes to the channel.

Weaker fit: you want a channel that fills itself after every call. Wispr Notetaker doesn't do that, and this page won't pretend otherwise. You're on Windows, or you want this from a phone: Wispr Notetaker is on Mac today, with Windows coming soon and phones on the roadmap. It's also rolling out gradually, so sharing may not have reached your account yet. You're on Flow Basic and record constantly, since the free plan limits how many meeting notes you get each week. A paid plan raises that limit.

One practical test. Take your next real meeting, paste the summary into the channel where the work actually happens, and see whether anyone asks a follow-up question you'd have needed the transcript to answer. If they do, email-invite those two people. If they don't, the summary was the whole job.

Frequently asked questions

Does Wispr Notetaker post meeting notes to Slack automatically?

No. Every route into Slack is something you do: paste the summary, copy the meeting as Markdown, paste a share link, or invite people by email. The Slack connection runs the other way, into your pre-meeting Brief, and each Brief line carries a chip with the source's icon that opens the original thread.

Can I share just the summary and not the transcript?

Yes. A share link shows the summary only, so the transcript stays out of the channel. Transcript access comes from an email invite, and every recipient gets viewer access, so nobody you invite can edit the note.

What does Copy to Markdown actually include?

Everything the meeting holds, in one document: the header info, the summary flattened into headings, the Brief, your notes, chat, and the transcript. The Summary tab's copy action is the narrower option when you only want the recap, and it is the one to use for a busy channel.

How do I get real names instead of Speaker 1 in a Slack recap?

Name the speaker in the note before you copy anything. Unassigned speakers appear as underlined mentions with a "Who is this?" popover. Assigning a name live-updates the summary, transcript, search results, and hub previews. Speaker assignment works only on meetings you own.

Can my whole team see a note without me sharing it one by one?

Yes. Set the note to Shared with team and anyone in your organization can open it without an individual invite. They get viewer access, and the transcript still needs an email invite.

Does Wispr Notetaker keep recordings of my meetings?

Your meetings are yours. Meeting audio is encrypted and kept only temporarily to create your transcript, let you resume a meeting, verify quality, and troubleshoot. After that limited period, it's automatically removed. Wispr Notetaker doesn't create voiceprints or biometric profiles of you or anyone on your call.

Share this