Short answer: Drop the "Linear → Get Issue" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Issue ID issueId | string | Required | The Linear issue UUID or identifier (e.g. ENG-123) |
{"issueId": "e.g. ENG-123"}
{"data": {"issue": {"id": "uuid","url": "https://linear.app/team/issue/ENG-123","state": {"name": "In Progress"},"title": "Fix payment flow","labels": {"nodes": [{"name": "bug"}]},"project": {"name": "Q1 Launch"},"assignee": {"name": "John Doe","email": "john@example.com"},"priority": 2,"identifier": "ENG-123","description": "The checkout page crashes on mobile","priorityLabel": "High"}}}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.