Every 5 minutes

Get pinged about Highest and Blocker issues

Within minutes of a top-priority issue being created, you get its summary, reporter and link.

Runs: Every 5 minutes
Apps: Jira
AI: Not needed
Access: read

Send this to your assistant

Create a ClickRuntime automation: Slack me within 5 minutes when a new issue with priority Highest or Blocker is created in project ABC, with the summary, reporter and link.

Paste it into your assistant. It tells you what it will send or change before it runs live.

Add to ChatGPT Add to Claude

First time? Adding ClickRuntime to your assistant takes about two minutes.

Why use it

Why teams use this automation

A customer on the enterprise plan reports that exports are failing, and the support engineer files it in Jira at Highest priority. Most of the engineering team does not look at Jira during the day. They are in code, in meetings, or in Slack, and the ticket sits in the queue while the customer refreshes their inbox. Two hours go by before the on-call developer happens to open the board, and the account manager has been apologizing without any information to share.

Every 5 minutes, ClickRuntime runs a JQL search for issues created in the last 10 minutes with priority Highest or Blocker, skips any key it has already reported, and posts a message with the summary, the reporter and a link. The overlap between the window and the schedule means nothing slips through a gap between runs.

It is for engineering and support teams where a small number of issues really are urgent, and everyone else should not be bothered.

What you get out of it

Urgent problems reach people in minutes
The one ticket that matters stands out from fifty routine ones when it appears in a channel people watch. Developers begin work within minutes instead of at the next time someone checks the board.
Customers are updated sooner
Account managers can tell a customer that engineering is already looking at the problem. A prompt, specific message does far more for trust than a long silence followed by a late apology.
Priority labels start to mean something
When setting Highest triggers a visible alert, people use the label with care. That reduces the habit of marking everything urgent, and keeps the top priority for incidents that need immediate action.
Blockers do not wait for stand-up
A blocker created in the afternoon can easily wait until the next morning's meeting. Seeing it immediately lets the team decide the same hour whether to pause other work and unblock a release.
Alerts are not repeated
Issues that were already reported are remembered by key, so one ticket produces one message. A quiet, reliable channel is one people keep unmuted, which is the whole point of an alert.

How it works

What happens, step by step

Every five minutes, the automation checks Jira for new issues with Highest or Blocker priority.
It skips any issue it has already posted.
Each one is posted to your Slack channel with its summary, reporter and link.

Before it runs live

Connect Jira

What you get

RunsEvery 5 minutes

Get pinged about Highest and Blocker issuestoday, 9:00Succeeded

Slack · #dev:rotating_light: Blocker: ABC-455 Payments failing for EU cards Reported by Jordan Lee · https://your-domain.atlassian.net/browse/ABC-455

Build your own

Need it to work differently?

This template is a starting point. Copy the prompt and change it, or describe a different automation from scratch, with your own conditions, more apps or an AI step. Your assistant writes it, tests it and runs it on ClickRuntime.

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
Add an AI step, for example to summarize, sort or draft a reply
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

This is the Python script that runs each time the automation starts. Your AI assistant writes it for you when you send the prompt, and you allow each step in your assistant. To change how the automation works, describe the change to your assistant and it updates the script for you. For every function it can use, see the script reference.

high_priority_issue_alert.pyexample

from clickruntime import on_trigger, credentials, http, state, notify, report_fetched

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"]


@on_trigger
def run(event):
    issues = search("project = ABC AND priority in (Highest, Blocker) AND created >= -10m", ["summary", "reporter", "priority"], 50)
    seen = set(state.get("seen") or [])
    new = [i for i in issues if i["key"] not in seen]
    report_fetched(len(new))
    if not new:
        return {"posted": 0}
    for i in new:
        f = i["fields"]
        notify.slack(f":rotating_light: {f['priority']['name']}: {i['key']} {f['summary']}\n"
                     f"Reported by {f['reporter']['displayName']} · https://your-domain.atlassian.net/browse/{i['key']}",
                     channel="#dev")
    state.set("seen", sorted(seen | {i["key"] for i in new})[-200:])
    return {"posted": len(new)}

FAQ

Common questions

Why does the search look back 10 minutes if it runs every 5?

The overlap guards against missing issues created just as one run ends and the next begins, or when Jira is slow to index a new issue. Duplicates are avoided because already reported issue keys are skipped.

What if our priority names are different from Highest and Blocker?

Jira projects can use custom priority schemes. Give your AI assistant the names you use, such as P0 and P1 or Critical, and the search will match those instead. The alert only works with priority values that exist in your Jira.

Does it notice when an existing issue is raised to Highest?

The search looks for issues created recently, so an old issue whose priority is raised later would not be caught. If escalations matter to you, ask for the search to also consider priority changes within the same window.

What permissions does it need?

read. Nothing else in your accounts is used.

Does it need AI?

No. It runs without AI, so it doesn't use your plan's AI allowance.

How many runs does it use?

One run each time it checks. Checks that find nothing new and stop right away aren't counted.

Can I change how it works?

Yes. Describe the change to your AI assistant, for example a different schedule, channel or filter. It updates the automation, tests it and tells you what changed.

On a schedule