How to Connect 
Close + 
Jira: Step-by-Step Integration & Automation Guide (2026)
A complete blueprint for automating workflows between Close and Jira using native connectors, Webhooks, or Zapier/Make.
- Connection
- Middleware
- Zapier Required
- Setup time
- 20–30 minutes
- Difficulty
- Medium
When & why to run Close with Jira
Outbound sales dialer vs. enterprise dev tracking.
Close is a calling-first sales CRM for outbound; Jira is the enterprise software delivery tracker. Opposite ends of the org — a useful pairing routes feature requests surfaced on sales calls (logged in Close) into Jira for engineering.
Automation Blueprints — make them work together
The real payoff is the stack. These are concrete Close ↔ Jira workflows worth building.
Feature gap on a call → File an issue
Custom Activity Logged
Type = Feature Request
Create Issue in Backlog
Feature gaps reps hear on outbound calls reach engineering's backlog instead of staying trapped in call notes.
Requested work shipped → Follow up
Issue Status Changed
Status = Done · Label = Customer Request
Create Follow-up Task on Lead
Reps get a task to re-engage the account the moment its requested feature ships.
Setup steps
The Zapier/Make path, start to finish.
- 1
Create a Zapier or Make account and connect both Close and Jira (authorize each via OAuth).
- 2
Create a new Zap/Scenario with the trigger — Close: Custom Activity Logged.
- 3
Add a filter for the condition (Type = Feature Request) 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: Close 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.
- 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.