- Integrations
- /
- Linear
- /
- Triggers
- /
- Issue Updated
TriggerLinearReal-timeUpdated May 2026
How do I trigger when a Linear issue status changes?
Short answer: Drop the "Linear → Issue Updated" trigger on your workflow canvas, add filters if you want them, and publish. It fires within seconds of the event in Linear, not on a polling schedule.
Anatomy
What this trigger looks like in a workflow.
Drop it on the canvas. Configure a couple of fields. Publish.
In the builder
Trigger
Issue Updated
When the matching event happens
when an issue status is changed in linearissue changedon issue updatednew issue updatedwhen issue updatedwatch for issue updatedissue modified
What this trigger returns
for the curiousYou don’t need to read this. Tiny Command auto-maps every field into the visual picker so downstream nodes can pull values by clicking. We show it here for power users who want to know what’s on the wire.
{"url": "https://linear.app/tc/issue/ENG-42","type": "Issue","title": "TC test issue","action": "update","team_id": "team-id","actor_id": "user-id","issue_id": "abc-123","priority": 0,"state_id": "state-id","label_ids": [],"actor_name": "Test User","created_at": "2026-04-11T10:00:00.000Z","creator_id": "user-id","identifier": "ENG-42","project_id": null,"state_name": "Backlog","state_type": "backlog","updated_at": "2026-04-11T10:00:00.000Z","actor_email": "tester@example.com","assignee_id": null,"description": null,"occurred_at": "2026-04-11T10:00:00.000Z","updated_from": {"title": "Old title"},"priority_label": "No priority","subscriber_ids": ["user-id"],"organization_id": "org-id"}
Output shape
Fields available to downstream nodes.
Every field below can be referenced by name in any action or filter that comes after this trigger.
| Field | Type | Example |
|---|---|---|
| url | string | "https://linear.app/tc/issue/ENG-42" |
| type | string | "Issue" |
| title | string | "TC test issue" |
| action | string | "update" |
| team_id | string | "team-id" |
| actor_id | string | "user-id" |
| issue_id | string | "abc-123" |
| priority | number | 0 |
| state_id | string | "state-id" |
| label_ids | array | [] |
| actor_name | string | "Test User" |
| created_at | string | "2026-04-11T10:00:00.000Z" |
| creator_id | string | "user-id" |
| identifier | string | "ENG-42" |
| project_id | null | null |
| state_name | string | "Backlog" |
| state_type | string | "backlog" |
| updated_at | string | "2026-04-11T10:00:00.000Z" |
| actor_email | string | "tester@example.com" |
| assignee_id | null | null |
| description | null | null |
| occurred_at | string | "2026-04-11T10:00:00.000Z" |
| updated_from | object | { … } |
| updated_from.title | string | "Old title" |
| priority_label | string | "No priority" |
| subscriber_ids | array | ["user-id"] |
| organization_id | string | "org-id" |
Pairs with
Drop these actions after Issue Updated.
FAQ
Questions about Issue Updated.
How does the Issue Updated trigger work in Linear?
Fires when an issue is updated in Linear (status, priority, assignee, estimate, custom fields). Combine with filters to react only to specific transitions.
Is the Issue Updated trigger real-time?
Yes. Issue Updated uses webhooks or push subscriptions, not polling. Your workflow fires within seconds of the event happening in Linear.
What data does Issue Updated return?
The full event payload from Linear. The output shape table on this page lists every field, its type, and an example value so you can map fields into downstream nodes.
Can I filter Issue Updated so only some events start a workflow?
Yes. Add a Filter node right after the trigger and match on any field, whether that's subject, sender, status, or anything else in the payload. Workflows only continue when the filter passes.
Do I need Linear admin permissions to use Issue Updated?
For most Linear accounts a standard user can authorize the trigger. Some Linear plans require an admin to enable third-party webhooks. Check Linear's docs if the trigger fails to register.
More triggers
Other Linear triggers.
Trigger
Comment Created
Fires when a comment is added to a Linear issue. Use to mirror engineering discussion to Slack or to feed AI summaries into a status doc.
TriggerNew Cycle
Fires when a new cycle (sprint) is created in Linear. Use to kick off stand-up bots or to seed a cycle-kickoff doc.
TriggerNew Issue
Fires when a new issue is created in Linear. The standard inbound hook for routing, enrichment, and SLA-aware notifications.
TriggerIssue Deleted
Fires when an issue is deleted in Linear. Useful for audit logs or for tearing down related records in other systems.
TriggerNew Project
Fires when a new project is created in Linear. Use to provision related docs, mirror to a roadmap tool, or notify product.
Build a workflow on this trigger.
One trigger. 8+ downstream actions. Zero glue.