Agent skill
Jira Webhooks Skill
Receive and verify Jira Cloud webhooks. Use when setting up Jira webhook handlers, debugging signature verification, or handling issue and comment events like jira:issue_created, jira:issue_updated, jira:issue_deleted, comment_created, or comment_updated.
Install this skill
npx skills add hookdeck/webhook-skills --skill jira-webhooks
When to Use This Skill
- How do I receive Jira webhooks?
- How do I verify Jira webhook signatures?
- How do I handle
jira:issue_createdorjira:issue_updatedevents? - Why is my Jira webhook signature verification failing?
- Understanding Jira event types and payloads
Verification (core)
Jira Cloud signs the raw request body with HMAC-SHA256 keyed on the secret you set when registering a dynamic/OAuth 2.0 webhook, and sends the digest in the X-Hub-Signature header using the WebSub method=signature format — i.e. sha256=<hex>. Verify the raw body before parsing JSON and compare timing-safe.
Only dynamic webhooks (registered via the REST API with a
secret) are signed. Webhooks created in the Jira UI are not signed — they rely on HTTPS plus a hard-to-guess URL and an optional?secret=query parameter. See references/verification.md.
Node:
const crypto = require('crypto');
function verifyJiraWebhook(rawBody, signatureHeader, secret) {
const [method, sig] = (signatureHeader || '').split('=');
if (method !== 'sha256' || !sig) return false;
const expected = crypto.createHmac('sha256', secret).update(rawBody).digest('hex');
try {
return crypto.timingSafeEqual(Buffer.from(sig, 'hex'), Buffer.from(expected, 'hex'));
} catch {
return false; // length mismatch = invalid
}
}
Python:
import hmac, hashlib
def verify_jira_webhook(raw_body: bytes, signature_header: str, secret: str) -> bool:
method, _, sig = (signature_header or "").partition("=")
if method != "sha256" or not sig:
return False
expected = hmac.new(secret.encode(), raw_body, hashlib.sha256).hexdigest()
return hmac.compare_digest(sig, expected)
For complete handlers with route wiring, event dispatch, and tests, see:
Common Event Types
Jira does not send an event-type header. The event name is in the JSON body under the webhookEvent field.
Event (webhookEvent) | Triggered When |
|---|---|
jira:issue_created | An issue is created |
jira:issue_updated | An issue is edited or transitioned |
jira:issue_deleted | An issue is deleted |
comment_created | A comment is added to an issue |
comment_updated | A comment is edited |
comment_deleted | A comment is deleted |
worklog_created | A worklog is logged on an issue |
For the full event reference, see Jira webhook events.
Important Headers
| Header | Description |
|---|---|
X-Hub-Signature | HMAC SHA-256 signature, formatted sha256=<hex> (only on signed dynamic webhooks) |
X-Atlassian-Webhook-Identifier | Unique delivery identifier |
Environment Variables
JIRA_WEBHOOK_SECRET=your_webhook_secret # The `secret` set when registering the dynamic webhook
Local Development
# Start tunnel (no account needed)
npx hookdeck-cli listen 3000 jira --path /webhooks/jira
Reference Materials
- references/overview.md - Jira webhook concepts and common events
- references/setup.md - Registering webhooks via REST API and UI
- references/verification.md - Signature verification details and gotchas