Automatically assign Jira Service Management reporter from forwarded emails
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 9 nodes and runs on Jira events (jira:issue created). Along the way it connects Jira Software.
How it runs
Trigger: On Jira events (jira:issue created).
- Filter Forwarding Emails (If): checks a condition and branches into true / false
- Set Description Variable (Edit Fields (Set)): sets 1 field: description
- Parse Details From Description (Code): runs custom JavaScript code
- Search for Existing Customer (HTTP Request): calls an HTTP API
- If: checks a condition and branches into true / false
- Update Reporter (Existing Customer) (Jira Software): update
- Create Customer (HTTP Request): calls an HTTP API (POST)
- Update Reporter (New Customer) (Jira Software): update
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (6)
- If
n8n-nodes-base.if - Edit Fields (Set)
n8n-nodes-base.set - Code
n8n-nodes-base.code - Jira Software
n8n-nodes-base.jira - HTTP Request
n8n-nodes-base.httpRequest - Jira Trigger
n8n-nodes-base.jiraTrigger
From the author
Automatically Assign Jira Service Management Reporter from Forwarded Emails This workflow solves a common problem in Jira Service Management: when an email is forwarded to create a ticket, Jira often sets the forwarding system (e.g., [email protected])…