TriggerLinearReal-timeUpdated May 2026
How do I trigger when a new Linear cycle starts?
Short answer: Drop the "Linear → New Cycle" 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
New Cycle
When the matching event happens
when cycle createdon cycle creatednew cycle creatednew cyclewatch for cycle createdwhen a new cycle is created in linearcycle added
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.
{"name": "Cycle 1","type": "Cycle","action": "create","number": 1,"ends_at": "2026-04-18T10:00:00.000Z","team_id": "team-id","actor_id": "user-id","cycle_id": "c-1","starts_at": "2026-04-11T10:00:00.000Z","actor_name": "Test","created_at": "2026-04-11T10:00:00.000Z","updated_at": "2026-04-11T10:00:00.000Z","actor_email": "t@x.com","occurred_at": "2026-04-11T10:00:00.000Z","completed_at": null,"organization_id": "org"}
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 |
|---|---|---|
| name | string | "Cycle 1" |
| type | string | "Cycle" |
| action | string | "create" |
| number | number | 1 |
| ends_at | string | "2026-04-18T10:00:00.000Z" |
| team_id | string | "team-id" |
| actor_id | string | "user-id" |
| cycle_id | string | "c-1" |
| starts_at | string | "2026-04-11T10:00:00.000Z" |
| actor_name | string | "Test" |
| created_at | string | "2026-04-11T10:00:00.000Z" |
| updated_at | string | "2026-04-11T10:00:00.000Z" |
| actor_email | string | "t@x.com" |
| occurred_at | string | "2026-04-11T10:00:00.000Z" |
| completed_at | null | null |
| organization_id | string | "org" |
Pairs with
Drop these actions after New Cycle.
FAQ
Questions about New Cycle.
How does the New Cycle trigger work in Linear?
Fires when a new cycle (sprint) is created in Linear. Use to kick off stand-up bots or to seed a cycle-kickoff doc.
Is the New Cycle trigger real-time?
Yes. New Cycle uses webhooks or push subscriptions, not polling. Your workflow fires within seconds of the event happening in Linear.
What data does New Cycle 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 New Cycle 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 New Cycle?
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 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.
TriggerIssue Updated
Fires when an issue is updated in Linear (status, priority, assignee, estimate, custom fields). Combine with filters to react only to specific transitions.
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.
