Slack
Slack is most useful when the team already treats channels as the operating inbox for work. Hyper can push the right recap into the right place so follow-up happens where the team is already reading.
Use it when meetings should end with visible next steps instead of another tool tab everyone forgets to open.
Wireframes
Section titled “Wireframes”┌──────────────────────────────────────────────────────────────────────┐
│ Hyper app.hyper.video/integrations/slack │
├──────────────────────────────────────────────────────────────────────┤
│ │
│ Slack routing │
│ │
│ Default channel: #team-sync │
│ Private channel access: allowed only after app invite │
│ │
│ Rules │
│ ┌──────────────────────────────────────────────────────────────┐ │
│ │ Weekly sync -> #team-sync summary + tasks │ │
│ │ Customer call -> #account-alpha summary only │ │
│ │ Incident review -> #ops-private recap after approval │ │
│ └──────────────────────────────────────────────────────────────┘ │
│ │
│ [ Save routing ] [ Test post ] [ View scopes ] │
│ │
└──────────────────────────────────────────────────────────────────────┘
Route different meeting types to different destinations and control which artifacts leave Hyper.
When to use this
- Standups, customer calls, project syncs, and leadership reviews that need visible recap distribution.
- Teams that want channel-based routing and per-meeting overrides.
Before you start
- Decide which channels should receive which types of meeting output.
- Review the app scopes and private-channel rules with your Slack admins.
- Confirm what should happen for sensitive meetings before enabling default posting.
Settings and options
Routing and controls
- Use workspace defaults for common meeting types and per-meeting overrides for exceptions.
- Separate internal and external meeting channels when confidentiality differs by audience.
- Review whether recordings should be posted automatically or only summaries and action items.
What this feature helps with
Auto-post summaries
Summaries, action items, and recording links post to Slack the moment your meeting ends. No manual copy-paste — your team gets updates without leaving their workflow.
Channel routing
Choose which channels get which content. Route standup summaries to #standup, client recaps to #sales, or send everything to a single channel — you decide.
Per-meeting controls
Override defaults for any meeting. Skip posting, change the channel, or add a custom message — full control without changing your workspace settings.
How to work with it
Connect your Slack workspace
- Go to Settings → Integrations and click Connect for Slack
- Authorize Hyper with the requested scopes
- Choose a default channel for posting
Choose default channels and content types
- Select which content to post: summaries, action items, recordings
- Set channel routing rules (e.g., standups → #standup)
- Customize message format and optional prefixes
Summaries auto-post after every meeting
- Once connected, summaries post automatically when meetings end
- Use per-meeting overrides to skip, change channel, or add context
- Team members get updates without leaving Slack
Where it fits well
Sales teams
- Post client call recaps to #sales or deal-specific channels
- Action items with owners visible to the whole team
- Recording links for managers to review key moments
- No manual forwarding — updates flow automatically
Engineering standups
- Daily standup summaries in #standup or team channels
- Action items and blockers surfaced for async follow-up
- Recording links for anyone who missed the call
- Keeps remote and async teams in sync
Cross-functional syncs
- Route product/eng sync summaries to shared channels
- Decisions and action items visible to stakeholders
- Recordings for leadership and PMs who couldn't attend
- One source of truth — no duplicate note-taking
What to expect
- Automatic posting
- Configurable content (summaries, action items, recordings)
- Per-meeting overrides
- Channel routing rules
- Rich message formatting
- No manual copying
Questions that come up often
What Slack scopes does Hyper need?
Hyper requests chat:write to post messages, channels:read and groups:read to list channels, and users:read for attribution. We only use these for posting meeting content — we never read your Slack messages or DMs.
How do privacy controls work?
You control what gets posted. Per-meeting overrides let you skip posting for sensitive calls. Channel routing ensures summaries only go to appropriate channels. Workspace admins can restrict which channels Hyper can post to.
Can I override posting for a specific meeting?
Yes. Before or during a meeting, you can choose to skip posting, change the target channel, or add a custom message. Per-meeting overrides don't affect your default settings for future meetings.
Can I post to custom or private channels?
Yes. Hyper can post to any channel you have access to, including private channels. You'll need to invite the Hyper app to private channels before they appear in your routing options.
What does the Slack message format look like?
Messages include the meeting title, summary (or action items, or recording link — based on your settings), and optional metadata like attendees. Format is configurable: you can add prefixes, change structure, or keep the default rich layout.
Related tasks
Limitations and rollout notes
- Slack channel availability depends on app installation scope and whether the app has been invited into private channels.
- Posting into Slack does not override Hyper artifact permissions; the target audience still matters.
Troubleshooting
The summary did not post where I expected
- Check whether a per-meeting override changed the target channel.
- Verify the app was invited into the destination private channel.
- Review the workspace routing rule for that meeting type and artifact set.