Pipedrive Integration

Sync your Pipedrive CRM contacts and companies with Propstreet automatically.

Overview

Feature	Support
Market	Global (Nordic-wide)
Sync Direction	Bidirectional
Real-time Updates	Yes (customer-managed sync)
Contacts	✅ Full support
Companies	✅ Full support

Data Mapping

Contact Fields

Pipedrive	Propstreet	Notes
Name	First/Last Name	Parsed from single name field
Email	Email	Primary email synced
Phone	Phone	Primary phone synced
Organization	Connection	Links contact to company
Job Title	Job Title	Synced to company connection
Labels	Tags	Mapped as tags
Notes	Notes	Via Notes API
Custom: Strategy	Strategy	Investment focus (custom field)

Note: Pipedrive supports multiple emails and phones per person. We sync the primary value to Propstreet's single-value fields.

Company Fields

Pipedrive	Propstreet	Notes
Name	Name
Address (country)	Country Code	ISO 2-letter code
Custom: Org Number	External Reference	For Nordic deduplication
Custom: Domain	Domain	For company matching

How Sync Works

Pipedrive → Propstreet

You control the sync through your own integration layer:

Configure Pipedrive Webhooks v2 to send events to your middleware (e.g., Zapier, Make, Azure Logic Apps, n8n, or custom service)
Your middleware transforms and pushes data to Propstreet via our API
Records are matched using email or company domain and created/updated in Propstreet

Pipedrive Webhooks v2 provide near real-time delivery with retry logic—any 2XX response counts as successful delivery.

Propstreet → Pipedrive

When you update a contact in Propstreet, you have two options:

Option A: Webhooks (Recommended)

Register a Propstreet webhook for contact.* and company.* events
Propstreet pushes changes to your endpoint in real-time
Your middleware transforms and pushes to Pipedrive

Option B: Polling

Your integration layer polls the Propstreet API for changes (using updated_since)
Changes are transformed and pushed to Pipedrive via their API
Your Pipedrive records stay in sync

Propstreet recommends polling every 5–15 minutes for delta sync.

Duplicate Handling

We use smart matching to prevent duplicates:

Contacts: Matched by email address first, then Pipedrive person ID via externalRefs
Companies: Matched by domain, then organization number (if configured)

Store Pipedrive IDs in Propstreet's externalRefs array and Propstreet IDs in Pipedrive custom fields for reliable bidirectional sync.

Field Considerations

Multiple Emails and Phones

Pipedrive supports multiple emails and phone numbers per person. Propstreet syncs the primary value only; additional values remain in Pipedrive but are not synced.

Job Title and Organization

Pipedrive stores persons with an organization association. In Propstreet, job title is part of the company connection. When syncing:

The person's organization maps to a company connection in Propstreet
Job title (if stored as custom field or note) maps to the connection's job title field

Notes vs Strategy

Pipedrive has a notes feature for activity logging. For commercial real estate investors:

Investment criteria ("Looking for office buildings, €10M+") → sync to Propstreet's strategy field via a custom Pipedrive field
Activity logs ("Called Jan 15, discussed pipeline") → sync to Propstreet's Notes API

Create a custom Pipedrive field investor_strategy to separate investment focus from activity notes.

Website and Domain

Pipedrive organizations don't have a native website field. For company matching:

Create a custom field domain in Pipedrive to store the company's web domain
Use this for deduplication alongside organization number

Organization Number (Nordic)

Pipedrive doesn't have a built-in organization number field. For Nordic markets, create a custom field in Pipedrive to store:

Norway: Organisasjonsnummer
Sweden: Organisationsnummer
Denmark: CVR-nummer
Finland: Y-tunnus

This enables accurate company matching via Propstreet's externalRefs field.

Setup Requirements

To build a Pipedrive integration, you'll need:

Pipedrive Account - Any plan; Advanced or higher recommended for more API tokens
Propstreet API Credentials - Generate in your account settings
Integration Layer - Middleware to handle webhooks and API calls (Zapier, Make, Azure Logic Apps, n8n, or custom)
Pipedrive Custom Fields - Create fields for: propstreet_contact_id, propstreet_company_id, investor_strategy, domain, and optionally org_number

Getting Started

Generate Propstreet API credentials in your account settings (requires login)
Review the Propstreet API documentation for endpoints and data models
Set up your integration layer to sync data between Pipedrive and Propstreet
Create custom fields in Pipedrive for Propstreet IDs and investor strategy
Configure Pipedrive Webhooks v2 for person and organization events
Test with a small dataset before full rollout

You're responsible for building and maintaining the integration.

Frequently Asked Questions

Which Pipedrive plans support the integration?

The integration works with all Pipedrive plans. However, API token budgets vary by plan—Advanced and higher tiers provide more daily API tokens.

How does Pipedrive rate limiting work?

Pipedrive uses token-based rate limiting with daily budgets (30,000 base tokens × plan multiplier × seats) and burst limits (10 requests per 2 seconds for Search API). Design your integration to:

Use webhooks instead of polling where possible
Avoid heavy Search API usage—use stable IDs and a mapping database instead
Implement exponential backoff on 429 responses

How often does data sync?

Sync frequency depends on how you configure your integration layer:

Real-time: Use Pipedrive Webhooks v2 to trigger immediate syncs
Scheduled: Poll Propstreet API every 5–15 minutes (using updated_since)
Manual: Trigger syncs on-demand

What happens to data if I stop syncing?

Your data remains in both systems. No data is deleted. Use externalRefs to maintain record linkage if you resume syncing later.

Can I choose which contacts to sync?

Yes. Your integration layer controls which records to sync. Common filtering approaches:

Pipedrive filters or custom fields
Labels (e.g., only sync persons with "Investor" label)
Organization associations

How should I handle merge conflicts?

Design your integration layer to handle conflicts. Common approaches:

Last write wins: Compare updatedUtc (Propstreet) and update_time (Pipedrive) to determine the most recent change
Source of truth: Designate one system as authoritative for specific fields (e.g., CRM for identity, Propstreet for investment strategy)
Manual review: Flag conflicts for human review

Propstreet supports ETags for optimistic concurrency—use If-Match headers to prevent lost updates.