Skip to main content

Linear Integration

Connect Linear to give Annie visibility into the engineering work behind your infrastructure. During an incident or chat session, Annie can search Linear for related tickets, retrieve issue details, and tie infrastructure changes back to the issues that requested them.

Setup Guide

  1. Go to the Linear integration page.
  2. Click Connect with Linear.
  3. Sign in to Linear (if needed) and authorize Anyshift.
  4. You are redirected back to Anyshift with the workspace connected.
OAuth uses a refreshable access token scoped to your Linear account. You can disconnect at any time from the Anyshift integration page or by revoking Anyshift in Linear’s application settings.

Option B: Personal API key

Use this if you prefer a static key or OAuth is not enabled for your workspace yet.

1. Create a Linear personal API key

  1. In Linear, open Settings → My Account → Security & access → API keys, or jump straight to the creation flow at https://linear.app/<your-workspace>/settings/account/security/api-keys/new.
  2. Give the key a label (e.g. Anyshift / Annie) and click Create key.
  3. Copy the generated API key. Linear only shows it once.
Personal API keys inherit the permissions of the user who created them. For least-privilege access, create the key from an account that has only the workspace access you want Annie to have.

2. Find your workspace URL key

The workspace URL key is the slug in your Linear URL, immediately after linear.app/. For example, if your workspace lives at https://linear.app/acme, your workspace URL key is acme. You can paste the full URL into the Anyshift form. Anyshift strips the linear.app/ prefix and any trailing slash automatically.

3. Connect Linear to Anyshift

  1. Go to the Linear integration page.
  2. Click New credentials.
  3. Fill in the form fields below and click Save.
Display name
A human-readable label for this credential (e.g. Engineering Workspace). Used only to identify the credential in the Anyshift UI.
Workspace URL key
The slug for your Linear workspace (e.g. acme). Pasting the full URL also works.
API key
Paste the personal API key you copied in step 1. Anyshift validates the credentials against Linear’s GraphQL API on save. The credential is stored even if validation fails, so you can fix and retry without re-entering the form.

Required Permissions

Annie performs read-only operations on your Linear workspace. OAuth and personal API keys both grant access based on the permissions of the authorizing user. The Linear user needs access to:
  • View issues
  • View teams and team members
  • View projects
Annie does not create, modify, or delete any issues, comments, or other content in your Linear workspace.

How It Works

Anyshift’s agent gateway authenticates against Linear’s GraphQL API using the OAuth access token or personal API key you provided. Tokens are encrypted at rest (KMS) and only decrypted in-process when Annie makes a Linear call. OAuth credentials are refreshed automatically when they expire. Once connected, Annie’s AI agent can:
  • List filtered issues — Filter by assignee (including “assigned to me”), team, state, or title substring.
  • Search your workspace — Free-text search across issues by title, description, and identifier (not by assignee).
  • Read issues — Retrieve a single issue by identifier (e.g. ENG-42) with its team, state, assignee, labels, description, parent, and project.
  • Browse teams — List teams in the workspace or fetch a specific team by key (e.g. ENG), including members and active issues.
  • Browse projects — List projects in the workspace or fetch a specific project by slug or UUID.
  • Resolve the workspace — Look up the authenticated user (viewer) and their organization to confirm what the credential can see.

Example use cases

  • “What Linear issues are assigned to me?”
  • “List open tickets on the Platform team.”
  • “Find the Linear issue that tracks the database migration we shipped last Tuesday.”
  • “What’s the engineering ticket behind this Terraform change?”
  • “Pull the open issues in the Platform team that mention Redis.”
  • “What project does ENG-1234 belong to?”

Security & scope

  • Access follows the Linear user who connected (OAuth) or created the key (API key). To restrict what Annie can see, connect from an account with scoped access.
  • Credentials are encrypted at rest using AWS KMS and only decrypted in-process by Anyshift’s gateway.
  • All communication with Linear uses HTTPS/TLS.
  • You can revoke access at any time by disconnecting in Anyshift, revoking the OAuth app in Linear, or deleting the personal API key.
Anyshift + Linear = Annie ties every infrastructure change and incident back to the engineering work that drives it.