Jira event capture in real time via WebHook and trigger Snaplogic pipeline
How to Trigger Snaplogic Pipeline after an event in Jira
This document shows how to setup a Jira instance to trigger a Snaplogic Pipeline (REST API) after an event in Jira and send the event information to Snaplogic pipeline. The events can be one of the following:
• Issue related events
• Project related events
• User related events
• JIRA configuration related events
• JIRA Software related events
Integration Scenario: Update ServiceNow ticket when an Issue is updated in Jira
Steps involved in this integration are:
• Create a SnapLogic pipeline and publish it as a triggered task
• Create a WebHook in Jira to trigger a SnapLogic pipeline after an issue is updated in Jira
Step1: Create a Snaplogic pipeline and publish it as a triggered task
The diagram below is a screen shot of SnapLogic pipeline that consumes the json document sent by Jira after an event (Example: Issue update, like add comments) happens in Jira and updates corresponding ServiceNow ticket.
The Binary Router Snap receives the incoming json from Jira and sends the output to two flows.
In the first flow, the incoming json document in binary format is parsed and converted to document format, mapper is used to map Jira issue information to appropriate fields in Service Now and “ServiceNow Update Snap” is used to update ServiceNow ticket.
In the second flow, the json received from Jira is written to an audit file.
A section of the json document received is below.
The following is a triggered task REST API created by Snaplogic for the integration scenario and we will use this to configure WebHook in Jira.
Step2: Create a WebHook in Jira to trigger a Snaplogic pipeline after an issue is updated in Jira
In Jira go to Applications.
You will see WebHooks in Advanced Configuration
Create a new WebHook to call the Snaplogic Triggered task
In the URL configuration: Put the Snaplogic Triggered task, including the authorization information (bearer_token)
Configure the event related information, in this integration we are capturing the issue related events. The diagram below shows the available events of an issue that can be captured and also you can write a JQL query send events only that match certain conditions.