Attachment from JIRA is not getting attached to proper target record in ServicenNow.Issue For the existing issue in Jira, when an attachment is added to an issue and it also has an associated incident in ServiceNow, the attachment_created event is received in ServiceNow. However, with the flow setup from https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0861023, even if we add a lookup record action into this flow, we will fail to identify the existing incident to attach the attachments. SymptomsWhen we receive attachment_created webhook event is ServiceNow, as per the webhook decision routing policy we execute the required flow. If the requirement is to find the existing incident record in ServiceNow based on the correlation ID and attach the attachment to it, the lookup up record action will fail, because the attachment_created webhook event payload does not contain the Issue ID Typically issueID will be mapped to correlation ID in ServiceNow to identify the matching records between Jira and ServiceNow Since issueID will not be provided with attachment_created payload, we cannot identify the existing incident in ServiceNow to attach the attachment, it identifies a random incident where correlationID is empty and it attaches the attachment to such incident. FactsAttachment_created payload will look like this. This doesn't include issueID { "Attachments": [ { "author": { "accountId": "xxxxxxxxxxxxxxxxxxxxxxxxxxx", "accountType": "atlassian", "active": true, "displayName": "Test", "emailAddress": null, "key": null, "name": null, "self": "https://xxxxxxxxxxx.atlassian.net/rest/api/2/user?accountId=712020%3A3c815e55-dd11-4bcd-8767-488214c116d4", "timeZone": "Asia/Calcutta" }, "content": "https://xxxxxxxxxx.atlassian.net/rest/api/2/attachment/content/10066", "created": "2025-05-29T09:55:30.962+0530", "filename": "Screenshot 2025-05-28 at 10.28.17 AM.png", "id": "10066", "mimeType": "image/png", "self": "https://xxxxxxxxxx.atlassian.net/rest/api/2/attachment/10066", "size": 2902972 } ] }ReleaseJira webhook all versionsResolutionAttachment_created event payload will not have IssueID and it's a limitation from Jira. We need to modify the callback URL configured in Atlassian webhook URL to receive the issue ID for all webhook events explicitly. Default callback URL generated in ServiceNow will look like this: https://XXXXXX.service-now.com/api/sn_jira_spoke/jira_webhook_callbacks/wh_entry?ni.nolog.id=17f9e9ef47771910d90c0e52846d43fe&ni.nolog.token=%EF%B7%9E%EF%B7%9F We need to append the issue ID as a query parameter in webhook URL as below. In your callback URL registered in Jira webhook, include &issue_id=${issue.id} at the end. https://XXXXXX.service-now.com/api/sn_jira_spoke/jira_webhook_callbacks/wh_entry?ni.nolog.id=17f9e9ef47771910d90c0e52846d43fe&ni.nolog.token=%EF%B7%9E%EF%B7%9F&issue_id=${issue.id} With this, the transactions received in ServiceNow will capture the issueID in the URL. Sample transaction URL received in ServiceNow: /api/sn_jira_spoke/jira_webhook_callbacks/wh_entry?issue_id=10036&triggeredByUser=xxxxxxxxx Based on the below scripted REST resource, it assigns the Issue ID from request query params and assigns it as sub flow input IssueID. https://xxxxxxxx.service-now.com/now/nav/ui/classic/params/target/sys_ws_operation.do%3Fsys_id%3D2316ac0c87723300c1e95773e8cb0b57 Then in the flow we can use correlationID=IssueID and use it to lookup records in ServiceNow. Sample flow design and sample execution is attached below Use IssueID from subflow inputs to lookup record in flow: Sample Execution with changes to webhook url to include issue ID: Flow design is similar to https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0861023 But above KB explains it by creating a new incident and attaching attachments. For existing incidents, you just need to include Lookup record action to identify existing incidents with correlationID=IssueID from sub flow inputs. Please note, correlationID should not be issue>ID from subflow inputs. It is direct subflow input Issue ID because we do not get payload for issue input in subflow for atachment_created events. For a use case to attach attachments to existing incidents, sample flow looks like this. Added a lookup record step to the flow in KB0861023 article.