# Linear integrations

> Call the Linear API from any Tray.ai workflow with the HTTP Connector.

**Canonical page:** https://tray.ai/connectors/linear-integrations/
**Categories:** Operations
**Connects through:** HTTP Connector

## Overview

Linear is an issue tracker and project planner for software teams, covering issues, projects, cycles, and initiatives. Tray.ai connects to Linear through the HTTP Connector, so your workflows can call the Linear API alongside the rest of your stack.

## Use cases

### Issues

Read, create, and update issues in Linear from any Tray.ai workflow. The Linear API covers calls such as get an issue and create an issue.

- Get an issue
- Create an issue
- Update an issue

### Teams

Read teams in Linear from any Tray.ai workflow. The Linear API covers calls such as list teams and get a team.

- List teams
- Get a team

### Users

Read users in Linear from any Tray.ai workflow. The Linear API covers calls such as list users and get a user.

- List users
- Get a user

### Workflow states

Read workflow states in Linear from any Tray.ai workflow. The Linear API covers calls such as list workflow states and get a workflow state.

- List workflow states
- Get a workflow state

### Linear events

Start a Tray.ai workflow the moment something happens in Linear. Linear sends events such as issue created and issue updated to a Tray.ai webhook trigger.

- Issue created
- Issue updated
- Issue removed

## Challenges Tray.ai solves

### Keeping Linear credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Linear credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Linear API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Linear API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Linear?

Yes. Tray.ai connects to Linear through the HTTP Connector, which calls the Linear API directly. Any call the Linear API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Linear?

The Linear API uses an API key in a request header and OAuth 2.0. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Linear connector?

Linear runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Linear connector from the Linear API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/