Contact Us web form for Jira Service Desk using Kumologica Flow
In this article we will create “Contact Us” HTML form that is present on most of websites and integrate it with Jira Service Desk using Kumologica Designer flow running on AWS Lambda.
If you want to learn more about Kumologica, we’d highly recommend you check out:
Prerequisites
Jira Service Desk
If you don’t have access to Jira software or Jira Service Desk you can create free account. Once account has been created you will be given your site url (ends with atlassian.net) for your Jira Service Desk Instance.
Next Step is to create API Key. Navigate to: Settings icon (in the top right corner) > Atlassian account settings > Security (in the left panel) > Create and manage API tokens >Create API Token. Enter label for token and press Create, you will be presented API token. Copy it as you will need this token to authenticate from Kumologica flow.
We will be using General service desk (GSD) example project that has been created for us. The GSD is a project id that we will be using in Kumologica flow.
Building orchestration flow
Once we have access to Jira configured we can start building our Kumologica flow.
Create New Project
Open Kumologica Designer, click the Home button and choose Create New Kumologica Project. Enter name (for example jira-demo), select directory for project and switch Source into From Existing Flow …
Copy and Paste the following flow:
press Create Button.
Install Jira Plugin.
Jira node is a contribution node and must be explicitly installed in Kumologica Designer. Press Add more nodes button located in the bottom left corner of designer. You will be presented screen with all contribution nodes that are currently available. Choose JIRA node, press Install button. After few seconds, plugin will be installed and you will be prompted to restart Kumologica Designer. Jira node will be located under new category: Platforms after restart.
Edit flow
After installing JIRA node, the imported flow will look like below:
Click on the Create Issue Jira node to display its properties and change Jira Connection Details section:
- Host URL: enter the url that has been created for your Jira service desk instance (ends with atlasian.net)
- Username: the user name you setup when creating account or the username you use for your jira instance
- API Token: token created in Prerequisites section
Press Save button to return to the flow.
We have put connection details directly into properties for simplicity. We recommend to use AWS Parameter store to store secrets and use Kumologica AWS SSM Node to retrieve them.
Deploy flow to AWS Lambda
Select CLOUD tab on the right panel of Kumologica designer, choose AWS Profile and press Deploy button. This will trigger build and deployment of flow into AWS Lambda. After short while you should see the API gateway url that has been created for your flow in the terminal:
Contact Us HTML form
Below is a sample “Contact Us” html form, save it in local drive. Change line 18 to use the API Url that was displayed in Kumologica Designer terminal after successful deployment to AWS Lambda. Don’t forget to append it with /issue to call right service.
Open html file in your browser, fill up details and press Submit button.
The browser should display empty json: {}. When you switch to your Jira Service Desk General service desk project you should see new issue created with following details:
As you can see, the properties set in Kumologica Jira node mapped Summary into Title, Your E-Mail and Your Message got concatenated into Description.
Conclusion
This article presented how easy Kumologica Designer flow orchestrates and integrates with Jira software using Jira node. Within few minutes we have setup Jira Service Desk, created and deployed Kumologica flow and finally created simple contact us html form that calls flow and creates issue in Jira.
Remember Kumologica is totally free to download and use. Go ahead and give it a try, we would love to hear your feedback.
In the meantime, if there is any specific use case that you would like to see in a future article please let us know in the comments section.
Resources
Code used in this article is available in KumologicaHQ public Github repository:
Feel free to check it out and change for your needs.
