note1 for SlackAfter every recorded Google Meet, Microsoft Teams, or Zoom call, note1 posts an AI meeting recap to the Slack channel you choose. Search past meeting transcripts privately with /note1, or ask @note1 in a thread for evidence-linked answers.
Searching your meetings for "what did we decide about onboarding?"...
The team decided to ship the shorter onboarding flow first and measure activation after one week. The longer guided setup remains available for enterprise workspaces. [1] [2] No explicit action items were found.
We agreed to launch the shorter setup first...
Activation will be reviewed after seven days...
Searched as alex@company.com
After a meeting ends and note1 finishes processing it, note1 can post a recap to Slack. The message carries the meeting title, date and time, summary overview, and an Open meeting button. It gives the channel enough context to continue the work without dumping a full transcript into the conversation.
Posting depends on the channel settings you control. note1 first checks the meeting, then its recurring series, then the team default. A meeting or series can explicitly turn posting off. If no channel resolves, note1 sends nothing.
Aug 8, 2026, 10:00 AM
The team approved the shorter onboarding flow for the next release. Activation will be reviewed after one week, while the existing guided setup remains available for enterprise workspaces. Design will deliver the final empty states on Tuesday, and engineering will begin the staged rollout after QA signs off.
Open meetingA team admin can choose the public Slack channel that should receive processed meeting recaps by default. Leave it unset if automatic posting should be opt-in.
A meeting can inherit the team default, post to another public channel, or choose Don't post. The meeting setting wins over the global choice.
Apply the selected channel or disabled state to future scheduled meetings in a recurring series. Past and already-recorded meetings stay unchanged.
Slack receives the summary overview and a link. The recording, complete transcript, structured summary, and action items remain on the meeting page with normal access controls.
A recap gives people who missed the meeting a readable overview without forcing them through a recording or transcript. The title and meeting time make the update easy to place, while the summary captures the main discussion in the same Slack channel where follow-up work already happens. Anyone who needs more can use Open meeting to review the complete record in note1. This gives the channel a dependable starting point while keeping detailed review one click away.
note1 remains the system of record for the recording, full transcript, structured summary sections, speakers, and action items. That separation keeps Slack readable and preserves the meeting's access rules. A short recap can start a discussion in the channel; the linked meeting page carries the evidence needed to settle details, verify wording, or hear the original exchange.
Not every meeting belongs in Slack. Leave the team default empty, disable one sensitive meeting, or disable a recurring series when its notes should stay in note1. Automatic posting only happens when the connected workspace and channel settings resolve to a public Slack channel.
Type /note1 followed by a question and note1 searches the connected team's meeting knowledge. When Slack can provide the caller's email and it matches a note1 team member, the search uses that person's normal meeting permissions. If the identity cannot be matched, note1 falls back to team-visible meetings instead of taking a privacy shortcut.
Use the question you would ask a colleague: what did we decide, who owns the follow-up, or what was my latest meeting about? note1 searches titles, summaries, transcripts, action items, questions, and topics.
The response is ephemeral. Only the person who ran /note1 can see the answer and its source list, so a broad search does not interrupt the channel or disclose its result by default.
When one source belongs in the channel, share that evidence card. note1 checks access again before posting and refuses to publish a private meeting through this control.
A useful answer needs a trail back to the conversation. note1 turns evidence citations into numbered links that open the relevant meeting at the matching timestamp. The visible source rows show the meeting title, date, and excerpt, so you can judge whether the result supports the answer before you repeat it.
The Share to channel button publishes one eligible source card: its title, date, excerpt, and timestamped link. It does not broadcast the complete AI answer or the full transcript. Before anything appears in the channel, note1 repeats the team-visible access check. Private meetings do not get a share button and cannot be posted to a channel.
Mention @note1 in a Slack channel and ask the question where the team is already talking. note1 replies in the same thread with an evidence-linked answer and a focused source list. The thread stays connected to the project discussion instead of sending everyone to a separate search screen.
Shared space means stricter access. Mentions search team-visible meeting content only. They never inherit the caller's private meeting permissions, even when that user could find more through /note1. Mention replies also omit share controls because the answer is already in the channel thread.
@note1 what did we decide about onboarding?
The team decided to ship the shorter onboarding flow first and measure activation after one week. [1] [2] No explicit action items were found.
We agreed to launch the shorter setup first...
Activation will be reviewed after seven days...
Team-visible meetings only
The team integration defines the default destination. Each meeting can inherit it, select another public channel, or turn posting off; recurring meetings can carry that choice forward.
Post meeting recaps to Slack channels
Slack connected
Workspace: Acme
Meeting recaps post here unless a meeting or series picks its own channel or turns posting off.
Choose where this recap should appear.
Post the recap to a channel when this meeting is ready.
Apply to future meetings
Use #launch-room for future meetings in this recurring series.
A note1 team admin opens Team, then Integrations. Team members can see the connection status, but only an admin can connect or disconnect a Slack workspace.
Connect Slack opens Slack OAuth. Slack shows the requested permissions before the admin approves the workspace connection and returns to note1.
Select a non-archived public channel for automatic recaps, or leave the team default empty when posting should be decided meeting by meeting.
In meeting settings, inherit the team default, choose another public channel, or disable posting. Apply the setting to future meetings when the event belongs to a recurring series.
A team admin can disconnect later. note1 attempts to revoke the Slack token and removes the stored workspace integration from the team.
Slack is a shared surface, while meeting access can be personal. note1 treats those as different contexts. It does not assume that a person who can read a private meeting should be able to quote it into a channel.
/note1 answers are ephemeral. Personal meeting permissions are used only after Slack identity is matched to a member of the connected note1 team.
@note1 mentions, automatic channel posts, and shared evidence never use a person's private meeting access as a fallback.
note1 verifies Slack signatures on commands, events, and button interactions and rejects stale signed requests. Stored Slack bot tokens are encrypted at rest.
The integration sends recap text, answers, and selected snippets to Slack when those features are used. Full meeting records remain in note1 behind their normal permissions.
A Slack recap is not another archive. It is a handoff from the meeting to the channel where decisions, customer context, and follow-up work continue.
A decision made in a planning call should not disappear into a recording. Send the processed recap to the project channel, then use /note1 when someone needs the reason behind a scope change. The answer links back to the exact meeting evidence, so engineers can check what was agreed before changing a ticket or reopening an old debate.
Keep account channels current after demos, discovery calls, and renewals. A recap gives the wider team the meeting overview without publishing the full transcript. When a customer question comes up later, search for the objection, requested feature, or next step and share the relevant source instead of forwarding a wall of notes.
Route recurring team updates to one channel and keep exceptions under control with per-series settings. Leaders can ask @note1 for team-visible context inside a thread, while individuals use /note1 privately when their question depends on meetings available through their own note1 permissions.
Give people in another time zone enough context to continue the work without scheduling another status call. Recaps arrive after processing, evidence links preserve the source, and thread replies keep follow-up questions next to the conversation that prompted them. The meeting stays useful after the people who attended have logged off.
Meetings recorded from Google Meet, Microsoft Teams, and Zoom can all feed the same post-processing and Slack workflow. Slack controls where the completed recap goes and how people search it later; recording attendance remains managed in note1 and your calendar.
Record Google Meet calls with note1, process the meeting, and route its recap to the Slack channel selected by your team.
Keep Teams meeting summaries in the same note1 workspace and use the same Slack recap and meeting-search workflow.
Turn recorded Zoom conversations into summaries and searchable evidence that can be referenced from Slack after processing.
After note1 finishes processing a recorded meeting, it can post the meeting title, date and time, summary overview, and an Open meeting button to the selected public Slack channel. The full transcript and action items remain on the meeting page in note1.
The recap appears after the meeting has ended and note1 has finished processing its recording and summary. It is a post-meeting update, not a real-time transcript or live alert.
Yes. A note1 team admin can choose a default public Slack channel for the team. Individual meetings and recurring series can inherit that default, use another public channel, or turn Slack posting off.
Yes. In the meeting settings, choose the team default, select another public channel, or choose Don't post. The override applies to that meeting unless you also choose to update future meetings in its recurring series.
Yes. You can apply a Slack channel choice or the disabled setting to future scheduled meetings in a recurring series. Past and already-recorded meetings are not rewritten.
Yes. Slash-command results are ephemeral and visible only to the person who runs the command. If their Slack email matches a note1 team member, note1 uses that member's normal meeting permissions; otherwise it falls back to team-visible meetings.
No. Mentions happen in shared Slack threads, so @note1 deliberately searches team-visible meeting content only. It never falls back to a user's personal or private meeting permissions.
You can share an eligible evidence source with the Share to channel button. note1 rechecks that the meeting is team-visible before posting its title, date, excerpt, and timestamped link. It does not share private meetings or the complete AI answer.
No. Automatic Slack recaps contain summary overview text and a link back to the meeting. The complete transcript, recording, summary sections, and action items stay in note1 behind the meeting's normal access controls.
Meetings recorded by note1 from Google Meet, Microsoft Teams, and Zoom can use the same post-processing and Slack recap workflow. The Slack integration does not control whether the recording assistant joins a meeting.
A note1 team admin opens Team, then Integrations, selects Connect Slack, and approves the requested permissions in Slack. After the workspace is linked, the admin can choose a default public Slack channel and meeting editors can override that destination or turn posting off.
Explore the meeting workflows that power note1 for Slack.
Connect note1 to Slack from Team integrations, choose a default recap channel, and keep every meeting's destination under your control.