Linear ↔ HubSpot Integration
Seamlessly connect your customer support workflow with your development process
Comprehensive Settings Guide
General Settings
1️⃣ Enable Ticket Creation from HubSpot tickets to Linear issues
When enabled, new HubSpot tickets will automatically create corresponding Linear issues.
What happens when enabled:
- • New HubSpot ticket → New Linear issue created automatically
- • Ticket properties (title, description, priority) sync to Linear
- • A mapping is created linking the ticket and issue together
- • Updates to either side will sync bidirectionally
⚠️ Important:
You must select a Default Team below before enabling this setting. The default team is where all new Linear issues will be created.
2️⃣ Sync Linear issues to HubSpot only
When enabled, Linear issues can create HubSpot tickets, but HubSpot tickets will NOT automatically create Linear issues.
What happens when enabled:
- • New Linear issue → New HubSpot ticket created automatically
- • New HubSpot ticket → NO Linear issue created (unless manually created)
- • You can still manually create Linear issues from HubSpot using the card UI
- • Updates sync bidirectionally by default
💡 Use Case:
Perfect when your workflow is primarily Linear-driven, and you want HubSpot to reflect Linear activity without creating issues for every support ticket.
3️⃣ Enable one-way updates from Linear to HubSpot only
When enabled together with "Sync Linear issues to HubSpot only", updates only flow from Linear → HubSpot. HubSpot changes will NOT sync back to Linear.
What happens when enabled:
- • Linear issue updated → HubSpot ticket gets updated ✅
- • HubSpot ticket updated → Linear issue does NOT get updated ❌
- • Useful for reporting/tracking purposes only in HubSpot
- • Linear remains the single source of truth
⚠️ Important Requirement:
This setting only works when "Sync Linear issues to HubSpot only" is also enabled. If you want full bidirectional sync, leave this disabled.
4️⃣ Enable bidirectional sync
When enabled, updates to either HubSpot tickets or Linear issues will sync in both directions.
What happens when enabled:
- • Update HubSpot ticket → Linear issue gets updated ✅
- • Update Linear issue → HubSpot ticket gets updated ✅
- • Both systems stay perfectly in sync
- • Changes to title, description, status, priority, assignee all sync
💡 Use Case:
Ideal when both support and engineering teams need to update the same data from their respective tools.
5️⃣ Enable comment sync
Synchronize comments between Linear issues and HubSpot tickets.
What happens when enabled:
- • Comments added in Linear → Synced to HubSpot ticket notes
- • Comments added in HubSpot → Synced to Linear issue comments
- • Author names are preserved in sync
6️⃣ Enable owner sync
Synchronize assignee/owner between Linear and HubSpot.
What happens when enabled:
- • Assign a Linear issue → HubSpot ticket owner gets updated
- • Assign a HubSpot ticket → Linear issue assignee gets updated
- • Team members are automatically matched by email
Team & Project Configuration
Default Team
Required when "Enable Ticket Creation" is turned on. All new Linear issues created from HubSpot tickets will be assigned to this team.
Default Project (Optional)
If specified, new Linear issues will be automatically added to this project within the default team.
Filtered Teams & Projects
Optionally filter which Linear teams and projects should sync with HubSpot. If empty, all teams/projects sync.
Linear-Specific Settings
Custom Field Mapping
Map Linear custom fields to HubSpot custom properties for seamless data transfer.
How it works:
- • Select a Linear field (e.g., "Customer Impact", "Feature Request")
- • Select a corresponding HubSpot property (e.g., "impact_score", "request_type")
- • When Linear issue is created/updated, the field value syncs to HubSpot property
- • Supports text, number, and select-type fields
⚠️ IMPORTANT: Custom Properties & Webhooks
These Linear-Specific Settings control Linear → HubSpot sync only.
If you add custom property mappings (e.g., Linear custom fields → HubSpot custom properties), our webhooks do NOT support custom properties in the reverse direction (HubSpot → Linear).
Solution for HubSpot → Linear custom syncing:
Use HubSpot Workflow Actions (like "Update Linear Issue") to manually push custom property changes from HubSpot to Linear when needed.
Example: You map a Linear custom field "Customer Impact" → HubSpot custom property "impact_score". This works for Linear → HubSpot automatically. But if you update "impact_score" in HubSpot, you'll need a workflow action to update the Linear custom field.
Status Mapping
Map Linear workflow states to HubSpot ticket pipeline statuses.
Configuration Steps:
- Select the Linear team whose statuses you want to map
- For each Linear status (Todo, In Progress, Done, etc.), select the corresponding HubSpot ticket status
- Save your mappings
- When a Linear issue status changes, the HubSpot ticket status updates automatically
💡 Pro Tip:
Different Linear teams can have different status mappings. This allows you to customize sync behavior for each team's workflow.
Label Mapping
Map Linear issue labels to HubSpot ticket properties (dropdown or checkbox).
Configuration Steps:
- Select a HubSpot property (must be dropdown or multi-checkbox type)
- Select the Linear team whose labels you want to map
- For each Linear label (e.g., "Bug", "Feature"), select the corresponding HubSpot property option
- When a Linear issue has labels, they sync to the HubSpot property automatically
✅ Example Use Case:
Map Linear labels like "Bug", "Feature Request", "Customer Request" to a HubSpot property called "Issue Type" with corresponding dropdown options. This helps categorize tickets in HubSpot based on Linear issue classification.