The moment it happens
Turn forwarded emails into sorted Jira tickets
Emails or requests you forward become Jira tickets with a category, priority and short summary, and you hear about the risky ones.
- Runs
- The moment it happens
- Apps
- Jira
- AI
- Yes, uses the built-in AI allowance
- Access
- write (Create issues)
Send this to your assistant
Create a ClickRuntime automation: give me a link I can forward emails to. For each one, decide if it's phishing or which team it belongs to, create a ticket in project SEC with a priority and summary, and email me if it looks high risk.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
Employees forward suspicious emails to a security mailbox, and customers write to a general support address. Someone must read each message, decide what it is, open a Jira ticket, copy the text, set a priority and tell the team if it looks dangerous. When a phishing report sits in the queue over a weekend, others in the company may click the same link, and the security team learns about the campaign far too late.
When a forwarded email or request arrives with its subject and body, ClickRuntime has built-in AI decide the category, priority and a short summary, then creates a Jira issue with those fields filled in. If the AI judges the message to be high risk, it also emails you straight away.
Security teams, IT help desks and support teams that rely on a shared mailbox for incoming reports will find it useful.
What you get out of it
Dangerous reports are escalated at once
A message that looks like active phishing triggers an email to you immediately. The team can warn colleagues and block a sender within the hour, not on Monday morning. A short delay in a real phishing case can mean several more employees click.
Every report becomes a trackable ticket
Messages in a mailbox disappear from view when they are read. As Jira issues, they have owners, statuses and history, so nothing is lost and the team can measure how long reports take to handle.
Triage work is done before a human looks
The category, priority and summary are filled in, so the analyst opens a ticket that is ready to act on. Handling time per report falls, which matters when volume spikes.
Patterns across reports become visible
Because each report is categorized, ten reports of the same fake invoice show up as a cluster. Seeing that pattern helps the team recognize a campaign and respond to all of it, not just one email.
Employees get a reliable process
People who report suspicious messages see them handled consistently. When reporting leads to a quick response, employees keep doing it, which strengthens the company's early warning system. A reliable reporting loop is one of the cheapest security controls a company can have.
How it works
What happens, step by step
When you forward an email or a request form is sent in, ClickRuntime receives its subject and text.
AI reads it and picks a category, a priority and writes a short summary.
A Jira ticket is created with those fields filled in.
If AI marks it high risk, such as a phishing attempt, you get an email straight away.
Before it runs live
- Connect Jira
- Paste your automation's link into the other app's webhook settings
What you get
Build your own
Need it to work differently?
Your own rules
Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.
Any number of apps
One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.
AI where it helps
Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.
On a schedule or on each event
Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.
Changes you can ask for
- Act only on the items that match your own rules, and skip the rest
- Change what the AI looks for, or how it writes the result
- Add another app, for example also send it to Slack
- Combine it with other Jira steps into one automation
Under the hood
The code that runs this automation
from clickruntime import on_event, credentials, http, ai, notify
JIRA = "https://api.atlassian.com/ex/jira/your-cloud-id"
def jira(method, path, **kw):
resp = http.request(method, JIRA + path, headers={
"Authorization": f"Bearer {credentials.connection('jira', 'work')}", "Accept": "application/json"}, **kw)
resp.raise_for_status()
return resp.json() if resp.content else None
def search(jql, fields, limit=100):
return jira("POST", "/rest/api/3/search/jql", json={"jql": jql, "fields": fields, "maxResults": limit})["issues"]
def adf(text):
return {"type": "doc", "version": 1, "content": [{"type": "paragraph", "content": [{"type": "text", "text": text}]}]}
SCHEMA = {"type": "object", "properties": {
"category": {"enum": ["phishing", "IT", "HR", "Finance", "Security", "Other"]},
"priority": {"enum": ["Highest", "High", "Medium", "Low"]},
"summary": {"type": "string"}, "high_risk": {"type": "boolean"}}}
@on_event
def handle(event):
mail = event.json or {}
out = ai.generate(f"From: {mail.get('from')}\nSubject: {mail.get('subject')}\n\n{(mail.get('body') or '')[:4000]}",
system="Triage this forwarded email: is it phishing, or which team owns it? Give priority and a one-line summary.",
json_schema=SCHEMA, max_output_tokens=120).json
issue = jira("POST", "/rest/api/3/issue", json={"fields": {
"project": {"key": "SEC"}, "issuetype": {"name": "Task"}, "priority": {"name": out["priority"]},
"labels": [out["category"].lower()], "summary": f"[{out['category']}] {mail.get('subject', '')}"[:250],
"description": adf(f"{out['summary']}\n\nFrom: {mail.get('from')}")}})
if out["high_risk"]:
notify.email_me(f"High-risk email: {issue['key']}", f"{out['category']} · {out['priority']}\n{out['summary']}")
return {"issue": issue["key"], **out}FAQ
Common questions
What does the AI decide about each email?
Can I trust the AI to judge phishing correctly?
How do emails get into the automation?
What permissions does it need?
Does it need AI?
How many runs does it use?
Can I change how it works?
Related
You might also like
Turn monitoring alerts into Jira bugs, one per problem
Each new problem from your monitoring becomes a Jira bug, and repeat alerts are added as comments on the open issue.
See how it worksTriage new Jira tickets as they come in
New tickets get labels and a priority, and the reporter is asked for anything missing, like steps to reproduce.
See how it worksEmail release notes when a Jira version is released
When a version is released, you get readable release notes built from its resolved issues.
See how it worksKeep exploring
Set up “Turn forwarded emails into sorted Jira tickets” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.