- Integrations
- /
- Linear
- /
- Actions
- /
- Add Comment
ActionLinearUpdated May 2026
How do I add a comment to a Linear issue?
Short answer: Drop the "Linear → Add Comment" 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 |
|---|---|---|---|
Issue ID issueId | string | Required | Issue ID. Example: issue-uuid |
Comment body | string | Required | Comment text (supports Markdown) |
Sample request
{"issueId": "e.g. issue-uuid","body": "e.g. Hi there, thanks for reaching out."}
Returns
{"data": {"commentCreate": {"comment": {"id": "uuid","body": "Comment text","createdAt": "2025-01-15T12:00:00.000Z"},"success": true}}}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Add Comment.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Add Comment.
What does the Add Comment action do in Linear?
Adds a comment to a Linear issue with optional Markdown formatting. Used for automation activity logs, AI summary notes, or status broadcasts.
What inputs does Add Comment require?
Required: Issue ID, Comment. 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 Add Comment support batch operations?
Yes. Run Add Comment 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
Create Issue
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.
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 add comment from your workflows.
Triggered by anything in the catalog. Free tier available. No credit card.