Short answer: Drop the "Linear → Create 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 |
|---|---|---|---|
Team ID teamId | string | Required | The Linear team ID (UUID) |
Title title | string | Required | Title. Example: Fix payment flow |
Description description | string | Optional | Markdown description of the issue |
Priority priority | options | Optional | Priority. Options: No priority, Urgent, High, Medium, Low |
Assignee ID assigneeId | string | Optional | Linear user UUID for the assignee. |
Label IDs labelIds | string | Optional | Comma-separated label UUIDs |
{"teamId": "e.g. abc-123-def","title": "e.g. Fix payment flow","description": "{{trigger.description}}","priority": "{{trigger.priority}}","assigneeId": "e.g. user-uuid"}
{"data": {"issueCreate": {"issue": {"id": "uuid","url": "https://linear.app/team/issue/ENG-123","title": "Fix payment flow","identifier": "ENG-123"},"success": true}}}
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.