The moment it happens

Get a Slack message for every new Linear issue

Each new issue in your team shows up in Slack with its title, priority, assignee and link.

Runs: The moment it happens
Apps: Linear
AI: Not needed
Access: read (webhook creation requires admin)

Send this to your assistant

Create a ClickRuntime automation: post to #eng in Slack whenever a new Linear issue is created in team ENG, with the title, priority, assignee 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

Engineering teams that keep their work in Linear still lose time to the question of what was just filed. A new issue is created, assigned to someone who is heads-down in code, and sits unseen until the next standup. For teams where issues come from customers, QA or other departments, a few hours of silence can be the difference between a quick fix and an unhappy requester.

When an issue is created in Linear, a webhook delivers it to ClickRuntime. The automation checks the team it belongs to, ignores other teams, and posts the title, assignee and priority to Slack. The right people see the issue as it appears, in the channel where they already chat.

It is a lightweight way to keep a team aware of its own incoming work.

What you get out of it

Assignees notice new work immediately
Someone who is assigned an issue gets a visible nudge in Slack rather than waiting for Linear's own notification to be noticed. Work starts sooner and fewer things wait unseen.
The team sees the stream of incoming work
A channel of new issues gives everyone a feel for what is coming in and how much. It helps a team spot a surge of bugs after a release without opening a report.
Priority is visible without opening Linear
Showing the priority in the message lets an engineer decide whether to interrupt what they are doing. An urgent issue is obvious, and a low one can wait for the next planning pass.
Only your team's issues appear
Filtering by team keeps the channel relevant. The mobile team does not have to read backend issues, and each team keeps its own quiet, useful feed. Each team keeps a feed that is worth reading.
Requesters see their issue was received
Teams that file issues for each other can watch the channel and confirm it landed. That prevents the follow-up message asking whether anyone saw the ticket. It keeps cross-team work moving without chasing.

How it works

What happens, step by step

When someone creates a new issue in Linear, ClickRuntime is notified straight away.
It checks the issue belongs to the team you chose and ignores the rest.
It posts a message to your Slack channel, such as #eng, with the issue ID, title, priority and assignee.

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 a Slack message for every new Linear issuejust nowSucceeded

Slack · #engNew issue ENG-412: Checkout button unresponsive on Safari Priority: High · Assignee: Unassigned

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.

new_issue_alerts.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 body.get("action") != "create":
        return {"posted": False}
    if (issue.get("team") or {}).get("key") != "ENG":
        return {"posted": False}
    assignee = (issue.get("assignee") or {}).get("name", "Unassigned")
    notify.slack(
        f"New issue {issue.get('identifier')}: {issue.get('title')}\n"
        f"Priority: {issue.get('priorityLabel')} · Assignee: {assignee}\n{body.get('url')}",
        channel="#eng",
    )
    return {"posted": True, "id": issue.get("identifier")}

FAQ

Common questions

Can I get alerts for several teams in different channels?

Yes. The team is part of each Linear event, so alerts can be routed by team, with each team's issues going to its own Slack channel. A single automation can handle all of them, or you can set up one per team.

Does it post when an issue is edited or only when created?

Only when it is created. Edits, comments and status changes are different events in Linear. If you want to hear about priority changes or reassignments as well, those can be added, but they will make the channel noisier.

Will it work for issues created through the API or by another integration?

Yes. Linear raises the same creation event no matter how the issue was made, whether through the interface, the API or a connected tool. Issues from other automations and integrations will appear in Slack in the same way.

What permissions does it need?

read (webhook creation requires admin). 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