Configure the webhook
Paste the Webhook URL
Use the following URL, replacing
<your-customer-key> with the key from the Customer Portal:Select the resources to track
Select all available resources for the most complete insights. Linear lets you pick individual resource types if you prefer granular control.
Save the signing secret
After creating the webhook, Linear will show you a signing secret. Copy this value — you’ll need to save it in the Customer Portal so Cogniscape can verify that incoming events are genuinely from Linear and have not been tampered with.Go to the Customer Portal and paste the signing secret in the Linear integration section under Get Started → Linear Integration.
Verify the webhook
After saving, you can trigger a test by creating or updating an issue in Linear. Check the webhook delivery log under Settings → API to confirm events are being sent with a200 response.
Supported resources
Cogniscape processes these Linear webhook resource types:| Resource | Actions | What it captures |
|---|---|---|
Issue | create, update, remove | Title, identifier (e.g. ENG-123), state, priority, assignee, labels, description, and previous state on updates |
Comment | create, update | Comment body on issues — discussions, decisions, and context |
Project | create, update | Project name and state (planned, started, completed) |
ProjectUpdate | create, update | Status reports posted to projects — body text and health status (on track, at risk, off track) |
Resources not listed above are received but silently ignored. Selecting all resources is safe — it won’t create noise in your knowledge graph.
Why the signing secret matters
Linear signs every webhook payload with an HMAC-SHA256 signature using the signing secret. Cogniscape verifies this signature before processing any event. Without the signing secret saved in the Customer Portal, webhook events will be rejected with a401 response.
If you’ve lost the signing secret, delete the webhook in Linear and create a new one — Linear will generate a fresh secret.