Use Easy Template Automation and the REST API to create standardized employee onboarding work in Jira when a new hire is created or reaches a defined onboarding status in an external business system.
System-agnostic integration: This use case applies to HRIS, ERP, CRM, recruitment, or other external systems that can send a webhook or HTTP request. The source system does not need to be specified.
Use case
When a new employee is marked as Hired, Ready for onboarding, or equivalent, the external system sends a POST request to Easy Templates. The configured template then creates the required Jira issues for HR, IT, Security, Facilities, and the employee’s manager.
Typical onboarding activities include account provisioning, equipment preparation, access requests, contract administration, workspace setup, and first-day coordination.
1. Prepare the template in Easy Issue Templates
-
Navigate to Manage Templates and select the Employee Onboarding template.
-
Open the Automation settings.
-
Enable automation and generate a new web request URL.
-
In the payload builder, select the required operation, such as Create Issues or Apply Template.
-
Select the target Jira project, or configure the request to provide the target
projectId. -
Define the variables used by the template, such as
employee_name,job_title,department,manager_name,start_date, andwork_location. -
Copy the generated web request URL and payload for use in the external system.
2. Configure the external system
-
Configure a workflow, automation rule, or integration action in the external system.
-
Set the trigger to a new employee record or a status change such as Hired or Ready for onboarding.
-
Configure an HTTP request with method
POST. -
Use the web request URL generated by Easy Templates.
-
Add the header
Content-Type: application/json. -
Map employee fields to the variables expected by the template.
{
"operation": "create-issues",
"projectId": "10025",
"variableValues": {
"employee_name": "{{employee.full_name}}",
"job_title": "{{employee.job_title}}",
"department": "{{employee.department}}",
"manager_name": "{{employee.manager_name}}",
"start_date": "{{employee.start_date}}",
"work_location": "{{employee.location}}"
}
}
Replace the example field mappings with the expression syntax supported by the source system. Variable names must match those configured in the Easy Templates template.
3. Optional Jira Automation routing
If the external system cannot call Easy Templates directly, route the event through a Jira Automation rule:
-
Create a Jira Automation rule with an Incoming Webhook trigger.
-
Configure the external system to send its event to the Jira webhook URL.
-
Add a Send web request action.
-
Set the destination to the Easy Templates web request URL.
-
Use POST, set the body type to Custom data, and map values from the incoming webhook.
{
"operation": "create-issues",
"projectId": "10025",
"variableValues": {
"employee_name": "{{webhookData.employee.name}}",
"job_title": "{{webhookData.employee.title}}",
"department": "{{webhookData.employee.department}}",
"manager_name": "{{webhookData.employee.manager}}",
"start_date": "{{webhookData.employee.start_date}}",
"work_location": "{{webhookData.employee.location}}"
}
}
4. Validate the integration
-
Use a test employee record or test event in the external system.
-
Confirm that the HTTP request is accepted successfully.
-
Verify that the onboarding epic, tasks, or subtasks are created in the target Jira project.
-
Confirm that employee-specific variables are populated correctly.
-
Check assignments, due dates, dependencies, and notifications generated by the template.
Recommended template variables
|
Variable |
Purpose |
|---|---|
|
|
Full name of the new employee |
|
|
Role or position title |
|
|
Organizational department or team |
|
|
Employee’s manager or reporting lead |
|
|
Planned employment start date |
|
|
Office, remote, or hybrid location |
Expected outcome
A single employee event creates a consistent, traceable onboarding workflow in Jira. Each responsible team receives clearly defined work, while employee-specific details are populated automatically from the external system.