Skip to main content
All Linear integration capabilities

​
About

Send Linear webhooks to Sazabi to search issue, comment, project, cycle, and other data changes next to the rest of your production telemetry. Linear posts each change to your Sazabi intake URL as a JSON POST, signed with the webhook’s signing secret. There is no agent to deploy, and Sazabi never calls the Linear API.

​
What Sazabi records

Each Linear delivery becomes one Sazabi record that keeps the full payload, timestamped with createdAt. These attributes are extracted for filtering:

​
Prerequisites

  • Linear workspace admin access, which creating webhooks requires.
  • The webhook’s signing secret. Linear shows it on the webhook’s page, so create the webhook first. Any placeholder URL works until you have your Sazabi intake URL.
  • Your Sazabi intake URL.
Signature verification is in early access. While it is on for your organization, Sazabi asks for the verification secret before it creates the intake URL, and rejects any delivery whose signature does not match. Contact support to turn it on.

​
Set up in the dashboard

1

​
Create the webhook in Linear

In Linear, open Settings > API > Webhooks and click New webhook. Give it any placeholder URL for now, choose the data change events to send, and save. Then open the webhook and copy its Signing secret.
2

​
Add the log source

In the Sazabi dashboard, open Settings > Log sources, choose Linear Webhooks and add it. If Sazabi asks for a verification secret, paste the signing secret from Linear. Sazabi then shows your intake URL.
3

​
Point the webhook at Sazabi

Back in Linear, open the webhook and set its URL to your Sazabi intake URL. Save.

​
Set up with the CLI

You can also register the Linear Webhooks log source with the Sazabi CLI (installed and authenticated — see CLI reference).
The command prints the intake URL. Paste it into the webhook’s URL in Linear. The secret is read from standard input, so it never appears in your shell history. Run sazabi log-sources get <log-source-id> at any time to reprint the endpoint, or sazabi log-sources list to see every log source in the project.

​
Verify signatures

Linear signs every delivery with the webhook’s signing secret and sends the result in the Linear-Signature header. Sazabi checks it on the exact bytes Linear sent and rejects a delivery with 401 when the signature does not match or when the webhookTimestamp in the body is more than a minute from Sazabi’s clock. A rejected delivery is not stored and not billed. Each Linear webhook has its own signing secret, so create one Sazabi log source per webhook. To change the secret later, open the log source in Settings > Log sources and choose Rotate secret. The previous secret keeps working for 24 hours by default, so Linear keeps delivering while you update it. The Intake page shows rejected deliveries and why.

​
Verify

Create or update an issue in a team the webhook covers. Open the Intake page in the Sazabi dashboard and confirm records from the Linear Webhooks source appear. Records typically arrive within a minute or two.

​
Troubleshooting

Linear shows failed deliveries with 401 — The signature did not match, or the delivery was more than a minute old. Check that the secret in Sazabi is the signing secret of this webhook, not of another webhook. No records after saving — Confirm the webhook’s URL exactly matches your Sazabi intake URL, including the https:// scheme, that the webhook is enabled, and that it covers the team and resource type you changed.

​
Further reading

Intake

See per-source ingestion volume and health in the Intake page.

Webhook Events

Verify signatures and send webhooks from any other platform.

Linear webhooks

Linear’s documentation for webhooks and the signature Sazabi checks.

Log sources

Browse the full log source catalog.