Template Automation with Webhook links
Easily integrate Smart Templates with Automation for Jira and other third-party tools ⚡️
Contents 👇🏼
Overview
With a Webhook link 🔗, you can trigger issue creation from a template using Jira Automation or third-party tools like Postman. It works with simple templates without variables, and you can also send different types of variables in the request body to enhance your processes even further 🚀.
Steps to Generate a Webhook Link
Open the edit page of the template you want to create a webhook link for.
Navigate to the Automation tab.
Click the Generate webhook button.
That’s it! Just click the Copy button to grab the link, then paste it into Jira Automation or any other tool where you want to trigger issue creation from the template.
Create issues from a template using a link
☝🏼NOTE: This method is ideal for templates without variables. Not using variables yet? Find more information about them here → Variables
Grab a Webhook link of a template
Execute web request using POST method (no need to add request body) like below in Postman
OR
Setup Jira Automation which will trigger issues creation from your template:
Go to your Jira project → Navigate to Project Settings in the left-hand sidebar →
Select Automation from the options.Click on Create Rule to start setting up a new automation rule → Choose a Trigger for your rule based on when you want the webhook to be called
After selecting your trigger, click on THEN: Add an Action → Select Send Web Request from the list of actions → In the Webhook URL field, paste the webhook link that you generated for the template
☝🏼NOTE: Use the HTTP POST
method and leave the Web Request Body empty. Also, keep the Headers section empty.
Add any additional Conditions or Actions based on your needs (optional)
Give your rule a Name and publish it → click Turn it on to activate the rule.
Automation of a Tempalte with variables
When triggering a Webhook, you can customize the issues created by passing variables in the request body using JSON format. Currently, Text Variables are supported, and in the future, additional variable types such as Select List (Single choice), Select List (Multiple choices), and User Picker will be available. More about Variables can be found here → Variables.
Go to the Edit page of the template that has the variables configured
Example of a Variable:
And the Variable usages:
Click the Generate webhook button on the Automation tab → Copy the generated webhook link.
Open your Jira project and go to Project Settings → Select Automation from the sidebar → Click on Create Rule to start a new automation rule → Choose the appropriate Trigger for your automation rule
After setting the trigger, click on THEN: Add an Action → Select Send Web Request as the action → Paste the copied webhook link into the Webhook URL field
Select HTTP Method POST → and pick Custom data in the Web request body field
In the Custom data field, paste the pairs of key : value using JSON format to customize your issues
Give your rule a Name and publish it → click Turn it on to activate the rule.
Check the created issues to confirm that the template has been applied as expected and that the variables have been correctly populated.
{
"Day" : "1st",
"Month" : "September",
"Year" : "2030"
}
Other examples (Jira Smart Values)
Smart Templates allow you to create customizable Jira issues by passing variables through the Webhook body. You can even pass Smart Values as the input for these template variables, enabling dynamic and context-specific issue creation based on real-time data.
Let's look at this template, where only variables have been added to the Summary and Description fields:
Your Webhook request body can include Smart Values that extract the Summary and Description from the source task and pass them as values to the corresponding variables in the template via the webhook body.
See it in JSON format below:
{
"summary" : "Review and Finalize API Documentation: {{issue.summary}}",
"description" : "This task is based on the completed documentation task:\n\n*Original Summary:* {{issue.summary}}\n*Original Description:* {{issue.description}}\n\n*Action Required:*\n- Review the completed documentation.\n- Ensure all necessary details are included and correct.\n- Finalize and prepare for release.\n\n*Reference Task:* {{issue.key}}"
}
Next, trigger the Automation rule for the task:
Here’s the result we get: