- Category: project management
- Auth: OAUTH2, API_KEY
- Composio-managed OAuth available? Yes
- Tools: 48
- Triggers: 12
- Slug:
LINEAR - Version: 20261101_00
Tools
Archive issue
Archive issue
LINEAR_ARCHIVE_ISSUEArchives an existing Linear issue by its UUID or shorthand identifier, removing it from active views while preserving its data for future reference.Input Parameters
Output
Archive Project
Archive Project
LINEAR_ARCHIVE_PROJECTArchives an existing Linear project by its UUID, removing it from active views. Use this action when you need to mark a completed or obsolete project as archived. Archiving is reversible (projects can be unarchived later), but confirm the project name with the user before executing, especially in bulk operations.Input Parameters
Output
Archive Project Update
Archive Project Update
LINEAR_ARCHIVE_PROJECT_UPDATEArchives a project update in Linear, hiding it from the default view while preserving its data. Use this action when you need to clean up old or obsolete project status updates without permanently deleting them. Archived updates can be unarchived later if needed. This action is irreversible only in the sense that the project update will be hidden from active views until explicitly unarchived.Input Parameters
Output
Create attachment
Create attachment
LINEAR_CREATE_ATTACHMENTCreates a new attachment and associates it with a specific, existing Linear issue.Input Parameters
Output
Add reaction to comment
Add reaction to comment
Create a comment
Create a comment
LINEAR_CREATE_LINEAR_COMMENTCreates a new comment on a specified Linear issue. This action modifies shared workspace data and is not reversible — confirm the target issue and comment content before executing.Input Parameters
Output
Create linear issue
Create linear issue
LINEAR_CREATE_LINEAR_ISSUECreates an issue in a specified Linear team with a title and optional project, description, assignee, state, priority, cycle, due date, and other properties. Returns the created issue’s ID and URL.Input Parameters
Output
Create issue relation
Create issue relation
LINEAR_CREATE_LINEAR_ISSUE_RELATIONCreate a relationship between two Linear issues using the issueRelationCreate mutation. Use this to establish connections like ‘blocks’, ‘duplicate’, or ‘related’ between issues.Input Parameters
Output
Create a label
Create a label
Create Project
Create Project
LINEAR_CREATE_LINEAR_PROJECTCreates a new Linear project with specified name and team associations.Input Parameters
Output
Create Project Milestone
Create Project Milestone
LINEAR_CREATE_PROJECT_MILESTONETool to create a project milestone in Linear with a name and optional target date and sort order. Use when you need to add milestones to track progress within a project.Input Parameters
Output
Create Project Update
Create Project Update
LINEAR_CREATE_PROJECT_UPDATETool to create a project status update post for a Linear project. Use when you need to post progress updates, status reports, or announcements for a project.Input Parameters
Output
Create Team
Create Team
LINEAR_CREATE_TEAMCreates a new team in Linear with the specified name and key. Use this action when you need to create a new organizational unit or work group in a Linear workspace. Teams are fundamental organizational structures in Linear that group issues, projects, and members together. Once created, the team’s key becomes the prefix for all issues created within that team (e.g., ‘ENG-123’). IMPORTANT: The key must be unique across the workspace and cannot be changed after creation.Input Parameters
Output
Delete issue
Delete issue
LINEAR_DELETE_LINEAR_ISSUEArchives an existing Linear issue by its ID, which is Linear’s standard way of deleting issues; the operation is idempotent. Archiving is permanent with no built-in undo — confirm the issue identifier and title with the user before executing, especially in bulk operations.Input Parameters
Output
Get all teams (Deprecated)
Get all teams (Deprecated)
LINEAR_GET_ALL_LINEAR_TEAMSDEPRECATED: Use ListLinearTeams instead (returns paginated payloads with members and projects); this tool returns simpler id/name-level data for all teams visible to the connected workspace with no server-side filtering. Match teams on stable team id, not display name, as names are not guaranteed unique. Partial results reflect workspace permission scope, not tool failure. Skip this call if team_id values are already known.Input Parameters
endCursor from the previous response’s page_info to fetch the next page.Output
Download issue files
Download issue files
LINEAR_GET_ATTACHMENTDownloads a Linear Attachment record or a private upload embedded in issue/comment Markdown; file_name must include the correct extension.Input Parameters
attachment_id; omit when using upload_url.https://uploads.linear.app/... URL embedded in an issue description or comment body. Use this to download inline screenshots and other uploaded files that are not present in the issue’s attachments list.issue_id; omit when using upload_url.Output
Get a comment
Get a comment
LINEAR_GET_COMMENTRetrieves a single Linear comment by its unique ID. Returns comprehensive details including the comment body, author, timestamps, associated issue, and thread information. Use this action when you need to fetch details about a specific comment, such as when displaying comment information, checking comment status, or retrieving comment content for processing. The comment ID can be obtained from issue queries, comment lists, or comment creation responses.Input Parameters
Output
Get current user
Get current user
Get cycles by team ID
Get cycles by team ID
LINEAR_GET_CYCLES_BY_TEAM_IDLists cycles for a specified Linear team ID, including progress, creation and end times, and history. Results are paginated; follow page_info cursors to retrieve subsequent pages.Input Parameters
endCursor value from the previous response’s page_info to fetch the next page.after to paginate through all cycles.Output
Get create issue default params
Get create issue default params
Get Linear issue
Get Linear issue
LINEAR_GET_LINEAR_ISSUERetrieves a Linear issue by UUID or shorthand identifier, including its details, parent, cycle, attachments, comments and subscribers. Optional related fields may be null; certain issue-not-found errors return a null issue with an explanatory message.Input Parameters
Output
Get Linear project
Get Linear project
Get Project Update
Get Project Update
LINEAR_GET_PROJECT_UPDATERetrieves a specific project update by its unique identifier. Use when you need to fetch details about a specific project status update, including the update content, health status, timestamps, and associated project information. This action is useful when verifying a newly created project update or retrieving historical project update information.Input Parameters
Output
List comments
List comments
LINEAR_LIST_COMMENTSLists comments from Linear workspace accessible to the authenticated user. Use this action when you need to retrieve comments for analysis, reporting, or tracking discussions across issues. The response includes comment content, timestamps, author information, and associated issue details. Supports pagination for large result sets.Input Parameters
Output
List issue drafts
List issue drafts
List issues by team ID
List issues by team ID
LINEAR_LIST_ISSUES_BY_TEAM_IDTool to list all issues for a specific Linear team, scoped by team ID. Use when you need to retrieve issues belonging to a particular team without fetching workspace-wide issues. This is more efficient than workspace-wide listing followed by client-side filtering.Input Parameters
end_cursor value from a previous response’s page_info. Cannot use issue IDs, UUIDs, or arbitrary strings. Omit for the first page.Output
Get all cycles
Get all cycles
LINEAR_LIST_LINEAR_CYCLESLists cycles across the Linear account without filters, including team IDs and scheduled end times. Results are paginated; use page_info.endCursor and hasNextPage to retrieve subsequent pages.Input Parameters
endCursor from the previous response’s page_info to fetch the next page.Output
List Linear issues
List Linear issues
LINEAR_LIST_LINEAR_ISSUESLists non-archived Linear issues with optional project and assignee filters, returning a paginated issues array and page_info. Issues include due dates; optional transition history includes completion timestamps and may be truncated or report per-issue errors.Input Parameters
endCursor value from the previous response’s page_info to fetch the next set of issues. Do not modify, prefix, or transform the cursor value in any way.first is internally capped at 25 and values above 50 return a structured error.Output
Get labels
Get labels
LINEAR_LIST_LINEAR_LABELSRetrieves paginated Linear issue labels for a specified team or across the workspace. Use page_info.hasNextPage and page_info.endCursor to fetch further pages.Input Parameters
endCursor value from the previous response’s page_info to fetch the next page.after to paginate through all labels.Output
List linear projects
List linear projects
LINEAR_LIST_LINEAR_PROJECTSRetrieves all projects from the Linear account. Returns a flat array (not a GraphQL connection) with fields id and name; use LINEAR_RUN_QUERY_OR_MUTATION for progress, state, issues, or team linkage. No server-side filtering: all workspace projects are returned regardless of team or name — filter client-side. Multiple projects can share identical names; always confirm project_id before downstream use. Results are permission-scoped to the connected user. Pagination: loop while page_info.hasNextPage is true, passing page_info.endCursor as after, or results will be silently truncated. HTTP 429 may occur in large workspaces; apply exponential backoff between calls.Input Parameters
endCursor from the previous response’s page_info to fetch the next page.Output
List Linear states
List Linear states
LINEAR_LIST_LINEAR_STATESRetrieves all workflow states for a specified team in Linear, representing the stages an issue progresses through in that team’s workflow. Returned state IDs are team-scoped — never reuse a stateId across different teams, as this causes validation errors or ‘Entity not found’ failures in tools like LINEAR_UPDATE_ISSUE. State names (e.g., ‘Done’, ‘In Progress’) are non-unique across teams; always resolve names to IDs via this tool for the specific team_id before using them in filters or mutations. Uses cursor-based pagination via pageInfo.hasNextPage and endCursor; iterate until hasNextPage is false to avoid missing states in large workspaces. Always fetch fresh state IDs rather than hardcoding or reusing stale values.Input Parameters
endCursor value from the previous response’s page_info to fetch the next page.after to paginate through all states.Output
Get teams
Get teams
LINEAR_LIST_LINEAR_TEAMSLists visible Linear teams with their members and project IDs, with pagination for teams but not nested members or projects. An optional project ID filters each team’s projects rather than the teams themselves.Input Parameters
endCursor value from the previous response’s page_info to fetch the next page.after to paginate through all teams.Output
List Linear users
List Linear users
LINEAR_LIST_LINEAR_USERSLists workspace users with IDs, names, emails, and active status. Results are paginated; use the returned cursor to retrieve subsequent pages.Input Parameters
endCursor from the previous response’s page_info to fetch the next set of users.page_info.hasNextPage and paginate using after; omitting pagination silently drops users beyond this limit.Output
List project updates
List project updates
LINEAR_LIST_PROJECT_UPDATESRetrieves all project updates from the Linear workspace. Project updates are status posts written by team members to communicate project progress, blockers, and health. Use when you need to fetch project update history, track project health over time, or review team communication. Returns a paginated list with fields including id, body, health, createdAt, url, user, and project. Results are permission-scoped to the connected user — only updates from accessible projects are returned. Pagination: loop while page_info.hasNextPage is true, passing page_info.endCursor as after, or results will be silently truncated. HTTP 429 may occur in large workspaces; apply exponential backoff between calls.Input Parameters
endCursor from the previous response’s page_info to fetch the next page.after to paginate through all updates.Output
Remove label from Linear issue
Remove label from Linear issue
LINEAR_REMOVE_ISSUE_LABELRemoves a specified label from a Linear issue using the issue and label IDs, and returns the updated issue and labels. If the label is absent, the label set is unchanged. The operation replaces the fetched label set, so concurrent label changes may be overwritten.Input Parameters
Output
Remove reaction from comment
Remove reaction from comment
Resolve comment
Resolve comment
LINEAR_RESOLVE_COMMENTMarks a Linear comment as resolved. This action is used when a comment thread or discussion has been addressed and should be marked as complete. Use this action when you need to resolve a comment after addressing the feedback or discussion it represents. The comment remains visible but is marked as resolved with a timestamp and the resolving user’s information.Input Parameters
Output
Run Query or Mutation
Run Query or Mutation
LINEAR_RUN_QUERY_OR_MUTATIONExecute a Linear GraphQL query or mutation to retrieve or change accessible data. Use it for custom filtering, schema introspection, or operations without a dedicated action. When an operation partially succeeds, the response can include both data and errors.Input Parameters
Output
Search Linear issues
Search Linear issues
LINEAR_SEARCH_ISSUESSearches Linear issues by full-text query, with pagination and an option to include archived issues.Input Parameters
Output
Unarchive Project Update
Unarchive Project Update
LINEAR_UNARCHIVE_PROJECT_UPDATEUnarchive a previously archived project update in Linear. Use this action when you need to restore an archived project update to make it visible and active again. Archived project updates are hidden from normal views but can be restored using this action. Use when a project update was archived by mistake or needs to be brought back into active use.Input Parameters
Output
Unresolve a comment
Unresolve a comment
LINEAR_UNRESOLVE_COMMENTUnresolves a previously resolved Linear comment, marking it as requiring attention again. Use this action when you need to reopen a comment thread that was previously marked as resolved. This is useful when additional discussion is needed or the resolution was premature.Input Parameters
Output
Update issue
Update issue
LINEAR_UPDATE_ISSUEUpdates an existing Linear issue by ID, requiring at least one field to modify; supplied fields overwrite existing values and labels replace the label set. A team move combined with a state, project, or cycle update runs in two phases, so an error may leave the first phase applied.Input Parameters
Output
Update a comment
Update a comment
Update Project
Update Project
LINEAR_UPDATE_LINEAR_PROJECTTool to update an existing Linear project. Use when you need to modify project properties like name, description, state, dates, or lead. All fields except project_id are optional - only provide the fields you want to update.Input Parameters
Output
Update Project Update
Update Project Update
LINEAR_UPDATE_PROJECT_UPDATETool to update an existing Linear project update post. Use this action when you need to modify a project update’s content, health status, or diff visibility settings. All fields except the update ID are optional - only provide the fields you want to update. Changes are immediately visible to all team members viewing the project.Input Parameters
Output
Update Team
Update Team
LINEAR_UPDATE_TEAMUpdates an existing Linear team’s settings, including its name, key, cycle settings, and workflow state configuration. At least one update field must be provided.Input Parameters
Output
Validate credential
Validate credential
LINEAR_VALIDATE_CREDENTIALValidates the Linear API credentials by checking if the authentication token can successfully query the current user. Use this action when you need to verify that API credentials are valid before performing other operations, or to confirm that authentication is working correctly. This is particularly useful for connection testing, credential verification flows, or troubleshooting authentication issues.Output
Triggers
Comment Received Trigger
Comment Received Trigger
Issue Created Trigger
Issue Created Trigger
Issue Updated Trigger
Issue Updated Trigger
Private Team Comment Created
Private Team Comment Created
LINEAR_PRIVATE_TEAM_COMMENT_CREATEDType: pollFires when a new comment is posted on an issue in a private Linear team (polled with the connected user’s token).Configuration
LINEAR_LIST_LINEAR_TEAMS to discover valid team UUIDs.Payload
Comment.parent is itself a full Comment type (carries body, user, createdAt, …); we only query id today because that’s what current customer use-cases need. Kept as a relation object — not flattened to a scalar — so a future need to surface the parent’s body or author can extend this class + _TEAM_COMMENTS_QUERY without breaking the canonical model.Private Team Issue Created
Private Team Issue Created
LINEAR_PRIVATE_TEAM_ISSUE_CREATEDType: pollFires when a new issue appears in a private Linear team (polled with the connected user’s token).Configuration
LINEAR_LIST_LINEAR_TEAMS to discover valid team UUIDs.Payload
Private Team Issue Properties Updated
Private Team Issue Properties Updated
LINEAR_PRIVATE_TEAM_ISSUE_PROPERTIES_UPDATEDType: pollFires when properties on an issue change in a private Linear team (polled with the connected user’s token).Configuration
LINEAR_LIST_LINEAR_TEAMS to discover valid team UUIDs.Payload
Project Created
Project Created
Project Properties Updated
Project Properties Updated
LINEAR_PROJECT_PROPERTIES_UPDATEDType: pollFires when properties on a Linear project change (status, lead, target date, priority, etc.). Covers projects in both public and private teams — polls with the connected user’s token.Configuration
LINEAR_LIST_LINEAR_PROJECTS to discover valid project UUIDs.Payload
Project Update Posted
Project Update Posted
LINEAR_PROJECT_UPDATE_POSTEDType: pollFires when a project status update is posted on the Linear project’s Updates tab. Covers projects in both public and private teams — polls with the connected user’s token.Configuration
LINEAR_LIST_LINEAR_PROJECTS to discover valid project UUIDs.Payload
Public Team Comment Created
Public Team Comment Created
LINEAR_PUBLIC_TEAM_COMMENT_CREATEDType: webhookFires when a new comment is posted on a public-team Linear issue. For private teams (lock icon in Linear’s sidebar) use LINEAR_PRIVATE_TEAM_COMMENT_CREATED.Configuration
LINEAR_LIST_LINEAR_TEAMS to discover valid team UUIDs.Payload
Public Team Issue Created
Public Team Issue Created
LINEAR_PUBLIC_TEAM_ISSUE_CREATEDType: webhookFires when a new issue is created in a Linear public team. For private teams (lock icon in Linear’s sidebar) use LINEAR_PRIVATE_TEAM_ISSUE_CREATED.Configuration
LINEAR_LIST_LINEAR_TEAMS to discover valid team UUIDs.Payload
Public Team Issue Properties Updated
Public Team Issue Properties Updated
LINEAR_PUBLIC_TEAM_ISSUE_PROPERTIES_UPDATEDType: webhookFires when properties on a public-team Linear issue change (status, assignee, priority, labels, etc.). For private teams (lock icon in Linear’s sidebar) use LINEAR_PRIVATE_TEAM_ISSUE_PROPERTIES_UPDATED.Configuration
LINEAR_LIST_LINEAR_TEAMS to discover valid team UUIDs.
LINEAR_COMMENT_EVENT_TRIGGERType: webhookTriggered when a comment is received.Configuration
Payload