On a schedule

Get yesterday's new Sentry issues each morning

A weekday email listing issues first seen in the last 24 hours, busiest first, with event counts.

Runs: On a schedule
Apps: Sentry
AI: Not needed
Access: project:read, event:read

Send this to your assistant

Create a ClickRuntime automation: every weekday at 9am, email me the Sentry issues first seen in the last 24 hours in my web-frontend and api projects, sorted by event count.

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 developer who returns from a weekend to find three hundred unread Sentry notifications will do what most people do: stop reading them. Issue alerts fire per event, so a single noisy bug produces dozens of emails, and a quiet but serious new error hides among them. The team learns about a regression from a customer support ticket on Tuesday, though the error first appeared on Sunday night when a release went out.

Every morning the automation asks Sentry for issues whose first seen time is within the last 24 hours, sorts them by how many events they produced, and emails you a list with titles, counts and links. New problems from yesterday are in one message, ordered by impact. Engineering managers and on-call developers use it as a quick start-of-day review of what broke.

What you get out of it

New errors reviewed in one place
Instead of triaging a stream of individual alerts, you open one email that lists only issues born yesterday. A five-minute scan replaces an inbox of notifications. Forty alert emails collapse into a ranked list you can read before the first coffee is finished.
Highest-impact bugs come first
Sorting by event count puts the error hitting thousands of users above the one that fired twice. Developers fix what matters most first, which cuts the damage from a bad release.
Regressions caught the next morning
An error introduced by yesterday's deploy appears in the digest the following day. Reverting or patching within a day is far cheaper than discovering the same bug in a support queue a week later.
Quiet teams still stay informed
Not everyone is subscribed to every project's alerts. A daily list gives managers and product owners visibility into quality without joining a noisy alert channel. A product owner can read the list and ask the right question without joining a noisy alert channel.
A daily record of quality
Saved digests show how many new issues appeared each day. Looking back over a month tells you whether releases are getting more stable or if the team is shipping more bugs.

How it works

What happens, step by step

Every weekday at 9, ClickRuntime asks Sentry for issues first seen in the last 24 hours.
It sorts them by how many times each error happened, busiest first.
You get an email listing each issue with its project and event count.

Before it runs live

Connect Sentry

What you get

RunsOn a schedule

Get yesterday's new Sentry issues each morningtoday, 9:00Succeeded

Email · New Sentry issues[api] TypeError: Cannot read properties of undefined (reading 'id') (312 events)

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

Run it at a different time, more or less often, or only on weekdays
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_a_daily_digest_of_new_issues.pyexample

from clickruntime import on_trigger, credentials, http, notify

SENTRY = "https://sentry.io/api/0"
ORG = "acme"

def sentry(path, **params):
    resp = http.get(f"{SENTRY}{path}", params=params, headers={"Authorization": f"Bearer {credentials.secret('SENTRY_AUTH_TOKEN')}"})
    resp.raise_for_status()
    return resp.json()

PROJECTS = ["web-frontend", "api"]

@on_trigger
def run(event):
    issues = []
    for project in PROJECTS:
        for i in sentry(f"/projects/{ORG}/{project}/issues/", query="firstSeen:-24h", statsPeriod="24h"):
            issues.append((int(i["count"]), f"[{project}] {i['title']} ({i['count']} events)\n  {i['permalink']}"))
    lines = [line for _, line in sorted(issues, reverse=True)]
    notify.email_me(f"{len(lines)} new Sentry issues", "\n".join(lines) or "No new issues.")
    return {"issues": len(lines)}

FAQ

Common questions

What counts as a new issue in Sentry?

An issue Sentry created for the first time within the window, identified by firstSeen. A recurring old error that spiked is not new, though a regression of a resolved issue may appear depending on your Sentry settings.

Can the digest cover several projects?

Yes. The query can span all projects in an organization or be limited to some of them. If you want separate lists for each team, it can send one email per project instead of one combined email.

Which Sentry token do I need?

An auth token with read access to issues for the organization, created in Sentry settings. Read-only is enough, since nothing is changed. ClickRuntime stores it as a secret, so it never appears in the email or in the run log.

What permissions does it need?

project:read, 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 each time it runs (on a schedule). Checks that find nothing to do 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.

Weekly