BuildStackFlow
Menu
FLOW Integration Guide

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

A complete blueprint for automating workflows between Close and Linear 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 Linear

Outbound sales dialer vs. product engineering tracker.

Close is a calling-first sales CRM; Linear is an engineering issue tracker. They sit at opposite ends of the org — a useful pairing routes feature requests surfaced on sales calls (logged in Close) into Linear for the product team.

03 · FLOW

Automation Blueprints — make them work together

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

Connection: Zapier RequiredDifficulty: MediumSetup: 20–30 minutes

Feature gap on a call → File an issue

TriggerClose

Custom Activity Logged

Condition

Type = Feature Request

ActionLinear

Create Issue (Feature Request)

Feature gaps reps hear on outbound calls reach engineering's queue instead of staying trapped in call notes.

Feature shipped → Follow up with the account

TriggerLinear

Issue Completed

Condition

Label = Customer Request

ActionClose

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. 1

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

  2. 2

    Create a new Zap/Scenario with the trigger — Close: Custom Activity Logged.

  3. 3

    Add a filter for the condition (Type = Feature Request) so the workflow only fires when it should.

  4. 4

    Add the action in Linear (Create Issue (Feature Request)) 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 Linear 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.
  • Linear: The Free plan caps active issues — active teams outgrow it quickly.
  • Linear: Insights, SAML, and unlimited teams require the Business tier.
  • 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.