> For the complete documentation index, see [llms.txt](https://agpt.co/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://agpt.co/docs/integrations/block-integrations/comment.md).

# Linear Comment

Blocks for creating and managing comments on Linear issues.

## Linear Create Comment

### What it is

Creates a new comment on a Linear issue

### How it works

This block creates a new comment on a Linear issue using the Linear GraphQL API. Provide the issue ID and comment text, and the block posts the comment and returns its ID.

Comments appear in the issue's activity timeline and notify relevant team members.

### Inputs

| Input     | Description                      | Type | Required |
| --------- | -------------------------------- | ---- | -------- |
| issue\_id | ID of the issue to comment on    | str  | Yes      |
| comment   | Comment text to add to the issue | str  | Yes      |

### Outputs

| Output        | Description                           | Type |
| ------------- | ------------------------------------- | ---- |
| error         | Error message if the operation failed | str  |
| comment\_id   | ID of the created comment             | str  |
| comment\_body | Text content of the created comment   | str  |

### Possible use case

**Automated Updates**: Post status updates or progress reports to issues automatically.

**Integration Comments**: Add comments when external systems (CI/CD, monitoring) detect relevant changes.

**Cross-Tool Communication**: Post comments from chatbots or customer support integrations.

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://agpt.co/docs/integrations/block-integrations/comment.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.