Sentry integration without code: issues, events and releases

The Sentry integration in nana800 reads issues and events, changes issue status, assigns owners and works with releases, projects and teams, with no code. The scheme starts on every new error when Sentry sends an alert to a webhook trigger, or the block fetches unresolved issues on a schedule. Each request to Sentry costs $0.002, and your balance is topped up to $3.50 for free every month.

Build it in the builder
  • Block run: $0.002
  • Free every month: $3.50
  • No card needed

What you can do

  • Fetch unresolved issues of a project or a whole organization with a Sentry filter, such as level:error or environment:production
  • Read one issue or one error event with all its details
  • Mark an issue as resolved, unresolved or ignored and assign an owner
  • Create, update and delete releases, for example after shipping a new version
  • List, create and change projects, teams and organizations
  • Work with sentry.io, the us and de regions and your own Sentry server

Blocks in the builder

  • Sentry request

    Action · $0.002 per run

    Pick a section (event, issue, organization, project, release, team) and an action (get, getAll, create, update, delete). One record comes in data, a list in records, and the Sentry error text in error_message.

How to set it up

  1. 1

    Create a token in Sentry

    In Sentry open Settings, Developer Settings, Organization Tokens (or Personal Tokens) and create a token. Reading issues needs event:read, changing them needs event:write, and deleting needs event:admin.

  2. 2

    Add the Sentry.io Request block

    Create a scheme, add the button trigger and the Sentry.io Request block. Paste the token and pick the server: sentry.io fits every cloud account, and for your own server choose self_hosted and enter its address.

  3. 3

    Get the list of issues

    Choose the issue section and the getAll action, then enter the organization slug from the Sentry address, for example my-company. The project is optional. Put a filter such as is:unresolved level:error into the search query, or leave it empty to get unresolved issues.

  4. 4

    Pass the issues on

    Add the Telegram message send block after the Sentry block and put the data you need from its result into the text. Turn the scheme on, press the button trigger and check the message. If Sentry returned an error, its text is in error_message.

  5. 5

    Choose what starts the scheme

    To react to every new error, replace the button with a webhook trigger using the POST method and put its address into the Sentry alert settings. To fetch issues on a schedule, use the time internal trigger. Keep the scheme on.

Popular connections

  • Sentry + Telegram

    Get new Sentry errors in Telegram: the title, the project and a button that opens the issue. No code and no server, free balance every month, no card needed.

Frequently asked questions

Each block request to Sentry costs $0.002. An enabled scheme costs $0.0042 per hour. Your balance is topped up to $3.50 for free every month, no card needed. A scheme kept on around the clock for a month spends most of that on scheme hours.

The Sentry.io Request block does not watch for errors itself, it runs a request when the scheme starts. There are two ways. Sentry sends an alert to the address of a webhook trigger once you put that address into its settings. Or the time internal trigger starts the scheme regularly and the block fetches unresolved issues.

event:read to read issues and events, event:write to change issues, event:admin to delete them. Working with projects, teams, releases and organizations needs scopes for those sections too.

Yes. Choose the self_hosted server and enter the address of your Sentry with https, for example sentry.mycompany.com. The block adds the /api/0 part itself. The server must be reachable from the internet.

The getAll action returns up to 1000 records, or up to 100 events, and the block loads the pages itself. With the count field empty you get one page of the Sentry answer: usually 100 records, or 10 events. If there are more, the result has is_truncated: true.

No, events (the event section) are read only: one by ID or a list of project events, which needs the organization and project slugs. Status changes, owner assignment and deletion work on the issue itself, in the issue section.

Build your first scheme for free

Sign-up is free and needs no card. Every month the balance is topped up to $3.50 for free, enough for about 3,500 runs of basic blocks.

Build it in the builder