- Integrations
- /
- Linear
- /
- Actions
- /
- Update Issue
ActionLinearUpdated May 2026
How do I update a Linear issue?
Short answer: Drop the "Linear → Update Issue" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Inputs
The fields this action accepts.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Issue ID issueId | string | Required | The Linear issue UUID |
Title title | string | Optional | Title |
Description description | string | Optional | Description |
Priority priority | options | Optional | Priority. Options: No priority, Urgent, High, Medium, Low |
State ID stateId | string | Optional | Workflow state UUID (e.g. 'In Progress' state ID) |
Assignee ID assigneeId | string | Optional | Assignee ID. Example: user-uuid |
Sample request
{"issueId": "e.g. issue-uuid","title": "{{trigger.title}}","description": "{{trigger.description}}","priority": "{{trigger.priority}}","stateId": "e.g. state-uuid"}
Returns
{"data": {"issueUpdate": {"issue": {"id": "uuid","state": {"name": "In Progress"},"title": "Updated title","identifier": "ENG-123"},"success": true}}}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Update Issue.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Update Issue.
What does the Update Issue action do in Linear?
Updates fields on an existing Linear issue: title, description, state, priority, assignee, estimate, labels, project, or cycle. Only the fields you pass are changed.
What inputs does Update Issue require?
Required: Issue ID. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Linear returns an error?
The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.
Does Update Issue support batch operations?
Yes. Run Update Issue inside a Loop node to process arrays. Tiny Command handles Linear's rate limits automatically so you don't have to throttle manually.
More actions
Other Linear actions.
Action
Add Comment
Adds a comment to a Linear issue with optional Markdown formatting. Used for automation activity logs, AI summary notes, or status broadcasts.
ActionCreate Issue
Creates a new issue in a Linear team with title, description (Markdown), state, priority, assignee, labels, project, and cycle. Standard write for piping external alerts or bug reports into Linear.
ActionGet Issue
Retrieves a single Linear issue by its identifier (e.g. ENG-123) with title, description, state, assignee, project, and labels. The standard read after a trigger fires.
ActionList Issues
Lists recent issues from Linear with filters for team, state, assignee, project, and label. Used for digests, sprint reviews, or warehouse exports.
ActionList Projects
Lists projects in your Linear workspace with name, state, lead, and target date. Used to populate a project picker or for roadmap reporting.
ActionList Teams
Lists all teams in your Linear workspace with key and name. Required first step to get team IDs for creating issues.
Send update issue from your workflows.
Triggered by anything in the catalog. Free tier available. No credit card.