ssanikop
Former Employee
Joined 9 years ago
User Profile
User Widgets
Contributions
Re: Providing Authentication for Triggered Tasks by passing credentials via https request
Make sure to use the correct URL. There will be two URL’s if you are using groundplex. Also, you might have to setup firewall rules if the call is from outside the firewall. https://docs-snaplogic.atlassian.net/wiki/spaces/SD/pages/1438189/How+to+Run+a+Pipeline+from+a+URL+Triggered+Task Running an On-Premises Pipeline from a URL If you are running a pipeline in an on-premises Snaplex and streaming data to/from the pipeline, you must use the “On-Premises URL” to execute the pipeline, the “Cloud URL” will not work. The “On-Premises URL” will refer to the Groundplex machine from which you can perform the request. The request must be done on the Groundplex machine since the service is only listening for connections from the local machine. If you would like to allow requests from other hosts, you can configure the machine’s firewall rules or install a proxy to forward the requests to the Groundplex service.3.2KViews1like0CommentsJIRA event capture in real time via WebHooks and triggering Snaplogic pipelines
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. { “timestamp”: 1483558289780, “webhookEvent”: “comment_created”, “comment”: { “self”: “https://snaplogic.atlassian.net/rest/api/2/issue/25701/comment/21801”, “id”: “21801”, “author”: { “self”: “https://snaplogic.atlassian.net/rest/api/2/user?username=admin”, “name”: “admin”, “key”: “admin”, “created”: “2017-01-04T11:31:29.780-0800”, “updated”: “2017-01-04T11:31:29.780-0800” } } 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. https://elastic.snaplogic.com:443/api/1/rest/slsched/feed/ConnectFasterInc/Shankar%20Sanikop/ServiceNow%20Jira/Jira%20Outbound%20Trigger%20Task? 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) https://elastic.snaplogic.com:443/api/1/rest/slsched/feed/ConnectFasterInc/Shankar%20Sanikop/ServiceNow%20Jira/Jira%20Outbound%20Trigger%20Task?bearer_token=FrcE0Whf6r2NjHx 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. strong text4.5KViews0likes1Comment