Pipedrive + Jobber Integration Guide

This guide walks you through setting up a complete integration between Pipedrive (CRM) and Jobber (field service management). By the end, your sales contacts and service clients will stay in sync across both platforms.

Overview

Goal: Keep Pipedrive Persons and Jobber Clients in sync, so your sales team's contacts automatically flow to your field service team as clients.

What You'll Set Up:

• Pipedrive Persons synced with Jobber Clients
• Pipedrive Organizations synced with Jobber company-type Clients
• Phone and address formatting handled automatically
• Optional: Pipedrive Deals referenced alongside Jobber Jobs

Time Required: 15–20 minutes

Prerequisites

Before starting, ensure you have:

• [ ] A FluxCascade account (sign up free)
• [ ] Admin access to your Pipedrive account
• [ ] Admin access to your Jobber account
• [ ] Both platforms connected to FluxCascade

If you haven't connected your platforms yet, see the Pipedrive integration docs and Jobber integration docs first.

Step 1: Understand the Data Model Differences

Pipedrive and Jobber organize contacts differently:

• Pipedrive separates people (Persons) from companies (Organizations). A Person can belong to an Organization. Emails and phone numbers are stored as arrays (a Person can have multiple).
• Jobber has a single Client object. A Client can be an individual or a company (controlled by the is_company flag). Clients have a single primary email and phone, plus a billing address.

This mapping connects Pipedrive Persons to Jobber individual Clients.

Step 2: Plan Your Field Mapping

Person → Client Field Pairs

Address Handling

Pipedrive stores addresses on Organizations, not Persons. To sync addresses to Jobber Clients, you have two options:

Option A: Sync Organization address to Client billing address

• org.address_street_number + org.address_route → billing_address.street1
• org.address_locality → billing_address.city
• org.address_admin_area_level_1 → billing_address.province
• org.address_postal_code → billing_address.postal_code

Option B: Use a custom Person field for address If you've added a custom address field on Pipedrive Persons, map it directly.

Step 3: Create the Mapping

1. Go to Mappings in FluxCascade
2. Click New Mapping
3. Configure the basics:

Source:

• Connection: Your Pipedrive connection
• Object: Persons

Target:

• Connection: Your Jobber connection
• Object: Clients

Direction: Bidirectional (recommended for active sales-to-service handoff)

4. Click Continue

Step 4: Configure Field Pairs

Basic Fields

1. First Name

   • Source: first_name
   • Target: first_name
   • Transform: None

2. Last Name

   • Source: last_name
   • Target: last_name
   • Transform: None

3. Email (Matching Field)

   • Source: email[0].value
   • Target: email
   • Transform: lowercase
   • Mark as Matching Field

4. Phone

   • Source: phone[0].value
   • Target: phone
   • Transform: phone_e164
   • Default country: US (or your country)

5. Company Name

   • Source: org_name
   • Target: company_name
   • Transform: None

Phone Number Formatting

Pipedrive stores phone numbers in various formats (e.g., (555) 123-4567, 555.123.4567, +15551234567). Jobber expects a consistent format. The phone_e164 transform normalizes all formats to +15551234567.

If a Pipedrive Person has multiple phone numbers, only phone[0].value (the primary) syncs by default. To sync a secondary phone, add another field pair mapping phone[1].value to a Jobber custom field.

Step 5: Set Matching Strategy

1. In mapping settings, find Matching Strategy
2. Select Email as the primary matching field
3. Enable Case Insensitive Matching

Step 6: Organization Mapping (Optional)

To sync Pipedrive Organizations as Jobber company-type Clients:

1. Create a second mapping: Pipedrive Organizations → Jobber Clients
2. Map name → company_name
3. Set a static value: is_company = true
4. Map address fields as described in Step 2

Step 7: Test the Mapping

1. Click Test Sync

2. Review the preview

3. Check for:

   • Correct name mapping
   • Email matching working
   • Phone numbers formatted correctly
   • Company names populated

4. Adjust and re-test if needed

Step 8: Run Initial Sync

1. Click Sync Now
2. Choose Full Sync for initial population
3. Monitor progress in real-time
4. Review completion statistics

Expected Results:

• Pipedrive Persons created as Jobber Clients
• Jobber Clients created as Pipedrive Persons (bidirectional)
• Phone numbers normalized to E.164 format

Step 9: Enable Scheduled Sync

1. Go to mapping Settings
2. Enable Scheduled Sync
3. Choose frequency: Every 15 minutes (recommended)
4. Save

Deals-to-Jobs Consideration

Pipedrive Deals and Jobber Jobs represent different stages of the customer lifecycle. While this guide focuses on contact/client sync, you may also want to create a Deals → Jobs mapping. See the Deals to Jobs guide for a general approach.

Key differences to keep in mind:

• Pipedrive Deal values are monetary amounts; Jobber Job totals include line items
• Pipedrive Deal stages are customizable per pipeline; Jobber uses fixed statuses
• A won Deal in Pipedrive often corresponds to an "Active" Job in Jobber

Verification

Check Pipedrive

1. Open a Person that should have synced
2. Verify Jobber-created persons appear
3. Check field values and phone formatting

Check Jobber

1. Open a Client that should have synced
2. Verify Pipedrive-created clients appear
3. Check field values match

Review Sync Logs

1. Go to Syncs
2. Click on recent sync jobs
3. Verify success rates and any errors

Common Issues & Solutions

Phone Numbers Show as Invalid

Cause: Pipedrive stores numbers without country codes, and the phone_e164 transform can't determine the country.

Solution: Set the default country in the transform configuration. For US numbers, set default country to US.

Multi-Value Email Not Syncing

Cause: Using email instead of email[0].value in the field selector.

Solution: Pipedrive stores emails as arrays. Use email[0].value for the primary email. To sync all emails, concatenate with the JOIN transform.

Organization Names Missing

Cause: The Person's org_id is populated but org_name isn't available as a direct field.

Solution: Use org_name (the resolved Organization name) rather than org_id (the numeric reference).

Duplicate Clients Created

Cause: Email matching not finding existing records.

Solution:

1. Ensure email is the matching field
2. Enable case-insensitive matching
3. Verify emails exist in source records

Best Practices

1. Start with Person → Client sync – Get individual contacts working before adding Organizations

2. Normalize phone numbers early – Apply phone_e164 to avoid format-based duplicates

3. Use email for matching – Most reliable shared identifier between Pipedrive and Jobber

4. Map Organizations separately – Keep Person and Organization mappings independent for clarity

5. Monitor the handoff flow – Track how quickly new Pipedrive contacts appear in Jobber

Next Steps

• Deals to Jobs mapping – Sync opportunities to service jobs
• Phone Formatting guide – Advanced phone number handling
• Field Transformations – Data transformation options