Skip to content
TriggerLinearReal-timeUpdated May 2026

How do I trigger when a Linear issue status changes?

Short answer: Drop the "LinearIssue 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 curious

You 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.

FieldTypeExample
urlstring"https://linear.app/tc/issue/ENG-42"
typestring"Issue"
titlestring"TC test issue"
actionstring"update"
team_idstring"team-id"
actor_idstring"user-id"
issue_idstring"abc-123"
prioritynumber0
state_idstring"state-id"
label_idsarray[]
actor_namestring"Test User"
created_atstring"2026-04-11T10:00:00.000Z"
creator_idstring"user-id"
identifierstring"ENG-42"
project_idnullnull
state_namestring"Backlog"
state_typestring"backlog"
updated_atstring"2026-04-11T10:00:00.000Z"
actor_emailstring"tester@example.com"
assignee_idnullnull
descriptionnullnull
occurred_atstring"2026-04-11T10:00:00.000Z"
updated_fromobject{ … }
updated_from.titlestring"Old title"
priority_labelstring"No priority"
subscriber_idsarray["user-id"]
organization_idstring"org-id"
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.

Build a workflow on this trigger.

One trigger. 8+ downstream actions. Zero glue.