The moment it happens

Get alerted when an issue becomes Urgent

You hear straight away when an issue is created as Urgent or raised to Urgent.

Runs: The moment it happens
Apps: Linear
AI: Not needed
Access: read

Send this to your assistant

Create a ClickRuntime automation: email me immediately when any Linear issue is created with Urgent priority or changed to Urgent, with the title, team 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

When a production bug is filed as Urgent in Linear, the clock starts. Customers cannot check out, a data export is wrong or an integration is down. Linear's own notifications reach the assignee, but the assignee may be asleep, in a meeting or on leave, and the people who could step in, the on-call engineer or the engineering manager, never hear that it exists.

Whenever an issue is created with the Urgent priority, or raised to Urgent later, Linear notifies ClickRuntime. The automation checks that the priority is Urgent and that it just changed, and emails the people you list with the issue title, link and who filed it, so the right responder knows within moments.

It is meant for on-call rotations and small teams without a formal paging tool.

What you get out of it

The right responder hears quickly
An email to the on-call engineer and the manager means that an urgent issue never depends on one person noticing. Time to first response falls, and so does time to resolution.
Escalations are caught too
Issues often start as Medium and are raised to Urgent after a customer complains. Watching for the change catches those cases that creation-only alerts would miss. Customers rarely say how serious something is up front.
Customers affected sooner get help sooner
Every minute of delay on an urgent bug is a minute of lost sales or frustrated users. Shortening the gap between filing and response limits the damage. Time saved here is measured in revenue.
A record of urgent incidents builds
Each email is a timestamp that shows when the team learned about a problem. During a review, you can compare it with the fix time to see how the response went.
Priority is taken seriously
When marking an issue Urgent reliably reaches people, requesters use the label carefully. The team can trust that Urgent means urgent, instead of ignoring it as noise. That trust keeps the priority field meaningful over the long run.

How it works

What happens, step by step

When an issue changes in Linear, ClickRuntime checks whether its priority has just been set to Urgent.
Issues that were already Urgent, or changed in other ways, are ignored, so you only hear about it once.
You get an email with the issue ID, title, team and a link to open it in Linear.

Before it runs live

Connect Linear
Paste your automation's link into the other app's webhook settings

What you get

RunsThe moment it happens

Get alerted when an issue becomes Urgentjust nowSucceeded

Email · Urgent issueUrgent: ENG-503 Payments failing for EU cards Team: Platform · linear.app/northwind/issue/ENG-503

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 Linear 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.

urgent_bug_alert.pyexample

from clickruntime import on_event, notify

@on_event
def handle(event):
    body = event.json or {}
    issue = body.get("data", {})
    if body.get("type") != "Issue" or issue.get("priority") != 1:
        return {"sent": False}
    changed = "priority" in (body.get("updatedFrom") or {})
    if body.get("action") != "create" and not changed:
        return {"sent": False}
    team = (issue.get("team") or {}).get("name", "")
    notify.email_me(
        f"Urgent: {issue.get('identifier')} {issue.get('title')}",
        f"Team: {team}\n{body.get('url')}",
    )
    return {"sent": True}

FAQ

Common questions

Does it trigger if someone re-saves an issue that is already Urgent?

No. The automation checks that the priority actually changed to Urgent, so editing a title or adding a comment to an issue that was already urgent does not send another email. Only new urgent issues and upgrades to Urgent do. The email lists the issue title and a link.

Can it call or text instead of email?

It sends email by default. If your team uses a paging tool or a phone-based service, an email address or webhook provided by that service can be used as the destination. Check how your paging service accepts alerts.

Can I limit it to certain teams or labels?

Yes. A common version only watches bugs, using a label such as Bug, or only a production team. The filter is added before the email step, so urgent feature requests or internal tasks do not wake anyone.

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 for each event the app sends.

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.

The moment it happens