Short answer: Drop the "Linear → New Project" 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/.../project/p-1","name": "TC project","type": "Project","state": "planned","action": "create","lead_id": null,"actor_id": "user-id","team_ids": ["team-id"],"actor_name": "Test","created_at": "2026-04-11T10:00:00.000Z","creator_id": "user-id","project_id": "p-1","start_date": null,"updated_at": "2026-04-11T10:00:00.000Z","actor_email": "t@x.com","description": null,"occurred_at": "2026-04-11T10:00:00.000Z","target_date": 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 |
|---|---|---|
| url | string | "https://linear.app/.../project/p-1" |
| name | string | "TC project" |
| type | string | "Project" |
| state | string | "planned" |
| action | string | "create" |
| lead_id | null | null |
| actor_id | string | "user-id" |
| team_ids | array | ["team-id"] |
| actor_name | string | "Test" |
| created_at | string | "2026-04-11T10:00:00.000Z" |
| creator_id | string | "user-id" |
| project_id | string | "p-1" |
| start_date | null | null |
| updated_at | string | "2026-04-11T10:00:00.000Z" |
| actor_email | string | "t@x.com" |
| description | null | null |
| occurred_at | string | "2026-04-11T10:00:00.000Z" |
| target_date | null | null |
| organization_id | string | "org" |
One trigger. 8+ downstream actions. Zero glue.