Short answer: Drop the "Linear → Comment Created" 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.
{"url": "https://linear.app/.../comments/c-1","body": "TC test comment","type": "Comment","action": "create","user_id": "user-id","actor_id": "user-id","issue_id": "abc-123","edited_at": null,"parent_id": null,"actor_name": "Test","comment_id": "c-1","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","organization_id": "org"}
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/.../comments/c-1" |
| body | string | "TC test comment" |
| type | string | "Comment" |
| action | string | "create" |
| user_id | string | "user-id" |
| actor_id | string | "user-id" |
| issue_id | string | "abc-123" |
| edited_at | null | null |
| parent_id | null | null |
| actor_name | string | "Test" |
| comment_id | string | "c-1" |
| 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" |
| organization_id | string | "org" |
One trigger. 8+ downstream actions. Zero glue.