Start with one real question and leave with a next step.
Start with the question in front of you, then use the guide to make the next decision easier.
Try saying
“I am trying to make this decision. What should I look at first?”
Start with context
Bring the smallest useful example.
Look for the signal
Separate what is known from what is assumed.
Take one step
Choose an action you can review.
Sentry Integration
What this connection is for
Bring production errors and crashes into product work, with AI helping you spot the bugs that affect customers.
How your data reaches Specky
Specky pulls from Sentry on a schedule. A sync runs when you open your workspace if the data is stale, and you can also start one by hand from the integration card.
Before you start
- Auth Token (Required) — Internal Integration auth token with
event:readandproject:readscopes. - Organization Slug (Required) — Your Sentry organization slug (visible in the URL).
- Project Slug (Required) — The Sentry project slug to pull issues from.
- Sentry Host (Optional) — Default is sentry.io. Change for self-hosted Sentry.
Setup
Open Settings → Integrations, find Sentry, and click Connect. The form will tell you what to paste and where to find it.
How to create an Auth Token
- Go to Sentry → Settings → Developer Settings → Internal Integrations
- Click "Create New Integration" and name it
Specky - Grant these permissions:
- Event: Read
- Project: Read
- Organization: Read
- Save, then copy the generated Internal Integration Token (starts with
sntrys_)
Finding your slugs
- Organization slug: the first path segment in your Sentry URL (
sentry.io/organizations/<org>/) - Project slug: visible on the project list page
What Specky does with Sentry data
- Pulls the latest unresolved issues and their most recent events
- An AI agent reviews every error stacktrace for severity, root cause, and PM-relevant impact
- Findings become Insights in your Product Graph, linked to originating issues
- Recurring patterns across errors feed into Opportunities and the Discovery Hub
Data synced
| Data | Used for |
|---|---|
| Unresolved issues | Bug tracking, user-impact scoring |
| Latest event per issue | Stacktrace, breadcrumbs, request context |
| User counts | Prioritization by affected-user count |
After connecting
New Sentry items appear in Discovery alongside your other sources. You can search them, ask questions about them, and cite them in product work without opening another tab.
Disconnecting Sentry removes the connection and the signals it brought in.
Troubleshooting
- Connected, but nothing appears. Open the Sentry card and run a sync by hand. If it errors, the card shows the reason.
- "Upgrade to connect". Your plan caps how many integrations you can connect at once, and a few providers are Scale-only. Settings → Usage shows where you stand.
- Credentials stopped working. Tokens expire and get revoked. Reconnect with a fresh one — your existing signals are kept.
See the Sentry integration page for what it's for and the questions people usually ask first, or the Integrations Overview for how integrations work in general.
Ready to apply this?
Start with your own product and keep the first read grounded. You'll create an account before the guided result so it can be saved to your workspace.