Notion
Notion integration is best when meeting outputs should live inside the same workspace as project docs, plans, and team knowledge. It turns a recap into a structured object in the team's knowledge system instead of a transient chat message.
Use it for project-driven teams that want durable meeting records and searchable context outside the live meeting surface.
Wireframes
Section titled “Wireframes”┌──────────────────────────────────────────────────────────────────────┐
│ Hyper app.hyper.video/integrations/notion │
├──────────────────────────────────────────────────────────────────────┤
│ │
│ Notion export │
│ │
│ Workspace: Product Operations │
│ Database: Meeting Recaps │
│ Template: Launch review summary │
│ │
│ Export fields │
│ ┌──────────────────────────────────────────────────────────────┐ │
│ │ Summary -> page body │ │
│ │ Decisions -> decisions property │ │
│ │ Action items -> related tasks database │ │
│ │ Recording link -> attachments │ │
│ └──────────────────────────────────────────────────────────────┘ │
│ │
│ [ Export recap ] [ Edit mapping ] │
│ │
└──────────────────────────────────────────────────────────────────────┘
Choose the database, page structure, and fields before enabling summary sync by default.
When to use this
- Project and product teams want summaries to become part of their knowledge base automatically.
- You need structured meeting recaps in a database or workspace hierarchy.
Before you start
- Decide whether each meeting should create a standalone page, a database row, or both.
- Choose the Notion destination and naming rules before enabling auto-sync broadly.
Settings and options
Destination structure
- Use a database when you want filtering, ownership, and repeatable meeting metadata.
- Use a document page destination when the team reads narrative recaps more than tabular indexes.
- Keep permissions aligned so the Notion audience matches the Hyper artifact audience.
What this feature helps with
Auto-sync summaries
Meeting summaries are automatically created as Notion pages after every call. No copy-paste, no manual export.
Database integration
Summaries are added to a Notion database with properties for date, participants, and meeting type. Filter and sort like any other Notion data.
Customizable templates
Choose how meeting notes appear in Notion. Customize the template to match your team's preferred format and properties.
How to work with it
Connect Notion
- Authorize Hyper to write to your Notion workspace
- Choose which database to sync meetings to
Configure sync settings
- Choose what to include: summaries, action items, transcripts
- Set up routing rules by meeting type or calendar
Meetings sync automatically
- After every call, notes appear in Notion within minutes
- Database properties are populated automatically
Where it fits well
Project management
- Meeting notes linked to project pages
- Action items visible in project databases
- Full context for async team members
- Searchable within Notion
Team wikis
- Decision log built automatically from meetings
- Meeting history organized by team
- New team members can browse past discussions
- Institutional knowledge captured passively
Client documentation
- Client meeting notes in a dedicated database
- Action items and commitments tracked
- Shareable with external stakeholders
- Professional documentation without manual effort
What to expect
- Automatic Notion sync
- Database properties
- Customizable templates
- Routing by meeting type
- Action item sync
- Transcript inclusion optional
Questions that come up often
Which Notion plans are supported?
The integration works with all Notion plans including free, Plus, Business, and Enterprise.
Can I sync to multiple databases?
Yes. Set up routing rules to send different meeting types to different Notion databases. For example, client calls to one database, internal meetings to another.
Is the sync real-time?
Summaries are synced within a few minutes of the meeting ending. Transcripts are synced once they're finalized.
Related tasks
Limitations and rollout notes
- Sync behavior depends on the connected workspace permissions and page/database structure.
- Large or heavily customized Notion schemas may require more careful field mapping.
Troubleshooting
The summary synced but the structure is wrong
- Check the selected database or parent page for the workspace rule that handled the sync.
- Review custom field mapping before sending another batch of meeting recaps.
- Use manual review for a few meetings before turning broad automation back on.