How to Automate Email Phishing Tickets in Jira?
Description
Protect your inbox and speed up phishing review with an email triage flow that watches Gmail and Outlook, uses AI to judge risk, and opens Jira tickets with proof. It fits IT and security teams that need fast, consistent handling of suspicious messages.
New emails arrive through two triggers that check Gmail and Outlook every minute. Outlook headers are pulled from Microsoft Graph, then a code step formats them for clear reading. The email body is turned into a text file and also rendered as an image using an HTML to image service. Both the HTML body and the headers go to OpenAI for analysis. A decision step routes results into two Jira paths. Malicious and benign reports are logged as separate issue types, and the workflow uploads the screenshot and the body file to the ticket. The Jira issue ID is tracked to keep all uploads linked.
Setup needs accounts for Gmail, Microsoft Outlook, Jira, OpenAI, and the HTML to image service. Expect review time per email to drop from many minutes to just a few, with cleaner evidence for your records. Use it for a phishing mailbox, for employee reports, or for a managed service team that supports multiple domains.
Tools Required
What this workflow does?
- Real time email capture from Gmail and Microsoft Outlook every minute
- Retrieves and formats Outlook internet message headers for clear analysis
- Builds a plain text file of the email body for easy reading and search
- Creates a visual screenshot of the HTML email using an HTML to image service
- Uses OpenAI to analyze HTML and headers for phishing risk with JSON output
- Routes results into malicious or benign paths using a decision step
- Creates Jira issues in the right project and issue type with rich descriptions
- Uploads both the screenshot and the text body file to the Jira ticket and tracks the issue ID
What are the benefits?
- Reduce manual review from 15 minutes to 2 minutes per email
- Automate up to 80 percent of phishing triage steps
- Improve evidence quality by attaching clear text and images
- Connect Gmail and Outlook to Jira in one flow
- Handle up to 10 times more reports without extra staff
How to set this up?
- Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
- You'll need accounts with Gmail, Microsoft Outlook, Jira Software Cloud, OpenAI and HTML/CSS to Image. See the Tools Required section above for links to create accounts with these services.
- Open the Gmail Trigger node, choose Credential to connect with, click Create new credential, and follow the on screen steps to sign in with Gmail OAuth2.
- Open the Microsoft Outlook Trigger node, choose Credential to connect with, click Create new credential, and complete the Outlook OAuth2 sign in. Ensure your account has permission to read messages.
- Open the Analyze Email with ChatGPT node, create a new OpenAI credential, and paste your API key from your OpenAI account API page. Name the credential clearly.
- Open the Jira ticket nodes, create a new Jira Software Cloud credential, and enter your site domain, email, and API token from your Atlassian account. Test the connection.
- Open the Screenshot HTML and Retrieve Screenshot nodes. Create a new Basic Auth credential for HTML/CSS to Image using your hcti.io username and API key from the dashboard.
- In the Gmail Trigger and Outlook Trigger nodes, keep polling every minute or adjust to your needs. Optionally add filters to limit messages you want to scan.
- Confirm the Retrieve Headers step returns internet message headers. If empty, check Outlook permissions and that the Prefer header is set to text.
- In the Jira nodes, pick the correct project and issue type. Update summary and description fields if your team needs different wording.
- Review the prompt in the Analyze Email with ChatGPT node. Adjust risk rules or output fields if your team uses a specific format.
- Send a test email to Gmail and another to Outlook. Run the workflow and check that the screenshot, text file, and Jira issue are created. Confirm the branch matches the AI decision.
- If the screenshot step fails, verify the HTML body variable and your HTML/CSS to Image credentials. If Jira uploads fail, check project permissions and attachment size limits. If AI calls fail, confirm your OpenAI key and model settings.
Need help or want to customize this?
Ask in the Futurise Pro Community.
Similar Templates
These templates were sourced from publicly available materials across the web, including n8n’s official website, YouTube and public GitHub repositories. We have consolidated and categorized them for easy search and filtering, and supplemented them with links to integrations, step-by-step setup instructions, and personalized support in the Futurise community. Content in this library is provided for education, evaluation and internal use. Users are responsible for checking and complying with the license terms with the author of the templates before commercial use or redistribution.Where an original author was identified, attribution has been provided. Some templates did not include author information. If you know who created this template, please let us know so we can add the appropriate credit and reference link. If you are the author and would like this template removed from the library, email us at info@futurise.com and we will remove it promptly.
