Linear

Project Management integration · 12 node(s).

00Overview

Every field below is exactly what you see in the Flomation editor. Fields marked ● live picker let you choose from a list pulled live from your account — no IDs to look up.

01Connecting Linear

Add your credentials as a Flomation environment secret, then pick them in each node. The connection fields are:

Field	Type		Details
Linear API Key	`secret`	Required	lin_api_...

Pick an Environment on your flow (Flow Settings → Environment) so the secret resolves. Secret fields never show the value — they reference ${secrets.your_secret}.

02Add

Add Comment

linear/add_comment · Action

Add a Markdown comment to an existing Linear issue.

Field	Type		Details
Issue ID	`secret`	Required	Issue UUID
Comment Body	`text`	Required	Markdown comment text

Returns: tool_result, comment_id, success, error

03Create

Create Issue

linear/create_issue · Action

Create a new Linear issue. Requires team_id (use List Teams to find it). Returns identifier and URL.

Field	Type		Details
Team ID	`secret`	Required	The team UUID or key (e.g. ENG)
Title	`string`	Required	Issue title
Description	`text`		Markdown description (optional)
Priority	`string`		choices: No Priority, Urgent, High, Medium, Low
Assignee ID	`string`		User UUID (optional)
State ID	`string`		Workflow state UUID (optional, defaults to team backlog)
Label IDs	`string`		Comma-separated label UUIDs (optional)
Project ID	`string`		Project UUID (optional)
Estimate	`integer`		Story points (optional)
Due Date	`string`		YYYY-MM-DD (optional)

Returns: tool_result, issue_id, identifier, url, success, error

04Delete

Delete Comment

linear/delete_comment · Action

Delete a comment from a Linear issue by comment ID.

Field	Type		Details
Comment ID	`string`	Required	Comment UUID

Returns: tool_result, success, error

05Get

Get Comment

linear/get_comment · Action

Retrieve a single Linear comment by ID with full body text.

Field	Type		Details
Comment ID	`string`	Required	Comment UUID

Returns: tool_result, body, author, created_at, issue_id, success, error

Get Issue

linear/get_issue · Action

Fetch a Linear issue by UUID or identifier (e.g. ENG-123). Returns full details.

Field	Type		Details
Issue ID or Identifier	`secret`	Required	UUID or ENG-123

Returns: tool_result, issue_id, identifier, title, description, state, priority, assignee, team, url, due_date, created_at, updated_at, estimate, labels, result, success, error

06List

List Comments

linear/list_comments · Action

List comments on a Linear issue. Returns comment IDs, authors, and body text.

Field	Type		Details
Issue ID	`string`	Required	Issue UUID

Returns: tool_result, comments, count, success, error

List Issues

linear/list_issues · Action

List and filter Linear issues by team, state, assignee, priority, or label.

Field	Type	Details
Team ID	`secret`	Filter by team UUID (optional)
Assignee ID	`string`	Filter by assignee UUID (optional)
State Name	`string`	Filter by state name, e.g. In Progress (optional)
Priority	`string`	choices: Any, Urgent, High, Medium, Low
Label Name	`string`	Filter by label name (optional)
Project ID	`string`	Filter by project UUID (optional)
Limit	`integer`	50

Returns: tool_result, issues, count, success, error

List Teams

linear/list_teams · Action

List all Linear teams with workflow states, labels, and members. Call first to get team_id.

Returns: tool_result, teams, count, success, error

List Users

linear/list_users · Action

List Linear workspace members. Returns user IDs, names, emails, and active status.

Field	Type		Details
Optional: filter by name or email	`secret`

Returns: tool_result, users, count, success, error

List Workflow States

linear/list_workflow_states · Action

List workflow states (e.g. Todo, In Progress, Done, Cancelled) for a team. Use this to get state UUIDs needed by update_issue.

Field	Type		Details
Team ID or Key	`secret`	Required	UUID or team key (e.g. FLO)

Returns: tool_result, states, count, success, error

07Search

Search Issues

linear/search_issues · Action

Full-text search across Linear issues by keyword.

Field	Type		Details
Search Query	`secret`	Required	Search keywords
Limit	`integer`		25

Returns: tool_result, issues, count, success, error

08Update

Update Issue

linear/update_issue · Action

Update a Linear issue. Accepts UUID or identifier (e.g. ENG-123). Omitted fields are unchanged.

Field	Type		Details
Issue ID or Identifier	`secret`	Required	UUID or ENG-123
Title	`string`		New title (optional)
Description	`text`		New description (optional)
Priority	`string`		choices: (unchanged), No Priority, Urgent, High, Medium, Low
State ID (UUID, optional — use state_name instead for convenience)	`string`		Workflow state UUID
State Name (e.g. 'Cancelled', 'In Progress', 'Done' — resolves to UUID automatically)	`string`		State name
Assignee ID	`string`		User UUID (optional)
Project ID	`string`		Project UUID (optional)
Due Date	`string`		YYYY-MM-DD (optional)
Estimate	`string`		Point estimate (optional)
Parent Issue ID	`string`		UUID or identifier of parent issue (optional)
Label IDs	`string`		Comma-separated label UUIDs to set (optional)

Returns: tool_result, issue_id, identifier, url, success, error

09Notes & Limitations

Behaviours and constraints worth knowing before you build with these nodes.

Priority is a number from 0 to 4 where 1 means Urgent and 4 means Low (0 is no priority), so a higher number does not mean more important.
Workflow states and labels are defined per team, so a state or label ID read from one team cannot be applied to an issue that lives in a different team.
An issue's short identifier (e.g. ENG-123) changes if the issue is moved to another team, while its UUID stays fixed — reference the UUID in flows that must survive such moves.
Comment and issue bodies are rendered as Markdown, so characters like # and * are treated as formatting unless escaped.