Reference · built on requestConnectorWork & ticket management

Linear

Issues, projects, cycles, and workflow states from Linear workspaces through the Linear GraphQL API and webhooks.

Request accessPricing ↗

About

Linear is an issue tracker for software teams. A workspace holds teams, and each team owns issues, cycles, projects, labels, and a set of workflow states that act as its status field. There is one GraphQL endpoint, https://api.linear.app/graphql, with a public schema you can explore, and a TypeScript SDK.

Through Fibric, an operator subscribes to Issue and Comment webhooks, reads the issue and its team's workflow states, and proposes a state change, an assignee, or a comment for your approval. Each approved change is kept as a receipt: what changed, why, and how it can be undone.

This is a reference listing. It documents what Fibric would read from Linear and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Issues by id or by team through the issue, team, and issues queries, with title, description, assignee, and state
  • A team's workflow states through the workflowStates query
  • Issues assigned to a person through user(id) and its assignedIssues connection
  • Data change webhooks for Issues, Issue comments, Issue labels, Projects, Project updates, Cycles, Documents, Initiatives, Customers, and Customer Requests
  • Issue SLA webhooks, and updatedFrom fields on update payloads showing the prior values
  • Webhook actions of create, update, and remove, each with actor, createdAt, data, and url

Proposed actions

  • Target capability: propose an issue update through the issueUpdate mutation, including stateId
  • Target capability: propose a new issue through issueCreate with a title, description, and teamId
  • Target capability: propose a comment on an issue, using an OAuth app granted the comments:create scope

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Respond to an uptime alert

    When a monitor fires, the operator drafts a Linear issue in the on-call team with the alert context, proposes it, and posts the issue link back to the paging channel.

    With Uptime Response

  • Hand off on-call cleanly

    At shift change, the operator lists open issues touched during the shift with their latest state changes and proposes the handoff note for the outgoing engineer to approve.

    With On-call Handoff

  • Turn feedback into issues

    Recurring customer themes become proposed issues linked to Customer Requests, so the product team sees demand without duplicate tickets.

    With Feedback Themes

  • Watch the error budget

    When error budget burn crosses a threshold, the operator proposes moving reliability issues into the current cycle and comments on why.

    With Error Budget

Requirements

  • A Linear workspace and a user or OAuth app with access to the teams the operator reads
  • A workspace admin, or an OAuth app with the admin scope, to create webhooks in API settings
  • An HTTPS endpoint that answers within 5 seconds and checks the Linear-Signature header
  • An actor choice for OAuth apps: resources created as the authorizing user or as the application
Authentication
A personal API key from Security & access settings in the Authorization header, or an OAuth 2.0 app with scopes such as read, write, issues:create, comments:create, and admin, using a Bearer token.

Limits

  • API keys allow 2,500 requests per hour per user; OAuth apps allow 5,000 per user or app user
  • Complexity is capped per hour at 3,000,000 points for API keys and 2,000,000 for OAuth apps, with 10,000 per single query
  • Rate limit errors return HTTP 400 with a RATELIMITED code, so the connector reads the X-RateLimit headers to pace itself
  • Webhook deliveries that fail are retried at most 3 times, after 1 minute, 1 hour, and 6 hours

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Linear ↗

Questions and answers

Is there a REST API?
No. Linear exposes a single GraphQL endpoint at https://api.linear.app/graphql. Queries such as viewer, teams, issue, and workflowStates read data; mutations such as issueCreate and issueUpdate write it. The schema can be explored in Apollo Studio without a login.
How does the connector check a webhook?
Linear sends a Linear-Signature header: a hex-encoded HMAC-SHA256 of the raw body, signed with the webhook's signing secret. The connector recomputes it, compares, and rejects payloads whose webhookTimestamp is more than a minute from the time it sees them.
Which webhook scope should we choose?
A webhook targets a single team or all public teams. Only workspace admins, or OAuth apps with the admin scope, can create or read webhooks. Payloads carry action, type, actor, createdAt, data, url, and, on updates, updatedFrom with the previous values.
Ask about Linear

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Linear through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy