Linear

Read and write Linear teams, projects, issues, sub-issues, relations and comments.

Route customer and operations signals into engineering work with traceable outcomes.

Build a flow with Linear Provider API documentation

Source actions

Destination actions

Data types

Validation status

Implemented · fixture tested.

Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.

What you can map

comments

Add issue comment
Destination
Duplicate protected
Adds a Markdown comment to an issue.
List issue comments
Source
Comments on an issue.

cycles

List cycles
Source
Team cycles (sprints) with dates and progress.

issue relations

Relate issues (dependency)
Destination
Not retried automatically
Creates a blocks, related or duplicate relation between two issues.

issues

Create issue or sub-issue
Destination
Duplicate protected
Creates an issue for a team; supply a parent ID to create a sub-issue.
List team issues
Source
Incremental
Issues for a team, optionally updated since a timestamp.
Update issue
Destination
Duplicate protected
Updates supplied fields on an issue.

projects

List projects
Source
Projects with status, lead, dates and progress.

teams

List teams
Source
Teams the API key can access.

users

List users
Source
Workspace members for assignee mapping.

workflow states

List workflow states
Source
Workflow states per team, for status mapping.

Authentication

Personal API key

Plans and access

All Linear plans. 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

Request and complexity budgets per hour per key; RATELIMITED errors when exceeded.

Provider events

Workspace webhooks signed with Linear-Signature HMAC-SHA256. Nexra event triggers are not yet available; flows run on demand or on a schedule.

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.