Jira webhook routing doesn't match webhooks to connections (Connection: n/a) #5254
Description
I’m encountering an issue where Jira webhooks received by Nango are forwarded without being associated with a connection. In the logs, both Connection and Script appear as n/a, which suggests that the jiraWebhookRouting script is never executed.
By contrast, Slack webhooks from the same Nango environment are correctly matched to a connection and wrapped with Nango metadata.
Setup
Integration: Jira (OAuth)
Scopes: offline_access, read:jira-work, write:jira-work, read:jira-user, manage:jira-webhook
Connection configuration:
{
"baseUrl": "https://subdomain.atlassian.net",
"cloudId": "1234",
"accountId": "1234",
"subdomain": "subdomain"
}
Webhook configuration
The Jira webhook points to Nango’s webhook URL:
https://api.nango.dev/webhook//jira
The webhook was created manually. The jiraPostConnection script did not create it automatically — is this expected behavior?
Observed behavior
When a Jira webhook is received, Nango logs show:
Type: WEBHOOK
Integration: jira
Connection: n/a ❌
Script: n/a ❌
As a result, the webhook is forwarded to my endpoint as a raw payload, without any Nango metadata.
Questions
- How does jiraWebhookRouting determine which connection a webhook belongs to?
- Is any additional configuration required for Jira webhook routing to work correctly?
- Is jiraPostConnection expected to automatically register a webhook in Jira, or must this always be done manually?