Skip to main content

​
Getting Started

Connect your Sentry organization to give Blocks access to error reports and issue data. Once connected, Blocks can look up errors, read stack traces, and pull error context when working in GitHub, Slack, and other platforms.
Blocks cannot be invoked from Sentry. Sentry is used as a data source only — Blocks reads from your Sentry organization to provide context when handling requests made elsewhere.

​
Setting Up the Sentry Integration

Connect Sentry via Settings > Integrations > Sentry in the Blocks dashboard. A single OAuth flow connects your Sentry organization — no per-user account linking is required.

​
What Blocks Can Do

Once your Sentry organization is connected, Blocks can:
  • Look Up Error Reports: Find and read Sentry issues including error messages, frequency, and affected users
  • Read Stack Traces: Inspect stack traces and exception details to understand the root cause of errors
  • Reference Open Issues: Pull relevant Sentry issues into context when debugging or implementing fixes
  • Provide Richer Context: Use Sentry error data to give more accurate, targeted answers when you make requests in GitHub or Slack

​
Using Sentry in Requests

After connecting your Sentry organization, you can ask Blocks to reference error data from any supported platform: 
@blocks investigate the TypeError in the checkout flow that Sentry has been reporting

@blocks fix the error in Sentry issue PROJ-1234

@blocks look at the recent Sentry errors in the payments service and suggest what might be causing them

@blocks implement a fix for the null pointer exception showing up in Sentry this week
Blocks will automatically search your Sentry organization for relevant issues when it would help complete a request. You can also explicitly reference a Sentry issue ID or describe the error you want Blocks to look up.

​
Best Practices

  • Reference Issue IDs: Including a Sentry issue ID in your request helps Blocks find the exact error quickly
  • Describe the Error: If you don’t have an issue ID, describing the error message or affected area helps Blocks locate relevant issues
  • Combine With GitHub: Sentry works best alongside GitHub, where Blocks can investigate an error and immediately open a PR with a fix
  • Keep Environments Organized: If you have multiple Sentry projects or environments, mention which one is relevant when making a request

​
Next Steps

New to Blocks? Check out the Getting Started guide to learn the basics. Learn more about: