Linear integration

What it does

The Linear integration lets your agency run issue, comment, and project operations on behalf of your clients without leaving TaskJuice. Connect a client's Linear workspace once and you can create, update, fetch, and archive issues, post comments on existing issues, list issues assigned to the connected user, list the workspace teams, and spin up new projects across one or more teams. Three webhook triggers fire when an issue is created, an issue is updated, or a comment is created, so you can chain Linear activity into the rest of your workflow.

Connect a Linear account

1. Open your workspace in TaskJuice and navigate to Connections.
2. Choose Linear and click Connect.
3. Sign in to the Linear account that should authorize the connection and approve the requested scopes (read, write, issues:create, comments:create).
4. TaskJuice returns you to the workspace with the connection ready to use in any workflow.

Linear access tokens last 24 hours and refresh automatically via the refresh token returned at authorization time. To revoke access, open Linear, navigate to Settings, API, and remove the TaskJuice OAuth application. See the Linear OAuth 2.0 guide for the full grant flow.

Triggers

• linear/issue-created fires when a new issue is created in the Linear workspace. The activation payload carries the Linear webhook envelope (action, type, data, createdAt) with the serialized issue under data.
• linear/issue-updated fires when an existing issue is updated. The activation payload includes updatedFrom with the previous values for any fields that changed.
• linear/comment-created fires when a comment is created on a Linear issue. The activation payload carries the serialized comment under data.

Linear signs every webhook with an HMAC-SHA256 hex digest of the raw body on the Linear-Signature header. TaskJuice verifies the signature against the signing secret returned by the GraphQL webhookCreate mutation before activating the workflow.

Actions

• linear/create-issue creates a new issue in the specified team, optionally setting description, assignee, state, priority, project, and labels.
• linear/update-issue updates an existing issue. Supports changing title, description, state, assignee, priority, and project.
• linear/get-issue fetches a single issue by ID, including assignee, state, team, project, and labels.
• linear/delete-issue archives an issue by ID. Linear performs soft deletion via issueDelete, so the issue can be restored from the workspace UI.
• linear/create-comment posts a comment on an existing issue. The body supports Markdown.
• linear/list-my-issues fetches issues assigned to the authenticated user, with cursor pagination via first and after.
• linear/list-teams lists the teams the connected workspace can access, with cursor pagination via first and after.
• linear/create-project creates a new project under one or more teams, with optional description, lead, start date, and target date.

Known limitations

• Linear exposes a single GraphQL endpoint at https://api.linear.app/graphql. Every action posts a GraphQL document to that URL, so the rate limit budget is shared across read and write traffic from the same connection.
• The platform enforces a complexity-based rate limit per OAuth application. When the budget is exhausted Linear returns a 429 status, which TaskJuice surfaces as a retryable error so downstream resilience policies can back off.
• Linear access tokens expire after 24 hours. TaskJuice handles refresh automatically using the refresh token returned at authorization time. If a refresh fails, reconnect the account from the Connections page.
• Personal API keys are not supported by this integration. Use the OAuth flow, which issues a workspace scoped access token tied to the authorizing user.
• Pagination uses Relay-style cursors. Each list action returns one page per call along with the endCursor value, so workflows that need every page should drive paging explicitly.