Skip to content

Integrations

Preview Roles: Workspace admin, Host Platforms: Web, Mac, Windows, Linux Reviewed: 2026-03-14

Use this section when Hyper needs to fit into the tools your team already relies on every day. These pages cover calendars, chat destinations, knowledge tools, browser entry points, and the current boundary between built-in integrations and planned API support.

After you finish this section, you should know which connections are workspace-level decisions, which ones are personal, and where shared meeting data leaves Hyper.

Calendar as the scheduling backbone
┌──────────────────────────────────────────────────────────────────────┐
│  Hyper   app.hyper.video/integrations/calendar                       │
├──────────────────────────────────────────────────────────────────────┤
│                                                                      │
│  Calendar connection                                                 │
│                                                                      │
│  Providers                                                           │
│  - Google Workspace     Connected     writable                       │
│  - Microsoft 365        Not connected                                │
│                                                                      │
│  Permissions                                                         │
│  ┌──────────────────────────────────────────────────────────────┐    │
│  │ Create events      Yes                                       │    │
│  │ Read availability  Yes                                       │    │
│  │ Update recurrence  Yes                                       │    │
│  │ Manage guests      Limited to connected calendar             │    │
│  └──────────────────────────────────────────────────────────────┘    │
│                                                                      │
│  [ Connect calendar ]  [ Re-authenticate ]                           │
│                                                                      │
└──────────────────────────────────────────────────────────────────────┘

Calendar setup is usually the first integration because it determines how meetings are created, synced, and discovered.

  • You want meetings to fit existing team workflows instead of creating another destination to monitor.
  • The meeting should automatically create follow-up in chat, docs, or internal tools.
  • Decide which workspace roles can connect or manage integrations.
  • Choose default destinations for summaries, action items, and scheduling flows.
  • Review artifact permissions before routing meeting data into external systems.

What this section covers

Calendar

Sync with Google Calendar, Outlook, or iCloud. Meetings appear in Hyper automatically. Schedule with natural language — "lunch with Sarah next Tuesday" — and attach agendas to invites. One source of truth.

Slack

Get meeting summaries and action items in Slack. Notify channels when meetings end, share key takeaways, and keep your team in the loop without leaving the conversation. Configurable per channel or DM.

Automations

Post summaries to Slack, create Notion pages from meeting notes, attach agendas to calendar invites — all via simple recipes. Fit Hyper into your workflows without custom code or complex setup.

Key workflows and controls

Calendar integration

  • Sync with Google Calendar, Outlook, or iCloud
  • Meetings appear in Hyper automatically — no manual import
  • Two-way sync keeps your calendar the source of truth
  • Works with personal and shared calendars

Scheduling (natural language input)

  • Schedule meetings with natural language — "lunch with Sarah next Tuesday"
  • Attach agendas and prep materials to invites
  • Suggest times based on availability
  • Reduces back-and-forth when scheduling

Slack

  • Post meeting summaries to Slack channels or DMs
  • Share action items and key takeaways automatically
  • Notify when meetings end with a summary link
  • Configurable per channel — choose what gets posted

Chrome extension

  • Join Hyper meetings from your browser
  • Quick access to meeting prep and notes
  • Capture context from tabs when relevant
  • Works with Google Meet, Zoom, and other video platforms

Notion / Google Docs

  • Export meeting notes and summaries to Notion or Google Docs
  • Create pages from meeting content with one click
  • Keep documentation in sync with discussions
  • Use recipes to automate exports after meetings

Recipes

  • Post summary to Slack — automatically share meeting summaries to a channel when meetings end
  • Create Notion page — turn meeting notes into a new Notion page with key takeaways and action items
  • Attach agenda to invite — add the meeting agenda to the calendar invite so attendees see it before joining

How the workflow fits together

Connect

Link your calendar, Slack workspace, or other tools with a few clicks. OAuth flows keep credentials secure. You choose which calendars and channels to connect — granular control from the start.

Configure

Set your preferences: which meetings sync, which Slack channels get summaries, which recipes to run. Configure once and it works for every meeting. Workspace admins can set org-wide defaults.

Automate

Meetings sync, summaries post, and recipes run automatically. No manual steps after setup. Hyper fits into your existing workflows — you stay in Slack, Notion, and your calendar without context switching.

Common starting points

Sales teams

  • Calendar sync keeps demos and discovery calls in Hyper
  • Post call summaries to Slack for the sales channel
  • Create Notion pages from client meeting notes for deal tracking
  • Attach agendas to calendar invites so prospects know what to expect

Engineering teams

  • Standup and sprint meeting summaries in Slack automatically
  • Sync with Google Calendar for sprint planning and retros
  • Chrome extension for quick access during remote pairing
  • Search and Ask Your Meetings for technical decisions across standups

Consulting firms

  • Client meeting summaries to project channels in Slack
  • Export meeting notes to Notion for client deliverables
  • Calendar sync across Google, Outlook, and iCloud for mixed environments
  • Attach project agendas to invites for consistent client touchpoints

Questions that come up often

What integrations are supported?

We support Google Calendar, Outlook, and iCloud for calendar sync; Slack for notifications and summaries; a Chrome extension for browser-based access; and Notion/Google Docs for exports. More integrations are in development. Check our integrations page for the latest list.

How long does setup take?

Calendar and Slack connections take under 2 minutes — OAuth flows, choose your calendars/channels, done. Recipes and automations add another minute or two. No technical setup or IT involvement required for most teams.

What permissions or scopes do integrations need?

Calendar integrations need read/write access to create and sync events. Slack needs permission to post to channels you specify. We request the minimum scopes required — you can revoke access anytime from your account or the connected app's settings.

Is my data shared with third parties?

Integrations send data only to the services you connect — e.g., Slack receives what you configure (summaries, action items). We don't sell or share your data with advertisers or other third parties. See our privacy policy for full details.

Can we build custom integrations?

We're exploring APIs and webhooks for custom integrations. If you have specific needs, contact us — we work with enterprise customers on tailored solutions. In the meantime, recipes cover many common automation scenarios.

Related tasks

  • Each external system has its own scopes, sync timing, and policy constraints.
  • Forwarding artifacts out of Hyper does not bypass your internal privacy and retention obligations.
  • Check admin policy and allowed scopes for that workspace first.
  • Confirm the integration was connected at the intended level: personal, team, or workspace.
  • Review per-meeting overrides when a single meeting behaves differently from the default.