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.
Drop it on the canvas. Configure a couple of fields. Publish.
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.
{"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"}
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" |
One trigger. 8+ downstream actions. Zero glue.