Skip to main content
Use the @bijection/connectors/linear entrypoint to declare Linear resources.

Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

Issues

pull: Listing, trash withdrawal and signed webhook hints

The following example matches configuration webhooks.

Configuration: standard

Case: linear/issues/pull/standard. Connection and resource configuration are declared by this exact case. Credential kind: linear. Keep credential material in the private credential inventory. Inspect the complete configuration contract below for settings and conditional requirements.
Native admission analysis is available for this exact declaration. Collection: issues
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Configuration: webhooks

Case: linear/issues/pull/webhooks. Connection and resource configuration are declared by this exact case. Credential kind: linear. Keep credential material in the private credential inventory. Inspect the complete configuration contract below for settings and conditional requirements.
Native admission analysis is available for this exact declaration. Collection: issues
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Provider guidance

Compiled declaration examples and configuration details are published in the connector reference. The connection holds a linear credential (linear.credential) for https://api.linear.app. A personal API key goes RAW in Authorization, with no Bearer; configure it as a raw-authorization credential (an OAuth token takes Bearer). Identity is the organization id. issues.pull walks the issues the key can see, archived and trashed ones included (includeArchived: true), in updatedAt order by Relay cursor while hasNextPage holds. The first pass walks every issue. Each finished pass carries the latest updatedAt it read (sync.carry), and the next pass reads only updatedAt >= five minutes before it. An updatedAt filter bounded a page and not the set, so the boundary is re-read and re-read issues deduplicate by updatedAt, the opaque version. A pass that fails hands nothing on. Linear’s own trashed: true withdraws an issue, in a listing or a point read; trash is restorable and a restored issue reappears under the same id. With updates: "webhooks", a delivery verified as HMAC-SHA256 in hex over the raw body (linear-signature), identified by linear-delivery, requests a point read of data.id. Linear’s replay bound, webhookTimestamp, is a field inside the signed body that no ingress scheme reads, so replay is bounded only by the delivery ring and a delivery proves a refresh hint. Identical creates made two issues and Linear offers no precondition, so no write is declared. Nothing here has run against Linear or been qualified.

Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.