The moment it happens

Post brand-new Sentry errors to Slack

When Sentry sees an error for the first time, a channel gets its title, culprit and a link to the issue.

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

Send this to your assistant

Create a ClickRuntime automation: whenever Sentry records a new issue in my api project, post the title, culprit and issue link to #errors in Slack.

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

Some errors matter immediately: a checkout exception on the first minutes after a deploy, a new crash on login, a payment library failing. Sentry catches them, but a team that only sees the dashboard when it opens it learns about the problem from users. Email alerts go to whoever is on the project and are easily lost, and a developer who is heads-down in code may not see an email for an hour while customers are failing to pay.

When Sentry sees an issue for the first time, it sends an event to the automation, which formats the title, culprit and a link, and posts it to a Slack channel. The alert arrives the moment Sentry creates the issue. Engineering teams use it as a shared, visible notice of brand-new problems, so the right person can start work immediately.

What you get out of it

Fixes start within minutes
A new error in Slack reaches a whole team already watching the channel. Someone picks it up, and the customer-facing problem is shortened from hours to minutes. A checkout exception reported within minutes can be rolled back before most of the day's buyers reach it.
Only brand-new problems interrupt
Alerts are limited to first-seen issues, so the channel does not fill with repeats of a known bug. People keep paying attention because every message is something they have not seen before.
The culprit is in the message
The post shows the title and culprit, the function or file responsible. A developer can often tell whose code is involved just by reading the notice and assign it directly.
Deploy problems are seen at once
A new error right after a release strongly suggests the release caused it. The team can roll back or patch quickly, before the issue reaches the rest of the user base.
Everyone shares the same picture
Developers, support and product see the same alert at the same time. Support can warn customers and product can decide on communication while engineers work on the fix. Support, product and engineering read the same message together, so nobody relays a half-remembered version to anyone else.

How it works

What happens, step by step

When Sentry sees an error for the first time, it tells ClickRuntime straight away.
ClickRuntime picks out the error title, the code where it happened and a link to the issue.
It posts them to your Slack channel.

Before it runs live

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

What you get

RunsThe moment it happens

Post brand-new Sentry errors to Slackjust nowSucceeded

Slack · #errorsNew Sentry issue: KeyError: 'customer_id' app.billing.sync_invoice https://acme.sentry.io/issues/4821…

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

get_alerted_on_new_issues_sentry.pyexample

from clickruntime import on_event, notify

@on_event
def handle(event):
    if event.header("Sentry-Hook-Resource") != "issue" or event.json.get("action") != "created":
        return {"skipped": True}
    issue = event.json["data"]["issue"]
    if issue["project"]["slug"] != "api":
        return {"skipped": issue["project"]["slug"]}
    notify.slack(f"New Sentry issue: {issue['title']}\n{issue.get('culprit', '')}\n{issue['web_url']}", channel="#errors")
    return {"issue": issue["id"]}

FAQ

Common questions

Is this the same as Sentry's own Slack integration?

Sentry has its own integration with rules you configure inside Sentry. This version is set up through ClickRuntime, which lets you control the message layout and combine it with other steps, such as adding context from another system.

How do I connect Sentry to this automation?

In Sentry, create an internal integration or a webhook for issue events and paste the link ClickRuntime provides. Sentry then posts an event whenever an issue is created, and the automation formats and forwards it to Slack.

Can I send high-severity issues to a different channel?

Yes. The event includes the issue level, such as error or fatal, and the project name. The automation can route fatal issues or issues from a production project to an urgent channel and the rest to a quieter one.

What permissions does it need?

event: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.

On a schedule