How to Integrate Pipedrive with Your Headless CMS

What is Pipedrive?

Pipedrive is a sales CRM built around pipelines, deals, contacts, activities, and sales reporting. Sales teams use it to track prospects from first contact to closed deal, assign follow-up tasks, and measure conversion across stages. It’s widely used by small and midsize teams that want a pipeline-first CRM without a large admin footprint.

Why integrate Pipedrive with a headless CMS?

Sales teams lose context when published content and CRM records live in separate systems. A product marketer publishes a new industry landing page, but the sales team doesn’t know which account segment it targets. A sales rep shares an outdated one-pager because the latest version never made it into Pipedrive. Someone copies campaign notes by hand, and the deal record is already stale by Friday.,Connecting Pipedrive to a headless CMS category tool solves that gap by turning content events into CRM actions. When a page, offer, case study, or sales asset is published, the integration can create or update a Pipedrive deal, attach a note with the live URL, assign an activity to the account owner, or tag a person with the campaign that generated interest.,With Sanity’s AI Content Operating System, structured content in the Content Lake is typed JSON, so Pipedrive doesn’t need to parse HTML or guess which fields matter. Webhooks fire on publish, GROQ selects exactly the fields Pipedrive needs, and Functions can run the server-side sync without a separate queue service. The trade-off is that you still need to map your business rules carefully, especially around duplicate people, organization matching, and pipeline stage IDs.

Architecture overview

A typical flow starts when an editor publishes a sales asset, campaign page, or account-specific offer in Sanity Studio. A Sanity webhook fires on the publish mutation and sends the document ID to a Sanity Function or webhook endpoint. That server-side code uses GROQ to fetch the fields Pipedrive needs, such as title, slug, campaign type, target segment, deal value, owner email, related account, and contact email. The function then calls Pipedrive’s REST API through the official Node SDK, using an API token stored as a server-side secret. Depending on your rules, it can add a person, find or create an organization, create a deal in a specific pipeline, add a note with the published URL, and create an activity for the sales owner. The end user sees the published web experience, while the sales team sees the right context inside Pipedrive within seconds instead of waiting for a manual update.

Common use cases

Step-by-step integration

1. 1

   Set up Pipedrive access

   Create or choose a Pipedrive account, then generate an API token from Personal preferences > API. Use OAuth instead if you’re building a shared app for multiple Pipedrive customers. Install the official SDK with npm install pipedrive @sanity/client.

2. 2

   Model the content in Sanity Studio

   Create schemas for the content that should affect sales, such as campaignPage, salesAsset, accountOffer, and caseStudy. Include fields like title, slug, targetSegment, estimatedValue, pipedrivePipelineId, pipedriveStageId, ownerEmail, relatedAccount, and primaryContactEmail.

3. 3

   Create the publish trigger

   Add a Sanity webhook filtered to the document types you want to sync, for example *[_type in ["campaignPage", "salesAsset", "accountOffer"]]. Send a small payload with the document ID, mutation type, and dataset. If you prefer to keep logic inside Sanity, run the same code in a Function triggered by content mutations.

4. 4

   Fetch the exact fields with GROQ

   In your handler, use @sanity/client and a GROQ projection to fetch only the fields needed for Pipedrive. Join referenced account, owner, and contact documents in the same query so your sync code doesn’t make extra reads.

5. 5

   Call Pipedrive’s API

   Use the Pipedrive Node SDK to add or update people, organizations, deals, notes, and activities. Keep the API token in server-side environment variables, and add duplicate checks before creating new people or organizations.

6. 6

   Test the full customer path

   Publish a test campaign page, confirm the webhook ran, verify the deal or note in Pipedrive, and click through the frontend page. Test updates and deletes too, because publish-only logic often misses stale CRM notes.

How Sanity + Pipedrive works

CMS approaches to Pipedrive

Keep building

Explore related integrations to complete your content stack.