> For the complete documentation index, see [llms.txt](https://help.getmobly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.getmobly.com/help-center/integrations/crm/pipedrive/setup-guide.md). # Pipedrive setup guide Mobly's Pipedrive integration syncs every captured-and-enriched lead into your Pipedrive Persons (and optionally Organizations), with field mapping, qualifier mapping, and per-event campaign sync. Connection runs through Mobly's new integration platform. ## What you can do * **Sync leads to Pipedrive Persons** — every Mobly-captured lead becomes a Person in Pipedrive, matched by Email * **Sync to Organizations** — Mobly creates or updates the lead's Organization based on company name or domain, and links the Person to it * **Map any Mobly field to any Pipedrive custom field** — Persons and Organizations both * **Use Pipedrive single-option and multiple-option fields** for qualifier mapping * **Toggle Automatic vs Manual sync** — see [Sync modes](/help-center/integrations/crm/sync-modes.md) ## What's not supported (yet) * **Deal sync** — Mobly doesn't create or update Deals; only Persons + Organizations. To turn Mobly leads into Deals, set up a Pipedrive Workflow Automation triggered when a Person is created or updated by Mobly * **Pipeline-specific routing** — Mobly creates Persons but doesn't route them into specific Pipelines or Stages. That's a downstream Workflow concern * **Activity logging** — Mobly doesn't write Pipedrive Activities (calls, meetings) for captured leads. Activity history lives in Mobly itself. For what activity logging looks like on the CRMs that support it (HubSpot, Salesforce, Zoho), see [Finding Mobly activities in your CRM](/help-center/integrations/crm/finding-activities-in-your-crm.md) * **Multi-integration** — running Pipedrive alongside another CRM in the same Mobly org isn't supported today (one CRM per org) ## Before you connect You'll need: * A **Pipedrive user** with: * **Admin permissions** (or a custom role with create/edit access to Persons, Organizations, and any custom fields you've mapped) * A **Mobly admin account** to view and configure Integrations Pipedrive permissions are role-based — confirm under **Settings → Manage users** that the connecting user has the right role before authorizing the connection. ## Connect the integration 1. Go to **Integrations → Pipedrive** in Mobly 2. Click **Connect** on the Connect tab 3. Sign in to Pipedrive in the OAuth window and approve the permissions Mobly requests Detailed walkthrough: see [Connecting your CRM](/help-center/integrations/crm/connecting.md). ## Configure data flow Work through the tabs in order: 1. [**Mapping**](/help-center/integrations/crm/field-mapping.md) — match Mobly fields to Pipedrive fields. Persona section maps to Person; Company section maps to Organization. 2. [**Qualifiers**](/help-center/integrations/crm/qualifiers.md) — define qualifiers and map values to Pipedrive single-option/multiple-option field choices. 3. [**Campaigns**](/help-center/integrations/crm/campaign-mapping.md) — link Mobly events to Pipedrive Campaigns (if your Pipedrive plan supports the Campaigns feature) or to a custom field representing event attribution. 4. [**Sync mode**](/help-center/integrations/crm/sync-modes.md) — Automatic by default; switch to Manual on the Connect tab if needed. ## Pipedrive-specific configuration tips **Persons + Organizations as a pair.** Mobly creates both when capturing a lead with company info. Make sure your mappings cover both objects — Persona section for Person, Company section for Organization. Skipping the Organization mapping means leads sync as Persons without their company association. **Custom fields per object.** Pipedrive has separate custom field schemas for Persons and Organizations. Add Mobly-specific custom fields under **Settings → Data Fields** before mapping, picking the right object type (Person vs Organization). **Field types.** Match Mobly's TEXT/EMAIL/URL/PHONE badges to the matching Pipedrive field type. Pipedrive has a richer set of field types (Address, Date Range, Numerical, Currency) — pick the closest match for each Mobly field. **Long values.** Pipedrive text fields default to 255 characters. For longer Mobly fields (notes, descriptions), change the field type to **Large text** (paragraph) under **Settings → Data Fields**. **Single-option vs multiple-option fields.** Pipedrive single-option fields reject multi-value sends — use them only for Mobly qualifiers configured as **Single**. For Mobly qualifiers in **Multiple** mode, map to Pipedrive multiple-option fields. **Pipedrive Campaigns.** Campaign tracking in Pipedrive varies by plan tier. If your plan doesn't include the Campaigns feature, use a custom field on the Person/Organization to capture event attribution from Mobly instead. ## Troubleshooting If a synced lead shows up in **Reconciliation → Failed**, see [Fixing Pipedrive sync errors](/help-center/integrations/crm/pipedrive/troubleshooting.md) — there's a section per error category with the fix. ## Related articles * [Connecting your CRM](/help-center/integrations/crm/connecting.md) * [Sync modes](/help-center/integrations/crm/sync-modes.md) * [Field mapping](/help-center/integrations/crm/field-mapping.md) * [Qualifiers](/help-center/integrations/crm/qualifiers.md) * [Mapping campaign fields](/help-center/integrations/crm/campaign-mapping.md) * [Reconciliation](/help-center/integrations/crm/reconciliation.md) * [Fixing Pipedrive sync errors](/help-center/integrations/crm/pipedrive/troubleshooting.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.getmobly.com/help-center/integrations/crm/pipedrive/setup-guide.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.