- Integrations
- /
- Linear
- /
- Actions
- /
- Create Issue
ActionLinearUpdated May 2026
How do I create a Linear issue from a workflow?
Short answer: Drop the "Linear → Create Issue" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Inputs
The fields this action accepts.
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 |
Sample request
{"teamId": "e.g. abc-123-def","title": "e.g. Fix payment flow","description": "{{trigger.description}}","priority": "{{trigger.priority}}","assigneeId": "e.g. user-uuid"}
Returns
{"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.
Triggered by
Apps that pair well as the trigger for Create Issue.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Create Issue.
What does the Create Issue action do in Linear?
Creates a new issue in a Linear team with title, description (Markdown), state, priority, assignee, labels, project, and cycle. Standard write for piping external alerts or bug reports into Linear.
What inputs does Create Issue require?
Required: Team ID, Title. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Linear returns an error?
The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.
Does Create Issue support batch operations?
Yes. Run Create Issue inside a Loop node to process arrays. Tiny Command handles Linear's rate limits automatically so you don't have to throttle manually.
More actions
Other Linear actions.
Action
Add Comment
Adds a comment to a Linear issue with optional Markdown formatting. Used for automation activity logs, AI summary notes, or status broadcasts.
ActionGet Issue
Retrieves a single Linear issue by its identifier (e.g. ENG-123) with title, description, state, assignee, project, and labels. The standard read after a trigger fires.
ActionList Issues
Lists recent issues from Linear with filters for team, state, assignee, project, and label. Used for digests, sprint reviews, or warehouse exports.
ActionList Projects
Lists projects in your Linear workspace with name, state, lead, and target date. Used to populate a project picker or for roadmap reporting.
ActionList Teams
Lists all teams in your Linear workspace with key and name. Required first step to get team IDs for creating issues.
ActionSearch Issues
Searches issues in Linear by title or identifier. The right tool for upsert lookups or for finding related work by keyword.
Send create issue from your workflows.
Triggered by anything in the catalog. Free tier available. No credit card.