Skip to content
Start in the sandbox
All connectors
Linear logo

Linear

Project & work management

Turn requests and orders into Linear work, and keep status in step across your tools.

20 ways to read, 19 ways to write, each write switched on by you.

Try this in the sandboxBring us a workflow

Quality checks

Built and tested with example responses.

  1. Ready to connect: doneEvery listed action is built in.
  2. Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Linear with Nexra

Connected, approved, proven.

The things teams do most with Linear, an example flow with a person in the loop, and what Nexra keeps as proof.

Top actions

  • Attach link to issueattachments.upsertApproval by rule
  • Add issue commentcomments.createApproval by rule
  • List issue attachmentsattachments.listRead

Example flow

  1. Linear · List issue attachmentsattachments.listDone
  2. Linear · Attach link to issueattachments.upsertMaker-checker
  3. Nexra · Record the decision and result in the evidence chainProven

Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Linear.

What gets logged

  • Whether it ran on its own or who approved it, and under which rule
  • A fingerprint of the exact request sent to Linear
  • Linear's reply: what it created or changed
  • One entry in the evidence chain, linked to the one before

Try this in the sandbox

Run the whole flow with test data in your sandbox, then connect your own account when you are ready to go live.

Try this in the sandboxBring us a workflow

For developers

Technical detail

Linear issues, projects, milestones, cycles, labels, workflow states, comments, link attachments, teams, users, initiatives and customer requests.

Linear Orbit, Inc. API docs
Source actions
20
Destination actions
19
Data types
15

What you can map

Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.

attachments2
  • List issue attachmentsSource

    Link attachments on an issue (pull requests, tickets, documents, URLs).

  • Attach link to issueDestinationProvider duplicate protectionApproval before production

    Attaches a URL to an issue. Linear treats the URL as unique per issue, so repeating it updates the same attachment.

comments3
  • Add issue commentDestinationProvider duplicate protectionApproval before production

    Adds a Markdown comment to an issue.

  • List issue commentsSource

    Comments on an issue.

  • Edit commentDestinationProvider duplicate protectionApproval before production

    Replaces the body of a comment.

customer requests2
  • Create customer requestDestinationProvider duplicate protectionApproval before production

    Records a customer request on an issue or project, linked to a customer by ID or your external ID.

  • List customer requestsSourceIncremental

    Customer requests (customer needs) linked to issues or projects.

customers2
  • List customersSourceIncremental

    Customers tracked for customer requests.

  • Upsert customerDestinationProvider duplicate protectionApproval before production

    Creates or updates a customer matched by your external ID (customerUpsert).

cycles2
  • Get cycleSource

    Reads one cycle with its dates, progress and state flags.

  • List cyclesSource

    Team cycles (sprints) with dates and progress.

initiatives3
  • Create initiativeDestinationProvider duplicate protectionApproval before production

    Creates an initiative.

  • List initiativesSourceIncremental

    Initiatives (groups of projects) with status, owner and target date.

  • Update initiativeDestinationProvider duplicate protectionApproval before production

    Updates an initiative's name, description, owner, status or target date.

issue relations1
  • Relate issues (dependency)DestinationNot retried automaticallyApproval before production

    Creates a blocks, related or duplicate relation between two issues.

issues5
  • Create issue or sub-issueDestinationProvider duplicate protectionApproval before production

    Creates an issue for a team; supply a parent ID to create a sub-issue.

  • Get issueSource

    Reads one issue by ID or identifier (ENG-42) with team, cycle, milestone and labels.

  • List team issuesSourceIncremental

    Issues for a team, optionally updated since a timestamp.

  • Search issuesSourceIncremental

    Finds issues by full-text term and/or structured filters (team, state type, assignee, project, cycle, label, priority, updated or created since).

  • Update issueDestinationProvider duplicate protectionApproval before production

    Updates supplied fields on an issue, including state, cycle, project and labels.

labels3
  • Create labelDestinationProvider duplicate protectionApproval before production

    Creates a workspace or team label, optionally inside a label group.

  • List labelsSource

    Issue labels and label groups, workspace-wide or for one team.

  • Update labelDestinationProvider duplicate protectionApproval before production

    Renames, recolours or regroups a label.

project milestones3
  • Create project milestoneDestinationProvider duplicate protectionApproval before production

    Adds a milestone to a project.

  • List project milestonesSource

    Milestones, optionally for one project.

  • Update project milestoneDestinationProvider duplicate protectionApproval before production

    Renames, re-dates or moves a milestone.

project updates2
  • Post project updateDestinationProvider duplicate protectionApproval before production

    Posts a project status update with health.

  • List project updatesSourceIncremental

    Project status updates (health and narrative), optionally for one project.

projects4
  • Create projectDestinationProvider duplicate protectionApproval before production

    Creates a project for one or more teams.

  • Get projectSource

    Reads one project with status, health, lead, teams and dates.

  • List projectsSource

    Projects with status, lead, dates and progress.

  • Update projectDestinationProvider duplicate protectionApproval before production

    Updates a project's name, description, lead, status, priority or dates.

teams2
  • Get teamSource

    Reads one team with cycle settings, triage and issue counts.

  • List teamsSource

    Teams the API key can access.

users2
  • Get userSource

    Reads one member with role flags and time zone.

  • List usersSource

    Workspace members for assignee mapping.

workflow states3
  • Create workflow stateDestinationProvider duplicate protectionApproval before production

    Adds a workflow state (status) to a team.

  • List workflow statesSource

    Workflow states per team, for status mapping.

  • Update workflow stateDestinationProvider duplicate protectionApproval before production

    Renames, recolours or repositions a workflow state.

Access and limits

Authentication
Personal API key
Plans and access
All Linear plans; initiatives and customer requests need Business or Enterprise. API keys act as the creating member; key permissions can be scoped to teams.
Test environment
Use a free Linear workspace for testing.
Rate limits
2,500 requests and 3,000,000 complexity points per hour per API key, and at most 10,000 points per query; RATELIMITED errors (HTTP 400) when exceeded.
Pagination
Relay cursors (first/after) with up to 100 nodes per page (50 for issue search).
Provider events
Workspace webhooks signed with Linear-Signature HMAC-SHA256. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.

Before you build a flow

  • Issue and comment creation send a deterministic client ID derived from the Nexra idempotency key; a repeat is rejected by Linear instead of creating a duplicate. Projects, milestones, labels, workflow states, project updates, initiatives and customer requests use the same scheme.
  • Attachments are links: Linear treats the URL as unique per issue, so attaching the same URL again updates it. File uploads are not implemented.
  • Initiatives and customer requests require a Linear plan that includes them; other plans return a permission error.
  • Cycles are read-only (cycleCreate is deprecated; cycles are scheduled by team settings).
  • Intentionally excluded: archiving, trashing or deleting issues, projects, milestones, labels, comments, attachments, initiatives and customers; team creation and settings; webhooks.

Developer reference

  1. Create the Linear Orbit, Inc. credentials described above with the narrowest permissions your flows need.
  2. In Nexra, open Connect, then Connections, then New connection, choose Linear, enter its settings and credentials, and tick only the write actions you need. Connection guide
  3. Test the connection, then use its actions as flow sources and destinations. Flow guide
Linear Orbit, Inc. docsAPI referenceLinear Orbit, Inc. docsAuthenticationLinear Orbit, Inc. docsRate limitsLinear Orbit, Inc. docsWebhooks

Machine-readable detail: GET /api/public/connect/connectors/linear and the Connections API.