Early access

Turn Sentry Errors Into Linear Issues

For the error list nobody owns. DuckyHelper learns Sentry and Linear once, groups the week's errors by cause, finds issues that already exist, and files the rest with the stack trace and how many people it hits.

YOU SAY

“Group this week's top Sentry errors and file or update Linear issues with stack traces and user counts.”

Press fn (Ctrl+Shift+Space on Windows and Linux) and ask out loud.

DUCKYHELPER DOES

01
Turn Sentry and Linear into APIs it can callIt watches each site's own requests once and saves them as actions. Kept on your device.listIssues(range, sort)searchIssues(text)createIssue(team, fields)addComment(id, text)
02
Pull the week's top errors
03
Group them by cause
04
Find Linear issues that already match
05
Update those, and file the rest with the stack trace

You getA backlog that matches reality. Every real error has one issue, with its impact attached. Next week it's one call per site.

Turn Sentry Errors Into Linear Issues

A run, drawn from this page · early access on Mac

WHERE IT ASKS FIRST

Nothing to send, so it runs straight through.

Nothing in this job sends a message or pays for anything, so it works through to the end and tells you when it's done. If a step ever would, it's built to stop and ask you first.

If it hits a sign-in, you sign in yourself. It's built not to type your passwords or card numbers.

Sign in to Sentry to keep going

DuckyHelper is built not to type your passwords or card numbers. Sign in yourself, then it picks up where it stopped.

MAKE IT ALWAYS ON

Do it once. Then let it repeat.

When it's done, it offers to keep doing it: every Monday at 9:00 AM. Each run goes through the API it learned the first time, so it's quick, and it's still built to ask before it sends or pays.

Always-on automations are in early access on Mac.

Make this automatic?Schedule

Turn Sentry Errors Into Linear Issues

WhenEvery Monday at 9:00 AM

DoesDuckyHelper groups the week's top Sentry errors, updates matching Linear issues and opens new ones with the stack trace.

ThenTells you when it's done

FAQ

Before you ask it.

What do I say?

Press fn (Ctrl+Shift+Space on Windows and Linux) and ask out loud, in your own words, like "Group this week's top Sentry errors and file or update Linear issues with stack traces and user counts."

Why is the second time faster?

The first time, it writes small JavaScript tools for Sentry and Linear and builds an API from each site's own buttons, forms and requests. After that it calls them directly, so the job runs in one go instead of click by click. It costs less and breaks less.

Will it send anything without me?

It's built to ask first before it sends a message or pays for anything, and to wait for your yes. It may not recognize every send or payment, so keep an eye on tasks that involve messages or money. It's built not to type your passwords or card numbers: you sign in yourself, and it picks up from there.

Why not just do it by hand?

Sentry fills up faster than anyone can triage, and the same bug gets filed three times.

Can it keep doing this on its own?

Yes. When it's done it offers to make it automatic (every Monday at 9:00 AM). Each run goes the same way and is still built to ask before it sends or pays.

Can I use this today?

Doing jobs in your apps is in early access on Mac. Talking to DuckyHelper, and having it see your screen and draw on it, works today on Mac, Windows and Linux.

MORE JOBS LIKE THIS

Every use case →