Product and engineering
Send the planning recap to the project channel. If someone questions a scope change, mention @note1 in the thread to find the meeting moment where the team discussed it.
After note1 processes a Google Meet, Microsoft Teams or Zoom call, it can post the summary to a public Slack channel you choose. Use /n1 to ask privately about a past meeting, or mention @note1 in a thread for a shared answer with sources.
what am I expected to do after yesterday's standup?
Two things are yours: send Agnes the rollout checklist before Thursday [1], and confirm who approves the empty-state copy [2]. The pilot start is Maya's to decide.
“I'll get Agnes the checklist before the customer call”
“someone has to sign off the empty-state copy, I can chase that”
Answered by Ask note1 as patryk@acme.com; only you can see this.
After processing, note1 posts the meeting title, date, summary overview and an Open meeting button to the selected public channel. The full transcript stays in note1.
The meeting setting takes priority, followed by its recurring series and then the team default. Turn posting off at either level or leave the default empty to avoid an unwanted post.
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 gets the summary overview and a link. The recording, transcript and action items stay on the meeting page.
The Slack post includes the meeting title, time and summary overview. People who missed the call can read the update in their channel, then use Open meeting if they need the full record.
The recording, transcript, detailed summary and action items stay on the meeting page in note1. The Slack post links back to that page; it does not publish the full record to the channel.
Anyone in the selected public Slack channel can read the recap. Leave the team default empty to make posting opt-in, or turn it off for a sensitive meeting or recurring series. Without a selected channel, note1 sends no recap.
Type /n1 and your question. The reply is visible only to you. When your Slack email matches a note1 team member, Ask note1 uses that member's meeting access; otherwise it uses team-visible meetings.
Ask what the team decided, which tasks are still open or when a topic last came up. The answer links to the meeting sources it used.
Only you see the /n1 reply. When your Slack identity matches a note1 team member, the answer follows your meeting access.
Use the follow-up buttons to keep asking without repeating which meeting you mean.
Ask note1 shows numbered sources with the meeting, date and excerpt. Open a citation to check the transcript moment or action item before sharing the answer.
Linked note1 users can also complete, reassign or create action items and start topic trackers from Slack. Ask note1 checks each item's current status before answering about open work.
Mention @note1 in a thread to get a cited answer there. It reads the thread for context, so “did we decide this?” refers to the conversation people are already having. Everyone in the thread can see the reply and its follow-ups.
Public replies use team-visible meetings. A private meeting can appear only when the person asking participated in it and explicitly asks about that meeting. Use /n1 for questions you want to keep private.
Danny said the shorter onboarding flow ships next week, right?
@note1 is this right?
Partly. Danny committed to the shorter flow in Thursday's standup [1], but the date was “after QA signs off”, not next week. The QA sign-off is still an open item [2].
“we ship the short flow once QA signs off, not before”
Daily Standup, Oct 2
Answered publicly by Ask note1 from team-visible meetings. Use /n1 for a private answer.
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.
A person may be allowed to see a meeting that the rest of the channel cannot. /n1 replies privately; @note1 keeps its public reply within the meeting-access rules described above.
That boundary is especially important when applying privacy controls to one-on-one meeting notes.
/n1 answers are ephemeral. Personal meeting permissions are used only after the Slack identity is matched to a member of the connected note1 team.
@note1 uses team-visible meetings unless a participant explicitly asks about their private meeting. Automatic recaps post only to a selected public channel.
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 and Ask note1 answers to Slack when those features are used. Full meeting records remain in note1 behind their normal permissions.
Post the short recap where the team works. Keep the transcript and recording in note1, and use a cited answer when someone needs the details later.
Send the planning recap to the project channel. If someone questions a scope change, mention @note1 in the thread to find the meeting moment where the team discussed it.
Post a recap after a demo or renewal without sharing the full transcript. Later, ask /n1 privately for the customer objection or next step and open the cited moment to check it.
Route recurring updates to a team channel, with per-series overrides for exceptions. Use @note1 for shared context and /n1 when the question depends on meetings only you can see.
People in another time zone can read the recap after processing and ask a follow-up in the same thread. Source links let them check the meeting before acting on a decision.
note1 can send processed recaps from Meet, Teams and Zoom to Slack. Choose the public channel in note1; recording and meeting access remain managed there.
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. /n1 answers are ephemeral and visible only to the person who ran the command. If their Slack email matches a note1 team member (plus-aliases included), Ask note1 answers with that member's own meeting permissions; otherwise it answers from team-visible meetings.
Mentions are answered in the open, for everyone in the thread, so @note1 reads team-visible meetings. A private meeting of the asker's appears only when they asked about it directly and took part in it. It never quotes a private meeting into a channel otherwise.
Yes. When mentioned in a thread it reads the whole thread, and at the top level the recent channel messages, so "is this right?" or "did we decide this?" are checked against the meetings. The thread is treated as quoted data, never as instructions. Follow-up buttons under an answer keep the conversation going, and everyone in the thread shares it.
Yes, as the linked note1 user: complete, reassign or create action items and manage topic trackers. Unlinked Slack users can ask but not change anything.
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 your Slack workspace, choose a default public channel and override it for meetings that belong somewhere else.