Add Linear Issue Label
Add an account-bound issue label ref to an account-bound issue ref.
Linear GraphQL provider using daemon-owned OAuth or a personal API key. Credentials stay daemon-held and only curated issue-work actions are executable.
Connection facts
These details come from the current StackOS provider manifest and action catalog. They describe the available connection—not a promise that every workflow will use every action.
Action catalog
Actions listed for this integration. Individual descriptions note availability limits. A workflow still decides which actions belong in the job and where approval is required.
34 matching actions
Add an account-bound issue label ref to an account-bound issue ref.
Archive one issue by an account-bound issue ref.
Create an issue from reviewed fields and account-bound refs.
Create a comment on one account-bound issue with an optional parent comment ref.
Create a reviewed relation between two account-bound issue refs.
Delete one account-bound issue comment; permanent issue deletion is not exposed.
Delete one account-bound issue relation.
Get one issue comment by an account-bound comment ref.
Get one cycle by an account-bound cycle ref.
Get one issue and its reviewed nested context by an account-bound issue ref.
Get one issue label by an account-bound label ref.
Get one issue relation by an account-bound relation ref.
Get one project by an account-bound project ref.
Get one Linear team by an account-bound team ref.
Get one Linear user by an account-bound user ref.
Return the authenticated Linear user and workspace as account-bound safe refs.
Get one workflow state by an account-bound ref.
List cycles with bounded pagination and reviewed team/timestamp filters.
List comments for one account-bound issue with bounded pagination.
List issue labels with bounded pagination and reviewed team/timestamp filters.
List relations from one issue; the workspace-wide relation root is not exposed.
List issues using only bounded pagination and reviewed safe-ref/timestamp filters.
List projects with bounded pagination and reviewed team/timestamp filters.
List Linear teams with bounded cursor pagination and account-bound refs.
List Linear workspace users with bounded pagination.
List workflow states using reviewed team and timestamp filters.
Remove an account-bound issue label ref from an account-bound issue ref.
Resolve one account-bound issue comment.
Search issues through Linear searchIssues with a required term and reviewed filters.
Restore one archived issue by an account-bound issue ref.
Reopen one account-bound issue comment.
Replace the body of one account-bound issue comment.
Patch one issue with reviewed fields while preserving omitted-versus-null semantics.
Change one account-bound relation to a reviewed relation type.
Direct answer
People continue using Linear as their tool. StackOS adds it to a visible workflow, keeps the work in order, and passes only the approved action to the integration when that stage is ready.
Common questions
The current catalog includes 34 Linear actions across Issue Work. The exact actions used depend on the workflow and approval rules.
No. Linear remains the tool that performs its part of the job. StackOS organizes the workflow, keeps status and dependencies visible, and calls the tool only when the plan reaches the right approved action.