Pipedrive

Pipedrive CRM sync with automatic activity creation, person matching, deal stage updates, and meeting note logging — built around Pipedrive's activity-based selling methodology.

When to Use This Connection

Use this connection when the user:

• Wants to connect their Pipedrive account so every Demodesk meeting creates a completed activity
• Needs to configure person matching rules between Demodesk attendees and Pipedrive persons
• Wants deal stages to advance automatically based on meeting outcomes
• Needs meeting notes and AI summaries logged to Pipedrive deals
• Wants to set up custom field mapping for Pipedrive-specific data models

What This Connection Does

Guide the user to Settings > Integrations > Pipedrive in Demodesk at https://demodesk.com/manage/settings/integrations/pipedrive. Pipedrive supports two authentication methods: OAuth 2.0 (recommended) or API token. For OAuth, click "Connect Pipedrive" and authorize. For API token authentication, the user navigates to Pipedrive > Settings > Personal preferences > API, copies the token, and pastes it into Demodesk's configuration screen.

After authentication, configure the integration:

Person Matching: Demodesk matches meeting attendees to Pipedrive persons by email address. When no match is found, a new person is created in Pipedrive with the attendee's name, email, organization, and role — enriched with context from the meeting (job title, company size if available). Configure matching rules in the "Person Matching" tab: strict email match, or domain-based matching that links unknown contacts to existing organizations.

Activity Type Mapping: Every completed Demodesk meeting creates a completed activity in Pipedrive. Map Demodesk meeting types to Pipedrive activity types (call, meeting, demo, etc.) in the "Activity Mapping" tab. Each activity includes: subject, duration, attendees, notes, and a link to the recording. This feeds directly into Pipedrive's activity-based pipeline reports.

Deal Stage Automation: Configure rules that advance deal stages based on meeting outcomes. For example: "When a discovery meeting is completed and outcome is 'qualified,' move the deal from 'Lead In' to 'Contact Made.'" Set these rules in the "Deal Automation" tab. Each rule specifies a meeting type, an outcome, and the target deal stage.

Meeting Notes and AI Summaries: After each meeting, AI-generated summaries and action items are logged as notes on the relevant Pipedrive deal. Notes include: summary, key discussion points, action items with owners, objections raised, and next steps. These appear in the deal's activity timeline.

Custom Field Mapping: Pipedrive custom fields can be mapped to Demodesk meeting data. Navigate to "Field Mapping" to connect Demodesk properties (meeting score, talk-to-listen ratio, topics discussed) to Pipedrive custom fields on deals, persons, or organizations.

Anti-Pattern: "Use API Token for Team Accounts" API tokens are tied to individual Pipedrive users. If the user who generated the token leaves the organization or changes their password, the integration breaks. For team use, always prefer OAuth 2.0 authentication, which is tied to the Pipedrive company account rather than an individual user.

Anti-Pattern: "Automate Every Stage Transition" Do not create deal stage automation rules for every possible meeting outcome. Over-automation leads to deals jumping stages unexpectedly when meetings are miscategorized. Start with one or two clear transitions (e.g., discovery completed moves to "qualified") and add more rules only after validating they work correctly.

Data Sync

Sync is real-time and event-driven.

Example Prompts

• "Connect my Pipedrive account to Demodesk"
• "Map my discovery calls to the 'Meeting' activity type in Pipedrive"
• "Set up a rule to advance deals to 'Qualified' when a discovery meeting outcome is positive"
• "Why are my Demodesk meetings not showing up as activities in Pipedrive?"