Linear

Bidirectional sync links issues to PRs. Issues auto-update from In Progress to Done as PRs move from draft to merged. Use issue IDs in branch names for auto-linking.

Via Zapier, you can turn Gmail emails into Linear issues automatically — the most popular pattern is: star or label an email in Gmail, and Zapier creates a new issue in Linear using the email subject as the issue title and the body as the description. You can also trigger on any email matching a Gmail search query (e.g. emails from a specific domain), which is useful for turning support requests or sales inquiries into tracked work items. During setup you connect both accounts, choose a Gmail trigger (new starred email, new labeled email, or new email matching a search), then map fields — subject to title, body to description, sender to a custom field — and activate the Zap. Issues created this way show as authored by 'Zapier' in Linear, not the individual user. You can add Zapier filter steps to skip emails you don't want converted, keeping your Linear workspace clean. Data flows: Gmail email (subject, body, sender) → Linear issue (title, description, optional custom fields). One-way: Gmail to Linear. No data flows back from Linear to Gmail in standard templates. Pain points: Zapier polls Gmail every 5–15 minutes depending on your plan, so there is a delay between an email arriving and the issue appearing in Linear — not suitable for time-critical alerts. The email body arrives as plain text or raw HTML, not clean markdown, so Linear issue descriptions can look messy. Attachments in emails do not transfer to Linear. Each email processed counts as one Zapier task toward your monthly limit. Issues are created under the Zapier bot identity, not individual team members.

Linear has a first-party GitLab integration that links Linear issues to GitLab Merge Requests and automates your issue status based on MR activity. When a developer opens or merges an MR that references a Linear issue ID in the title or description (using magic words like 'Fixes ENG-123' or 'Closes ENG-123'), Linear automatically moves the issue from In Progress to Done — no manual status updates needed. You can also copy a Linear-formatted branch name directly from the issue and use it in GitLab so the link is detected automatically. Setup requires a GitLab Personal Access Token or Project Access Token with at least read_api scope, plus a webhook configured in GitLab to send MR events to Linear. The integration supports both GitLab.com and self-hosted instances, as long as your instance is publicly reachable. Per-team workflow automations let different teams use different issue status mappings based on target branch or MR approval requirements. Data flows: GitLab MR events (opened, drafted, approved, merged, closed) flow into Linear to update issue status. Linear issue IDs flow into GitLab as linkback comments on MRs. Branch name suggestions flow from Linear to developers. Direction is primarily GitLab → Linear for status automation, with Linear → GitLab for linkback comments. Pain points: Self-hosted GitLab setup is more complex and requires the instance to be publicly accessible — internal-only instances won't work. Linkbacks post under the name of the token owner rather than a bot account, so Clockify recommends creating a dedicated Linear user for cleaner attribution. CI pipeline events for MR merge checks require additional webhook configuration. The integration cannot parse links from commit messages or MR comments — only from the MR title or description.

Create/link issues from Intercom conversations. Status visible in Intercom sidebar. Business+ plan.

Loom links auto-embed as rich previews in Linear issue descriptions and comments.

Via Zapier, when a new issue is created in Linear, Zapier instantly creates a corresponding task in Motion. Motion is an AI scheduling tool that auto-prioritizes and time-blocks your day, so this connection lets engineers track work in Linear while Motion schedules when they'll actually do each piece of work. You connect both accounts in Zapier, set 'New Issue in Linear' as the trigger, map the issue title and description to the Motion task name and notes, set a due date if present, and activate the Zap. Motion then applies its AI scheduling — fitting the task into open calendar slots based on priority and deadline. You can also trigger on 'Updated Issue in Linear' to push re-prioritized issues into Motion as fresh tasks. This is especially useful for solo founders or small teams where one person is both managing the backlog in Linear and scheduling personal work in Motion. Data flows: Linear issue (title, description, due date, priority) → Motion task (name, notes, deadline). One-way push from Linear to Motion. Motion handles scheduling from there; no data flows back to Linear. Pain points: The integration is one-way only — completing a task in Motion does not update the Linear issue status. Duplicate tasks can build up in Motion if issues are frequently updated and you use the 'Updated Issue' trigger. There is no built-in deduplication, so you may need a Zapier filter to avoid creating a new Motion task for every minor edit in Linear. Teams larger than 2–3 people may find Motion's individual focus less useful for shared issue tracking.

PostHog Data Warehouse syncs Linear issues, projects, teams. Create issues from PostHog with bidirectional links.

Create/link Linear issues from Figma designs. Design context in issue attachments.

Linear VS Code extension — view, create, update issues from the editor.

Vercel Preview Comments convert into actionable Linear issues with screenshots.

Sync Linear issues with Airtable records for engineering project tracking via Zapier

Linear for Slack — create issues from messages, receive status updates, subscribe channels to projects. Bi-directional.