Linear

A Linear webhook delivers issue lifecycle events from Linear into Plural. After you configure the source once, you can attach it to one or more workbench triggers to start jobs based on issue changes.

This guide uses the Plural Console UI and Linear's webhook settings. For general webhook behavior and trigger configuration, see Webhooks.

Prerequisites

Before you begin, make sure you have:

• A Linear workspace with issues you want to monitor.
• Permission in Linear to create and manage webhooks (workspace or team administrator).
• Permission in Plural Console to create a webhook source and configure workbench triggers.

Capabilities

Linear webhooks deliver issue lifecycle events:

• Issue created — a new issue is created in the team.
• Issue updated — issue fields such as title, description, status, assignee, priority, labels, or estimates are modified.
• Issue status changed — the issue moves to a different workflow state (for example, from "Backlog" to "In Progress").
• Issue completed — the issue is marked as done or completed.
• Issue canceled — the issue is canceled or archived.
• Issue deleted — an issue is removed from the workspace.

Plural accepts Linear webhook payloads with type: "Issue" and extracts issue data from the data field. Status mapping recognizes Linear's workflow states: In Progress and In Review map to in progress; Canceled or Cancelled map to cancelled; Done and Completed map to completed; all others default to open.

Inbound events are stored as issues in Plural and do not start a job until a workbench trigger matches the payload content. See Webhook triggers for binding events to workbenches.