Linear

Connecting Linear turns issue activity into work events Halyard can report on. This is a source for Workspace admins (Reader A) tracking issue flow alongside other delivery signals.

What you get: work events, not searchable knowledge. Linear produces episodic records of issue creation and status changes that you list and filter by type, author, and time. It does not make issue descriptions semantically searchable.

No backfill

Linear is a partial integration. Halyard receives only events that happen after you connect — there is no history import. Issues created or moved before you connected Linear will never appear as work events. Connect it as early as you can; anything before connect-time is lost to the ledger.

What it produces

Linear events arrive as work-event types including:

• issue_created
• issue_status_changed
• issue_completed
• issue_reopened
• issue_deleted

Pure title, description, label, and other field edits do not create lifecycle events, so activity totals measure issue movement rather than webhook volume.

Each event carries provider metadata and an actor stitched to a Halyard user via external identity when the Linear account is linked.

Connect Linear

1. In the Halyard app, go to Settings → Integrations.
2. On the Linear card, start the OAuth flow and authorize Halyard.
3. Approve the connection.

Halyard registers signed webhooks during connect and verifies their signatures on every delivery. From that moment forward, issue create and status-change events flow in.

Next

• Knowledge vs work events — why issue activity isn’t searchable knowledge.
• Connect your sources — the full source matrix.