Linear

Linear

Tools for working with Linear over the Linear GraphQL API (POST https://api.linear.app/graphql): create and update issues, comment on them and attach links, find issues by identifier or filter, manage projects and post project updates, and resolve the teams, workflow states, labels, users, milestones, and cycles an agent needs to act. 22 scripts across issue writes, issue reads, projects, and workspace navigation. This version covers the day-to-day issue-tracking job over the public API; every tool builds one GraphQL query or mutation and posts it to the single endpoint.

Independent, unofficial connector for Linear. Not affiliated with, endorsed by, or sponsored by Linear. "Linear" is a trademark of its owner, used only to identify the service this connector works with.

When to use this

• An agent needs to create or update issues — open an issue in a team; change its title, description, state, assignee, priority, project, cycle, or due date; add or remove a single label; comment on it; or attach a link (a related ticket, doc, or PR).
• An agent needs to find or read issues — fetch one by UUID or human identifier (e.g. ENG-118), or search by title text, assignee, state, team, project, or label, then read its comment thread.
• An agent needs to manage projects — create or update a project, read one, list projects, and post a status update with a health signal.
• An agent needs to resolve names to ids before writing — list teams, workflow states, labels, users, project milestones, and cycles, or get the authenticated "me" identity for assign-to-self / "my issues" flows.

Setup

This is an agentskills.io skill.

If the connector has not been installed as a skill yet, install it first with npx skills add zapier/connectors --skill linear (or your harness's own skill-install mechanism), then continue here. Installing the skill copies these files, not dependencies. Before running the CLI, a local MCP server, or zapier-sdk auth commands, run npm install --omit=dev here once. Importing the published package as a dependency in your own project instead? That npm install already resolves everything — see references/use-as-sdk.md.

Want the actual repo source instead — to browse references/, run this connector's tests, or hack on it? See README.md for a scoped git clone.

The connector runs on Node.js 22.18+. Pick the reference that matches how you're running it, and load it before doing anything else:

Scripts

Every script uses the single connection linear. Grouped below as issue writes, issue reads, projects, and workspace navigation; ids everywhere are UUIDs, except the issue tools (getIssue, updateIssue, archiveIssue, addIssueLabel, removeIssueLabel, createComment, createAttachment, listIssueComments) also accept an issue's human identifier (e.g. ENG-118).

Disambiguation & refusals

This connector resolves names to ids, then writes. Two situations trip up an action-biased agent — handle both before you write.

Before writing to a record you looked up by name — the id inputs on the write tools (assigneeId, teamId, projectId, leadId, stateId, labelId, cycleId, projectMilestoneId) are UUIDs you get from a resolver tool (listUsers, listTeams, listProjects, listWorkflowStates, listLabels, listCycles, listProjectMilestones). The names most likely to collide are users (two people with the same display name — resolve with listUsers) and projects / teams (a workspace can have similarly-named ones — resolve with listProjects / listTeams). Count the exact case-insensitive name matches in the resolver's page:

• Exactly one match — act on it. Don't over-ask; a single unambiguous match is the answer.
• Two or more that tie — stop. List the tied candidates with a distinguishing field (a user's email, a project's state / url, a team's key) and ask the user which one they mean. Don't pick arbitrarily and don't write against all of them.

Before fulfilling a request, check that a script actually does it. This catalog deliberately does not:

• Hard-delete an issue. There is no permanent delete — use archiveIssue, which is reversible (recoverable from the archive). Don't substitute another tool and call the issue deleted.
• Manage the customer-requests surface (create or find customers and their needs). It is not in this version. There is no tool for it; don't approximate it with an issue or a project.
• Set up triggers or event subscriptions. This connector is non-trigger by design; Linear's webhook surface is not exposed.

If asked for any of these, tell the user it's unsupported and stop — don't reach for an unrelated tool to approximate it and never report success for an action you didn't perform.

Auth

Every shape passes auth as one connection selector, not the secret — a [<resolver>:]<value> string. Every connector accepts zapier:<connection-id> (Zapier-managed auth — routes through Zapier's auth, retries, and governance layer); some also accept one or more direct-token resolvers (naming and count vary per connector) — check this connector's own resolvers rather than assuming. The <resolver>: prefix is optional; a bare value goes to the first resolver that claims it — a UUID-shaped bare value always claims zapier:. Each script declares the connections it needs and the resolvers each accepts. The exact syntax for passing a connection (and how to see this connector's resolver list) differs by shape — see the reference you loaded above.

Checking what's already configured first? Don't dump environment values to do it — env or env | grep <name> prints the value along with the name, leaking a live credential into the transcript if one is set. Check names only (env | cut -d= -f1 | grep -i <name>) or test a known name directly ([ -n "$VAR_NAME" ]).

No connection yet? Pick one — and follow the reference's own flow to obtain it; never just ask the user for a connection id or token as if they already have one memorized:

Output format

Every script returns a { data, meta } envelope:

• data — the script's result (the shape its outputSchema declares; see the reference you loaded above for how to inspect a script's exact schema in your shape).
• meta.outputDataValidation — what validating data did:
  • { skipped: false, droppedPaths: null } — validated, nothing removed.
  • { skipped: false, droppedPaths: [...], instruction } — validated, but those paths were stripped from data: fields the script returned from the API that the outputSchema doesn't declare. If you need them, re-run with output validation skipped.
  • { skipped: true } — validation was bypassed; data is the raw, unchecked script output.

Reading dropped fields / skipOutputDataValidation. To receive the raw, unvalidated result, opt out of output validation (the exact syntax differs by shape — see the reference you loaded above). Input validation is never skipped.

Trimming the result / filterOutputData. To shrink a large result down to the fields you need, pass a jq expression that post-processes data (again, exact syntax per shape). The jq runs against data only, NOT the { data, meta } envelope, so write it rooted at data (run the script's --help — or your shape's equivalent — to see its output schema). The transformed value replaces data, meta is preserved, and the result is NOT re-validated against the output schema.

References

Load the matching reference file before working in that area: