Notion

Sync meeting notes, action items, and AI-generated summaries into Notion databases — turning every customer interaction into structured, searchable knowledge.

When to Use This Connection

Use this connection when the user:

• Wants Demodesk meetings to automatically create pages in a Notion database
• Needs to map Demodesk meeting properties to Notion database columns
• Wants AI summaries formatted as rich Notion content with headings and callouts
• Needs action items synced to Notion to-do blocks for task tracking
• Wants to link meeting pages to existing Notion account or deal databases

What This Connection Does

Guide the user to Settings > Integrations > Notion in Demodesk at https://demodesk.com/manage/settings/integrations/notion. Click "Connect Notion" to start the OAuth 2.0 authorization flow. Notion will ask the user to select which workspace pages Demodesk can access — the user must grant access to the database(s) where meeting notes should be stored. The authorizing user needs editing permissions on the target database.

After authorization, set up the integration:

Select or Create a Database: In the "Database" tab, select an existing Notion database for meeting notes or let Demodesk create one. If using an existing database, it must have properties that can receive Demodesk data (text fields, date fields, select/multi-select fields, etc.). If creating a new database, Demodesk generates one with default columns: Meeting Title, Date, Attendees, Company, Deal Stage, Summary, and Action Items.

Map Properties to Columns: Navigate to "Property Mapping" to connect Demodesk meeting properties to Notion database columns. Available Demodesk properties include:

• Meeting title, date, and duration
• Attendee names, emails, and roles
• Company name and deal stage
• AI-generated summary (rich text)
• Action items with owners and due dates
• Recording URL
• Call score and talk-to-listen ratio
• Topics discussed and objections raised

Each property maps to a Notion column type. Text properties map to Title or Rich Text columns, dates map to Date columns, and categorical data (deal stage, meeting type) maps to Select columns.

Rich Content Formatting: AI-generated summaries are inserted as the Notion page body, not as a property value. Summaries use native Notion formatting: H2 headings for sections, bullet lists for key points, callout blocks for important takeaways, and to-do blocks for action items. This makes meeting pages scannable and actionable.

Cross-Database Linking: If the workspace has separate databases for accounts, deals, or projects, Demodesk can link meeting pages to related records using Notion's relation property. Configure this in "Database Relations" by selecting the related database and the lookup field (typically company name or deal name).

Action Item Sync: Action items extracted by AI are added as to-do blocks within the meeting page. Each to-do includes the task description, assignee, and due date. When a to-do is checked off in Notion, it does not sync back to Demodesk — the sync is one-way.

Anti-Pattern: "Grant Access to the Entire Workspace" When Notion asks which pages Demodesk can access, do not select the entire workspace. Grant access only to the specific database(s) used for meeting notes. Broad access creates security concerns and can cause confusion if Demodesk accidentally writes to the wrong database.

Anti-Pattern: "Use a Flat Page Instead of a Database" Meeting notes must go into a Notion database, not a flat page. Databases enable filtering by date, company, rep, or deal stage — turning meeting notes into a searchable knowledge base. Flat pages become unmanageable after a few dozen meetings.

Data Sync

All sync is one-way from Demodesk to Notion, triggered when a meeting completes.

Example Prompts

• "Connect Demodesk to my Notion workspace"
• "Create a Notion database for my meeting notes and map all the fields"
• "Link my meeting pages to my existing Accounts database in Notion"
• "Show me how meeting summaries are formatted when they land in Notion"