Import into Pipedrive — CSV, Excel & PDF

• Overview
• From
• Into

Importing for your users — or for yourself?

Building a product that feeds Pipedrive? A marketplace or sync product, agency onboarding tooling, a product that fills customers’ pipelines — this page is your integration guide: your users bring files, clean records land in Pipedrive (and your backend sees every row first), and nobody leaves your app. Read on.

Just trying to get your own file into Pipedrive? You have the file and the account; the file is the problem — renamed headers, merged columns, a PDF where a spreadsheet should be. See the wizard handle genuinely messy files in the playground (free, no signup). And a run-it-yourself importer is in the works: your own API token, runs on your machine, every row staged for review — and revertible after it lands. Join the waitlist.

Goal: your users bring the file they have — CSV, Excel, even a PDF or a scan — and clean records land in Pipedrive without leaving your product, and without you writing a mapping/validation UI. The pattern is the same every time: embed → validate → deliver. Mildport handles the first two; your webhook handler owns the Pipedrive API call.

1. Embed the importer

<mildport-import
  api-base-url="https://imports.your-infra.example"
  license-key="SIGNED_TENANT_KEY"
  catalog-key="pipedrive"
></mildport-import>

2. Publish a catalog that mirrors Pipedrive

The schema lives in a target catalog, not in host code. Create it in the catalog editor (/admin/catalogs on your engine, or embed <mildport-catalog-editor>), match Persons, Organizations and Deals, and publish. The widget loads that published catalog by catalog-key.

One record type per Pipedrive object (person, organization, deal). Name on a person is required; email is the natural upsert key.

Users then upload anything — renamed headers, six languages, XLSX/ODS, even PDF tables — and Mildport’s deterministic matcher plus the review step produce typed, validated rows.

Need the schema computed per user at runtime, or versioned with your app? That’s the schema-as-code path — pass targets from host code instead of catalog-key.

3. Deliver from your webhook

Clean rows arrive on your signed apply webhook; your handler feeds Pipedrive:

POST https://api.pipedrive.com/v1/persons (api_token) — link persons to orgs by org_id after upserting orgs first

Pipedrive-specific gotchas

• custom fields have hash keys (e.g. 9dc80c50…) — map catalog keys to hashes in your handler, not in user-facing labels.
• import order matters: organizations → persons → deals, so foreign keys resolve.
• burst rate limits are tight on lower plans — queue and retry with backoff.

Why not Pipedrive’s own CSV import?

Pipedrive’s spreadsheet import is a manual flow inside Pipedrive. An embedded importer lets your users load their book of business into your product AND sync it on, with the ID plumbing handled server-side.

---

Try the flow first: the playground (no signup), then the Quickstart and target catalogs. Prices are published — hosted and flat-annual self-host — at mildport.com/#pricing.