Skip to content
Botopticon
Menu
Start free

RecipesSentry

Sentry errors

Free

Errors in 24 hours, the trend, unresolved issues, and new high or fatal events. Botopticon is not affiliated with Sentry.

Access

Sentry auth token, read events

Required. Env SENTRY_AUTH_TOKEN. Mode api_key.

  • event:read
  • project:read
  • org:read

In Sentry open Settings, then Auth Tokens, and create a personal token named Botopticon board with event:read, project:read, and org:read. Do not grant event:write or event:admin. Pick the org and projects you watch.

Botopticon never stores this key. Paste it into the agent, cron host, or MCP config. Revoke it any time.

Board

Sample · not your account.

Errors 24h

Sample · Events

86events

+22%

Updated just nownowSentry

Error trend

Sample · Last 7 days

86

min 38max 86

SunMonTueWedThuFriSat

Updated just nownowSentry

Unresolved

Sample · Open issues

14issues

Updated just nownowSentry

Command Tiles

Pro

Sample · not your account. The agent puts the ask on the board. You answer there. How Command Tiles work

  • Mute the TypeError

    Needs you

    Sample data

    Approval · Sentry

    Mute the checkout TypeError for 24 hours?

    fatal · checkout · TypeError on pay.

    Updated just nownowSentry

    Needs you

  • Treat this fatal?

    Needs you

    Sample data

    Question · Sentry

    A new fatal landed in the last hour. How should we treat it?

    Updated just nownowSentry

    Needs you

Tiles

  • Errors 24h
  • Error trend
  • Unresolved
  • New issuesneeds you
  • New issues. Set needs_you true when a new high or fatal issue appeared in the last hour.

Setup

  1. 01

    Mint a read-only Sentry key

    Create a key that can only read. Never grant write. Keep it in the env var named on this page, on the agent or cron host. Botopticon never stores this key. Paste it into the agent, cron host, or MCP config. Revoke it any time.

  2. 02

    Create a Botopticon token

    In the app, open Connection tokens and create one named after this board. Copy it. It is shown once. That token posts to Botopticon. It is not the source key.

  3. 03

    Paste the prompt into your agent

    Open the tab for Grok Bot, Muse, MCP, Cursor, Claude, or curl. Replace $BOTOPTICON_TOKEN. The agent fetches the source, maps the fields in the brief, and posts. Do not paste canned sample JSON as live data.

  4. 04

    Wait for the first live post

    These numbers are sample. They flip when your agent posts with the key. Each tile keeps the sample label until that tile is replaced.

Snippets

Same recipe, one tab per platform. Replace $BOTOPTICON_TOKEN with a connection token. The prompt fetches the source and posts. Do not paste the sample numbers as live data.

Grok Bot

Paste this into Grok Bot. Replace $BOTOPTICON_TOKEN with a Botopticon connection token. Connect MCP at https://www.botopticon.com/api/mcp if this client can. If it cannot, POST /api/ingest with curl instead.

Keep the Botopticon board "Sentry errors" current.

Source: Sentry.
You hold SENTRY_AUTH_TOKEN (Sentry auth token, read events). Botopticon never stores this key. Paste it into the agent, cron host, or MCP config. Revoke it any time.
In Sentry open Settings, then Auth Tokens, and create a personal token named Botopticon board with event:read, project:read, and org:read. Do not grant event:write or event:admin. Pick the org and projects you watch.
Scopes (read-only): event:read, project:read, org:read.

What to fetch and how to map it:
Read the current Sentry API docs. Objects: Organization, Project, Issue, Event.
Errors 24h: event count in the last 24 hours for the projects you watch.
Error trend: one point per day for the last 7 days.
Unresolved: issues that are unresolved (not archived or resolved).
New issues: newest issues as a feed. Label culprit and title. Set needs_you true when a new issue in the last hour is level high or fatal, or when you already treat it as a Seer/priority flag you can read. Do not invent a priority Sentry does not return.

Tiles:
- Errors 24h — bot Sentry, tile err-24h, type kpi.
- Error trend — bot Sentry, tile err-trend, type trend.
- Unresolved — bot Sentry, tile unresolved, type kpi.
- New issues — bot Sentry, tile new-issues, type feed. Set needs_you true when a new high or fatal issue appeared in the last hour. Sample shows needs_you true.

Post each tile to https://www.botopticon.com/api/ingest with header Authorization: Bearer $BOTOPTICON_TOKEN and Content-Type: application/json. Fields: bot, tile, type, title, subtitle, props, needs_you, ttl_seconds.
If you can call MCP, connect to https://www.botopticon.com/api/mcp with the same Authorization header and call post_tile once per tile. The arguments are those JSON fields.
Do not invent numbers. Do not post the same body again just to keep a tile fresh. Set ttl_seconds to how often the value really changes. A quiet tile should show as stale.
When needs_you is true, say who is asking, what it is about, and the ask.

FAQ

Which pane turns amber?
New issues. When a new high or fatal event lands, the agent sets needs_you. The 24h count and the trend stay meters.
Does this run on the Free plan?
Yes. Every tile in this recipe is a Free type. A Free workspace still has one board and 8 live tiles. Using this recipe adds the sample tiles to that board.
Does Botopticon store the Sentry key?
Botopticon never stores this key. Paste it into the agent, cron host, or MCP config. Revoke it any time.
How does the board stay current?
Your agent fetches the source and posts when a number changes. Set ttl_seconds to how often that work really happens, so a quiet tile shows as stale. Use a timer only for data no agent touches, and then at most daily. Never post the same content again just to keep a tile fresh.