BuildStackFlow
Menu
FLOW Integration Guide

How to Connect Close logoClose + Pipedrive logoPipedrive: Step-by-Step Integration & Automation Guide (2026)

A complete blueprint for automating workflows between Close and Pipedrive using native connectors, Webhooks, or Zapier/Make.

Connection
Middleware
Zapier Required
Setup time
20–30 minutes
Difficulty
Medium
The Core Stack

When & why to run Close with Pipedrive

Built-in calling for outbound vs. visual pipeline for SMB.

Close bakes calling, SMS, and email sequencing directly into the CRM — ideal for high-velocity inside sales teams that live on the phone. Pipedrive is a broader, visual pipeline CRM for general SMB sales. Choose Close for call-heavy outbound; choose Pipedrive for a simple, affordable all-round sales pipeline.

03 · FLOW

Automation Blueprints — make them work together

The real payoff is the stack. These are concrete Close ↔ Pipedrive workflows worth building.

Connection: Zapier RequiredDifficulty: MediumSetup: 20–30 minutes

Qualified by SDR → Hand to the AE pipeline

TriggerClose

Lead Status Changed

Condition

Status = Qualified

ActionPipedrive

Create Deal + Assign AE

Teams that qualify by phone in Close pass hot leads into Pipedrive for account executives to close.

Deal won → Log the outcome back

TriggerPipedrive

Deal Updated

Condition

Status = Won

ActionClose

Update Lead + Log Outcome

Close keeps a complete activity history even when the final deal is closed in Pipedrive.

Setup steps

The Zapier/Make path, start to finish.

  1. 1

    Create a Zapier or Make account and connect both Close and Pipedrive (authorize each via OAuth).

  2. 2

    Create a new Zap/Scenario with the trigger — Close: Lead Status Changed.

  3. 3

    Add a filter for the condition (Status = Qualified) so the workflow only fires when it should.

  4. 4

    Add the action in Pipedrive (Create Deal + Assign AE) and map the fields from the trigger data.

  5. 5

    Test with a live record, verify the result, then turn the automation on and repeat for the other workflows.

Edge cases & rate limits

What breaks in production — plan for these before you scale.

  • Field mapping: Close and Pipedrive fields rarely map 1:1 — normalize dates, currencies, and dropdown/picklist values explicitly.
  • Pick a source of truth per field to avoid two-way syncs overwriting each other in a loop.
  • Pipedrive: Higher email/automation limits and forecasting require Professional+.
  • Zapier/Make task usage is metered — high-volume workflows can burn through your monthly task/operations quota, so batch where possible.
  • Watch API rate limits on bulk backfills — throttle or batch to stay under each tool's per-second/per-minute caps.

BuildStackFlow independently reviews SaaS tools and integrations.