> 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/projects.md).

# Linear Projects

Blocks for searching and managing Linear projects.

## Linear Search Projects

### What it is

Searches for projects on Linear

### How it works

This block searches for projects in Linear using a text query. It queries the Linear GraphQL API to find projects matching the search term.

Returns a list of projects with their details for further use in workflows.

### Inputs

| Input | Description                 | Type | Required |
| ----- | --------------------------- | ---- | -------- |
| term  | Term to search for projects | str  | Yes      |

### Outputs

| Output   | Description                           | Type           |
| -------- | ------------------------------------- | -------------- |
| error    | Error message if the operation failed | str            |
| projects | List of projects                      | List\[Project] |

### Possible use case

**Project Discovery**: Find projects by name to use in issue creation or queries.

**Portfolio Overview**: Search for projects to build portfolio dashboards.

**Dynamic Forms**: Populate project dropdowns in custom interfaces.

***


---

# 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/projects.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.