Skip to main content

Documentation Index

Fetch the complete documentation index at: https://explore.airia.com/llms.txt

Use this file to discover all available pages before exploring further.

Linear actions let an agent manage issues in Linear directly in a flow. An agent can create and update issues, read a single issue, and list issues with filters, then pass the results to later steps.

Supported actions

GroupActions
IssueCreate, Update, Get, List

Prerequisites

Generate an API key in your Linear settings, then store it as a Linear credential in Credential Management. Select that credential on every Linear action.

How to use these actions

  • Map text inputs from earlier steps. Inputs such as Title and Description accept a value mapped from a previous step.
  • Pick records from dropdowns. The Team ID, Project ID, Assignee ID, State ID, and Priority fields can be selected from lists loaded from your Linear account.
  • Numbers and toggles take fixed values. The First and Estimate numbers and the Include Archived toggle are entered as fixed values.
  • Labels are comma separated. Provide Label IDs as a comma separated list.
  • Descriptions support markdown. Issue descriptions are written in markdown.
  • Dates use ISO 8601. Enter a Due Date in ISO 8601 format.
  • List results page with a cursor. Pass the After cursor to page through more results.

Actions

Issue

Linear Issue Create

Creates a new issue.
InputRequiredDescription
Team IDYesThe team to create the issue in. Selectable from your account.
TitleYesThe title of the issue.
DescriptionNoThe issue description. Supports markdown.
PriorityNoThe priority of the issue: 0 none, 1 urgent, 2 high, 3 medium, 4 low. Selectable from your account.
Assignee IDNoThe user to assign the issue to. Selectable from your account.
Project IDNoThe project to add the issue to. Selectable from your account.
State IDNoThe workflow state of the issue. Selectable from your account.
Label IDsNoLabels to apply, as a comma separated list.
Due DateNoThe due date in ISO 8601 format.
EstimateNoThe estimate in points. A fixed number.

Linear Issue Update

Updates an existing issue.
InputRequiredDescription
Issue IDYesThe unique identifier of the issue to update.
TitleNoThe new title.
DescriptionNoThe new description. Supports markdown.
PriorityNoThe priority of the issue: 0 none, 1 urgent, 2 high, 3 medium, 4 low. Selectable from your account.
Assignee IDNoThe user to assign the issue to. Selectable from your account.
Project IDNoThe project to move the issue to. Selectable from your account.
State IDNoThe workflow state of the issue. Selectable from your account.
Label IDsNoLabels to apply, as a comma separated list.
Due DateNoThe due date in ISO 8601 format.
EstimateNoThe estimate in points. A fixed number.

Linear Issue Get

Retrieves an issue by ID.
InputRequiredDescription
Issue IDYesThe unique identifier of the issue to retrieve.

Linear Issue List

Lists issues with optional filters.
InputRequiredDescription
Team IDNoFilter by team. Selectable from your account.
Project IDNoFilter by project. Selectable from your account.
Assignee IDNoFilter by assignee. Selectable from your account.
State IDNoFilter by workflow state. Selectable from your account.
FirstNoMaximum number of issues to return, from 1 to 100. A fixed number.
AfterNoPagination cursor. The cursor to start after.
Include ArchivedNoWhether to include archived issues.

Example

An agent that files a bug report from a support ticket:
1

Find the team

A Linear Issue List action filters by Team ID so a model step can confirm the right team before filing.
2

Create the issue

A Linear Issue Create action maps Title and Description from the ticket summary, sets Priority, and selects the Assignee ID for the on call engineer.
3

Confirm

A model step summarizes the created issue, including its returned identifier, for the activity log.

Troubleshooting

Confirm the stored API key is valid and has not been revoked. Generate a new key in Linear and update the credential.
The Issue ID, Team ID, or other identifier does not exist or the key cannot see it. Use the List action to discover valid IDs, then feed them into later steps.
Priority must be one of 0 through 4, and Due Date must be in ISO 8601 format.
For issues common to every vendor, see the Actions overview.