Linear Webhook Setup Guide

The Native Webhook URL is generated once an account has been linked. You will paste it into Linear in the next steps.

• Open the linked account in StackOne Hub.
• Copy the value from Native Webhook URL.

Sign in to your Linear account and open the API settings for your workspace. The Webhooks section is its own section on the API settings page — separate from OAuth applications and from your Personal API keys — so you create webhooks here regardless of whether your StackOne connection uses an API Key or OAuth.

• In the left sidebar under Administration, click API.
• In the Webhooks section, click New webhook.

On the Create webhook page, identify the webhook and point it at StackOne.

• In Label, enter a descriptive name such as StackOne Integration.
• In URL, paste the Native Webhook URL you copied from StackOne.
• Linear auto-generates a Signing secret for the webhook. You do not need to copy it into StackOne — inbound events are authenticated by the token already embedded in the Native Webhook URL.

Under Data change events and Other events, enable the events you want delivered. Only the events you tick here are sent to StackOne.

• Tick each resource you want to receive, for example Issues, Comments, Projects, and Cycles.
• Enable Issue SLA under Other events to receive SLA events.
• See Available webhook events below for the full list and what each event covers.

Decide which teams the webhook covers, then save it.

• In Team selection, choose All public teams to cover the whole workspace, or pick a single team. This cannot be changed after creation.
• Click Create webhook.

Events related to issues. Enable the Issues checkbox.

• Issue Created (Issue.create) — Fired when a new issue is created.
• Issue Updated (Issue.update) — Fired when an issue changes, including status, assignee, or other field updates.
• Issue Removed (Issue.remove) — Fired when an issue is deleted.

Events related to issue labels. Enable the Issue Labels checkbox.

• Issue Label Created (IssueLabel.create) — Fired when a new issue label is created.
• Issue Label Updated (IssueLabel.update) — Fired when an issue label is renamed or recolored.
• Issue Label Removed (IssueLabel.remove) — Fired when an issue label is deleted.

Events related to attachments on issues. Enable the Issue attachments checkbox.

• Attachment Created (Attachment.create) — Fired when an attachment is added to an issue.
• Attachment Updated (Attachment.update) — Fired when an attachment on an issue changes.
• Attachment Removed (Attachment.remove) — Fired when an attachment is removed from an issue.

Events related to issue comments. Enable the Comments checkbox.

• Comment Created (Comment.create) — Fired when a comment is added to an issue.
• Comment Updated (Comment.update) — Fired when an existing comment is edited.
• Comment Removed (Comment.remove) — Fired when a comment is deleted.

Events related to emoji reactions. Enable the Emoji reactions checkbox.

• Reaction Created (Reaction.create) — Fired when an emoji reaction is added.
• Reaction Removed (Reaction.remove) — Fired when an emoji reaction is removed.

Events related to projects. Enable the Projects checkbox.

• Project Created (Project.create) — Fired when a new project is created.
• Project Updated (Project.update) — Fired when a project changes.
• Project Removed (Project.remove) — Fired when a project is deleted.

Events related to project status updates. Enable the Project updates checkbox.

• Project Update Created (ProjectUpdate.create) — Fired when a project update (status post) is created.
• Project Update Updated (ProjectUpdate.update) — Fired when a project update is edited.
• Project Update Removed (ProjectUpdate.remove) — Fired when a project update is deleted.

Events related to cycles. Enable the Cycles checkbox.

• Cycle Created (Cycle.create) — Fired when a new cycle is created.
• Cycle Updated (Cycle.update) — Fired when a cycle changes.
• Cycle Removed (Cycle.remove) — Fired when a cycle is deleted.

Events related to documents. Enable the Documents checkbox.

• Document Created (Document.create) — Fired when a new document is created.
• Document Updated (Document.update) — Fired when a document is edited.
• Document Removed (Document.remove) — Fired when a document is deleted.

Events related to initiatives. Enable the Initiatives checkbox.

• Initiative Created (Initiative.create) — Fired when a new initiative is created.
• Initiative Updated (Initiative.update) — Fired when an initiative changes.
• Initiative Removed (Initiative.remove) — Fired when an initiative is deleted.

Events related to initiative status updates. Enable the Initiative updates checkbox.

• Initiative Update Created (InitiativeUpdate.create) — Fired when an initiative update is created.
• Initiative Update Updated (InitiativeUpdate.update) — Fired when an initiative update is edited.
• Initiative Update Removed (InitiativeUpdate.remove) — Fired when an initiative update is deleted.

Events related to customers. Enable the Customers checkbox.

• Customer Created (Customer.create) — Fired when a new customer is created.
• Customer Updated (Customer.update) — Fired when a customer record changes.
• Customer Removed (Customer.remove) — Fired when a customer is deleted.

Events related to customer requests. Enable the Customer requests checkbox.

• Customer Need Created (CustomerNeed.create) — Fired when a customer request is created.
• Customer Need Updated (CustomerNeed.update) — Fired when a customer request changes.
• Customer Need Removed (CustomerNeed.remove) — Fired when a customer request is deleted.

Events related to workspace users. Enable the Users checkbox.

• User Updated (User.update) — Fired when a workspace user’s profile or membership changes.

SLA events for issues, under Other events. Enable the Issue SLA checkbox.

• Issue SLA Created (IssueSLA.create) — Fired when an SLA is set on an issue.
• Issue SLA Updated (IssueSLA.update) — Fired when an issue’s SLA status changes, such as breaching or completing.
• Issue SLA Removed (IssueSLA.remove) — Fired when an SLA is removed from an issue.

Audit log entries are delivered through Linear’s audit log webhook, which is configured separately from the data-change webhook above and may require an eligible Linear plan.

• Audit Entry Created (AuditEntry.create) — Fired when a new audit log entry is recorded in the workspace.

Linear sends a separate HTTP POST for each event — payloads are not batched. Every request carries the event type (such as Issue) and action (create, update, or remove), which StackOne uses to route the event to its handler.

Each request is signed with an HMAC-SHA256 Linear-Signature header and carries a Linear-Timestamp. Linear expects an HTTP 200 response within 5 seconds and retries failed deliveries up to 3 times with backoff; a webhook that keeps failing is disabled and must be re-enabled manually in Linear.