Linear

Manage issues, projects, comments, teams, users, workflow states, and labels over Linear's GraphQL API, and react in real time to Linear events. Turn tickets, alerts, and form submissions into tracked work.

1 trigger 16 actions available

A monitoring alert arrives that looks like it should become a Linear issue

Agent reads the alert details and the affected component

Agent runs Search Issues to see whether a matching open issue already exists

Agent posts a comment on the existing issue if it finds a match

Agent posts a summary and a proposed new issue to the triage channel when it finds no clear match

A triage lead confirms whether to open a new issue; the agent only calls Create Issue after confirmation

What This Integration Enables

FlowRunner agents use Linear to connect the backlog to the systems that feed it and depend on it. An agent can create issues from form submissions, support tickets, or monitoring alerts, keep status, assignee, and labels in sync as work progresses, post Markdown comments to relay updates, and search and report across the workspace for digests. The On Linear Event trigger lets a workflow react the moment an issue, comment, project, or label changes. Delete Issue archives rather than hard-deletes, so nothing is truly lost. The agent's discipline is to check for an existing issue before it creates a new one, and to ask when the match is unclear.

Without FlowRunner

Duplicate issues Every alert opens a fresh issue, so the backlog fills with repeats

Manual dedup Someone scans the backlog to find and merge the duplicates later

Stale status External systems never learn when an issue moves to Done

With FlowRunner

Dedup before create The agent searches for a match before it proposes a new issue

Human on the ambiguous ones A person confirms the borderline cases instead of the agent guessing

Two-way sync Status changes flow back out to stakeholders as issues progress

Use Case Scenarios

Alert-to-issue with a dedup gate

A monitoring alert arrives. Before creating anything, the agent runs Search Issues against the affected component. If it finds an open match, it posts a comment on that issue with the new occurrence instead of opening a duplicate. If it finds no clear match, it posts a proposed new issue to the triage channel and waits. A triage lead confirms, and only then does the agent call Create Issue. The backlog reflects real, distinct work.

Bulk backlog import

A workflow reads a backlog of tasks from a spreadsheet or planning doc. For each row, the agent calls Create Issue on the right team, sets priority using Linear's numeric scale, and assigns an owner. A planning session's output becomes tracked work without anyone retyping it.

Status change notifications

When On Linear Event reports an issue moving to a Done state, the agent notifies the original requester that their request is complete and updates any external tracker. Stakeholders learn when work finishes without checking Linear themselves.

Human-in-Loop Highlight

The human-in-loop moment in Linear is the create gate on ambiguous alerts. The agent's default is to avoid duplicates, so it always searches before it creates. When Search Issues returns a clear match, it comments and moves on with no human involved. When the match is uncertain, it stops. It posts the alert and a proposed issue to the triage channel and asks: "This alert may match issue ENG-412 or may be new. Open a new issue, or comment on ENG-412?" A triage lead decides. The agent handles the clear cases on its own. A person resolves the ones where opening the wrong issue would either lose the signal or clutter the board.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

16 actions

Issues

Create Comment Post a Markdown comment on an issue. Used to relay an update or a new occurrence.
Create Issue Create an issue on a team, with title, description, assignee, priority, workflow state, and labels. Used to turn an alert, ticket, or form into tracked work.
Delete Issue Archive an issue. Linear archives rather than hard-deletes, so the issue can be restored from Linear.
Get Issue Retrieve a single issue.
List Issues List issues for a team or project.
Update Issue Update an issue's status, assignee, priority, or labels.

Search

Search Issues Search issues across the workspace. Used to check for an existing match before creating a new issue.

Projects

Create Project Create a project.
List Projects List the projects in the workspace.
Update Project Update a project's details.

Teams

Get Team Retrieve a single team.
List Teams List the teams in the workspace.

Users

Get Viewer Return the authenticated user, the API key owner. Used as a connection check or to resolve the acting identity.
List Users List the users in the workspace.

Workflow States

List Workflow States List a team's workflow states. Used to map a friendly status name to its state before an Update Issue.

Labels

List Labels List the labels available in the workspace. Used to resolve label names before tagging an issue.

Triggers

1 triggers

Event Triggers

On Linear Event A realtime webhook trigger that fires on create, update, and remove events for a chosen resource (Issues, Comments, Projects, or Issue Labels), optionally scoped to one team. Starts a workflow the moment work changes state.

Start building with Linear

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us