Linear
Trigger Wexio flows from Linear issue events
Linear signs webhook bodies with HMAC-SHA256 in Linear-Signature (hex, no prefix). You connect it with the Linear preset, which uses Generic HMAC SHA-256. This mode has no replay protection, because the signature covers the body only and Wexio does not check the timestamp Linear puts in the body.
Provider docs: Setting up webhooks in Linear
Setup
1. Connect It in Wexio
Go to New connection → Inbound. Under Provider presets, click the Linear chip in HMAC presets. It sets Authentication mode to Generic HMAC SHA-256 and fills in these fields. Check that they match.
| Field | Value |
|---|---|
| Signature header name | Linear-Signature |
| Encoding | Hex |
| Header prefix (optional) | Leave empty |
Copy the Wexio endpoint URL.
2. Set Up the Provider
In Linear, go to Settings → API → Webhooks → New webhook. Paste the Wexio URL and pick the events. Copy the signing secret Linear shows into the Wexio Signing secret field.
3. Resolve Contacts
Linear events usually don't carry end-user identifiers. Send them through a proxy that adds the chat ID of a team contact to the body, and set Contact identifier type to Chat ID.
4. Capture the Schema and Bind a Flow
Capture the schema, then attach a Webhook Received trigger. Branch on {{webhook.action}} for the issue lifecycle (create, update, remove).
Troubleshooting
| Symptom | Fix |
|---|---|
| Signature mismatch | Re-copy the signing secret from Linear |
| Missing events | Check the webhook's event subscriptions in Linear |
Related
- Inbound Webhooks - auth modes, contact resolution and response codes
- Custom HMAC - how Generic HMAC SHA-256 verifies a request
- Webhook Received - the trigger that starts your flow
- Webhook History - check why a request failed