How to Connect 
Pipedrive + 
Jira: Step-by-Step Integration & Automation Guide (2026)
A complete blueprint for automating workflows between Pipedrive and Jira using native connectors, Webhooks, or Zapier/Make.
- Connection
- Middleware
- Zapier Required
- Setup time
- 20–30 minutes
- Difficulty
- Medium
When & why to run Pipedrive with Jira
Sales pipeline vs. enterprise dev/agile tracking.
Pipedrive runs the sales pipeline; Jira runs software delivery. They rarely overlap — teams connect them to turn customer requests or won-deal commitments into Jira issues so engineering can plan the work.
Automation Blueprints — make them work together
The real payoff is the stack. These are concrete Pipedrive ↔ Jira workflows worth building.
Custom build committed → Scope the work
Deal Updated
Status = Won · Custom Build Required
Create Issue in Backlog
Custom-build commitments made in the deal become Jira issues so engineering can plan and deliver them.
Committed work shipped → Update the deal
Issue Status Changed
Status = Done · Label = Customer Commitment
Add Note to Related Deal
Sales knows when customer-committed work ships, so they can update the account and invoice with confidence.
Setup steps
The Zapier/Make path, start to finish.
- 1
Create a Zapier or Make account and connect both Pipedrive and Jira (authorize each via OAuth).
- 2
Create a new Zap/Scenario with the trigger — Pipedrive: Deal Updated.
- 3
Add a filter for the condition (Status = Won · Custom Build Required) so the workflow only fires when it should.
- 4
Add the action in Jira (Create Issue in Backlog) and map the fields from the trigger data.
- 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: Pipedrive and Jira 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+.
- Jira: Advanced Roadmaps and unlimited automation require the Premium tier.
- Jira: Pricing is banded by user count — crossing a band can bump the rate.
- 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.