Salesforce Integration

Sync your Salesforce CRM contacts and accounts with Propstreet automatically.

Overview

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

Data Mapping

Contact Fields

Salesforce	Propstreet	Notes
FirstName	First Name
LastName	Last Name
Email	Email	Primary email synced
MobilePhone / Phone	Phone	Mobile preferred
Title	Job Title	Synced to company connection
AccountId	Connection	Links contact to company
Propstreet_Contact_Id__c	ID	External ID field (create this)
Custom: Investor Strategy	Strategy	Investment focus (custom field)

Note: Salesforce supports multiple phone fields. We recommend syncing MobilePhone to Propstreet's phone field; if mobile is empty, use the main Phone.

Account Fields (Company)

Salesforce	Propstreet	Notes
Name	Name
Website	Homepage URL	Full URL synced
—	Domain	Set directly or auto-extracted from URL
BillingCountry	Country Code	Map to ISO 2-letter code
Propstreet_Company_Id__c	ID	External ID field (create this)
Custom: Organization Number	External Reference	For Nordic deduplication

How Sync Works

Salesforce → Propstreet

You control the sync through your own integration layer:

Configure Salesforce Change Data Capture (CDC) or Platform Events to send changes to your middleware
Your middleware transforms and pushes data to Propstreet via our API
Records are matched using email, domain, or External ID and created/updated in Propstreet

Salesforce CDC provides near real-time change notifications for create, update, delete, and undelete events.

Propstreet → Salesforce

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 Salesforce using External ID upsert

Option B: Polling

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

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

Duplicate Handling

Salesforce's External ID upsert is the most reliable way to prevent duplicates:

Create External ID fields in Salesforce:
- Propstreet_Contact_Id__c (Text, External ID, Unique)
- Propstreet_Company_Id__c (Text, External ID, Unique)

Store Salesforce IDs in Propstreet's externalRefs:

{
  "externalRefs": [{ "namespace": "salesforce", "id": "003xx000001234ABC" }]
}

Use Salesforce upsert by External ID:

PATCH /services/data/v62.0/sobjects/Contact/Propstreet_Contact_Id__c/{propstreetId}

This approach ensures deterministic matching without relying on name or email alone.

Field Considerations

External ID Strategy

Store cross-system IDs to enable reliable bidirectional sync:

In Salesforce:

Create Propstreet_Contact_Id__c as External ID (unique) on Contact
Create Propstreet_Company_Id__c as External ID (unique) on Account

In Propstreet:

Use externalRefs with namespace "salesforce" containing the Salesforce record ID

Multi-Company Relationships

Commercial real estate investors often have multiple company affiliations (fund manager, board member, personal investments). Propstreet models this as Links with their own API endpoints.

For Salesforce, you have two options:

Option A: Primary Company Only (Simpler)

Use the standard Contact.AccountId for the primary company
Accept that secondary affiliations won't sync

Option B: Full Relationship Fidelity (Recommended)

Create a custom junction object like Investor_Affiliation__c:
- Contact__c (Lookup to Contact)
- Account__c (Lookup to Account)
- Job_Title__c (Text)
- Is_Primary__c (Checkbox)
- Propstreet_Link_Id__c (External ID)
Sync Propstreet Links to this object

Notes vs Strategy

Propstreet has two different fields for text information:

Strategy — Investment focus (e.g., "Office properties, €10–50M, Nordics")
Notes — Activity log entries (call notes, meeting summaries)

Create a custom Salesforce field for Investor_Strategy__c to separate investment criteria from general notes and activity history.

Phone Numbers

Salesforce has separate fields for Phone, MobilePhone, HomePhone, etc. We recommend:

Sync MobilePhone to Propstreet's phone field
If MobilePhone is empty, fall back to Phone
Other phone fields remain in Salesforce only

Organization Number (Nordic)

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

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

Use this with Propstreet's externalRefs for accurate company matching.

Conflict Resolution

For bidirectional sync, design your integration to handle conflicts. Recommended approaches:

Field Ownership Matrix:

Identity fields (name, email, phone): Salesforce wins
Network enrichment (tags, strategy): Propstreet wins
Relationship data (primary company): Propstreet wins
Compliance/consent flags: Salesforce wins

Loop Prevention:

Check the change_initiator field in Propstreet webhooks to skip events your integration triggered
Filter Salesforce CDC events made by your integration user

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

Setup Requirements

To build a Salesforce integration, you'll need:

Salesforce Account — Professional or higher recommended; Enterprise+ for Change Data Capture
Connected App — Configure OAuth 2.0 for server-to-server authentication (JWT bearer flow recommended)
Propstreet API Credentials — Bot User + Client Credentials for production
Integration Layer — Middleware to handle events and API calls (MuleSoft, Azure Logic Apps, n8n, or custom)
Custom Fields — Create External ID fields and any additional fields (organization number, investor strategy)

Change Data Capture Note

Salesforce CDC requires Enterprise Edition or higher. Without CDC, you can integrate using:

Scheduled polling of Salesforce REST API
Apex triggers with outbound messages
Platform Events (with custom implementation)

Getting Started

Generate Propstreet API credentials in your account settings (requires login)
Create a Connected App in Salesforce Setup and configure OAuth
Create External ID custom fields on Contact and Account
Review the Propstreet API documentation for endpoints and data models
Set up your integration layer to sync data between Salesforce and Propstreet
If using real-time sync, configure Salesforce CDC and/or Propstreet webhooks
Test with a small dataset before full rollout

You're responsible for building and maintaining the integration.

Frequently Asked Questions

Which Salesforce editions support the integration?

The integration works with all Salesforce editions. However:

Change Data Capture requires Enterprise Edition or higher
API limits vary by edition—higher tiers have more generous limits

How does Salesforce rate limiting work?

Salesforce uses concurrent and daily API call limits based on your edition and number of user licenses. For high-volume sync:

Use Composite API to batch up to 25 operations per call
Use sObject Collections to upsert up to 200 records per call
Use Bulk API 2.0 for initial loads (async, handles millions of records)

How often does data sync?

Sync frequency depends on how you configure your integration layer:

Real-time: Use Salesforce CDC + Propstreet webhooks for 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 External ID fields and 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:

Salesforce record types or custom fields
Reports or SOQL queries (e.g., only sync contacts with certain tags)
Account-based filtering (sync contacts linked to specific accounts)

How should I handle merge conflicts?

Design your integration layer to handle conflicts:

Last write wins: Compare updatedUtc (Propstreet) and LastModifiedDate (Salesforce)
Source of truth: Designate one system as authoritative for specific fields
Manual review: Flag conflicts for human review