Summary
This article describes one business use case integration where ‘New Issue’ in JIRA is synced to ‘Case’ in Salesforce CRM.
Prerequisites
-
The user needs to have a working JIRA and Salesforce CRM account.
-
Working webMethods.io Integration cloud tenant.
Contents
- When New Issue is created in ‘Jira’, Search for a matching Case in ‘Salesforce CRM’ by ‘Jira’ summary. If no matching case is found in ‘Salesforce CRM’, create New Case in ‘Salesforce CRM’. If a matching case is found in ‘Salesforce CRM’, update a case in ‘Salesforce CRM’.
Steps
-
Login to webMethods.io Integration.
-
Create a workflow.
-
Click on the ‘Settings’ button.
-
Select the ‘JIRA’ trigger from the available list of triggers.
-
Provide the necessary details for the trigger. Choose ‘New Issue’ as value for ‘Select Trigger’, click on ‘+’ next to ‘Connect to JIRA’ and provide the necessary details for authorization, select a ‘Project Name’ and add an ‘Issue Type’. Click on ‘Save’.
Note: This trigger will be executed whenever a new issue with the same issue type is created in JIRA.
-
Click on the ‘Skip’ button, followed by ‘Done’.
-
Drag and drop the ‘Salesforce CRM SOAP’ connector from the app menu, then click on the ‘Settings’ button.
-
Select ‘Salesforce CRM’ version, click on ‘+’ to create Custom Action. Select Authentication type and create a ‘Salesforce CRM’ account by clicking ‘+’ next to ‘Connect to Salesforce CRM’ by providing necessary details. Name the Custom Action and click on ‘Next’.
- Select operation ‘query’, Business object ‘Case’ and fields. Then, click on ‘Next’ followed by ‘Done’
- After creating Custom Action, select created ‘Action’ and ‘Account’ then Click on ‘Next’
- Search Jira summary in ‘Salesforce CRM’ by mapping as shown in the below screenshot, then click ‘Next’ and ‘Done’
-
Drag and drop ‘Switch’ under ‘Developer Tools’ from the app menu.
-
Drag and drop ‘Salesforce CRM SOAP’ provider and add two cases to the ‘Switch’ as below:
Case 1:
- Click on the ‘Settings’ button of ‘case 1’. Add a filter under condition. Map the summary under ‘New Issue’ of ‘Jira’ trigger to ‘Input’ of the case, select Condition as ‘Does Not Match’, then Expected as a subject under ‘Query_Case’ operation of ‘Salesforce CRM’. Then, click on ‘Done’.
- Click on the ‘Settings’ button of the 'Salesforce CRM SOAP’ connector. Click on ‘+’ to create Custom Action. Select Authentication type and create a ‘Salesforce CRM’ account by clicking ‘+’ next to ‘Connect to Salesforce CRM SOAP’ by providing necessary details. Name the Custom Action and click on ‘Next’.
- Select operation ‘create’, Business object ‘Case’ and fields. Then, click on ‘Next’ followed by ‘Done’
- After creating Custom Action, select created ‘Action’ and ‘Account’ then Click on ‘Next’. Click on ‘+’ to create a Case in ‘Salesforce CRM’.
- Map ‘summary’ of Jira trigger to ‘Subject’ of ‘Salesforce CRM’ then click ‘Next’ and ‘Done’
Case 2:
- Click on the ‘Settings’ button of ‘case 2’. Add a filter under condition. Map the summary under ‘New Issue’ of ‘Jira’ trigger to ‘Input’ of the case, select Condition as ‘Matches’, then Expected as a subject under ‘Query_Case’ operation of ‘Salesforce CRM’. Then, click on ‘Done’.
- Click on the ‘Settings’ button of the 'Salesforce CRM SOAP’ connector. Click on ‘+’ to create Custom Action. Select Authentication type and create a ‘Salesforce CRM’ account by clicking ‘+’ next to ‘Connect to Salesforce CRM SOAP’ by providing necessary details. Name the Custom Action and click on ‘Next’.
- Select operation ‘update’, Business object ‘Case’ and fields. Then, click on ‘Next’ followed by ‘Done’
- After creating Custom Action, select created ‘Action’ and ‘Account’ then Click on ‘Next’. Click on ‘+’ to update Case in ‘Salesforce CRM’.
- Map ‘Id’ of Salesforce ‘Query_Case’ operation to ‘Id’ of ‘Update_Case’ operation and ‘summary’ of Jira trigger to ‘subject’ of ‘Salesforce CRM’ then click Next and Done
-
Save the workflow
-
This workflow will execute whenever a ‘New Issue’ with the same ‘Issue Type’ (provided while configuring the JIRA trigger in step 5) is created in JIRA. Output can be seen in the actions output tab.