Short answer: Drop the "Linear → Update Issue" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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 |
{"issueId": "e.g. issue-uuid","title": "{{trigger.title}}","description": "{{trigger.description}}","priority": "{{trigger.priority}}","stateId": "e.g. state-uuid"}
{"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.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.