Sentry Connector

Who can do this: Owners, Admins, and Editors can add and manage project connectors. See Roles and Permissions for details.

Connect your Sentry account and build tools around your production health. Error triage boards, release quality dashboards, alert routing panels, and observability views that turn monitoring data into team workflows.

What you can do

Access your monitoring data:

• View issues with error messages and stack traces
• Browse releases with deployment history
• Check performance metrics and crash rates
• See alert configurations and incident history

Build observability tools:

• Error triage boards with workflow columns
• Release quality dashboards comparing deployments
• Alert routing panels for incident management
• Weekly health digests for stakeholders

Improve team workflows:

• Surface issues that need attention first
• Track regressions across releases
• Route alerts to the right channels
• Give stakeholders production visibility without Sentry access

How to connect

Sentry uses a single connection through the connector. Once connected, Sticklight can read your projects, issues, releases, and alert data.

Connect the connector

You can connect from chat or from your project settings.

From chat:

“Connect my Sentry account”

From project settings: Open Settings, go to Connectors, and select Sentry.

When you start the connection:

1. Click Connect Account.
2. Log in to Sentry when the authorization window opens.
3. Select the organization you want to connect.
4. Review the permissions Sticklight is requesting.
5. Click Authorize to complete the connection.

Once connected, Sticklight can access your Sentry data while you build and your published app can display production health information.

Available data

Once connected, your project can access:

Data	What you get
Issues	Error messages, stack traces, affected users, frequency
Releases	Version names, deployment times, commit data
Performance	Crash-free rates, session data, error counts per release
Alerts	Alert rules, configurations, trigger history
Projects	Project names, environments, team assignments

Common use cases

Error triage board

A Kanban-style board for managing production issues. Columns for New, Investigating, and Resolved. Cards show error message, affected users, and when it was last seen. Assign and move issues through your workflow.

“Build an error triage board from my Sentry project with columns for New, Investigating, and Resolved. Show error message, user count, and last seen on each card.”

Connection needed: Connector

Release quality dashboard

A side-by-side comparison of your recent deployments. See new errors introduced per release, crash-free session rates, and regressions highlighted. Know the health of each release before issues pile up.

“Create a release quality dashboard showing my last 5 Sentry releases with new error count, crash-free rate, and a comparison chart highlighting regressions.”

Connection needed: Connector

Alert routing panel

A configuration view for mapping alert severities to destinations. See which alerts go to which Slack channels, test your routing, and confirm the right team gets notified before incidents happen.

“Build an alert routing panel where I can see my Sentry alert rules mapped to Slack channels, with a test button to verify each route works.”

Connection needed: Connector (+ Slack connector for routing)

Stakeholder health digest

A simplified view of production health for non-technical stakeholders. Show error trends, uptime indicators, and release status without the complexity of the full Sentry interface.

“Create a production health dashboard for leadership showing error trends this week, current crash-free rate, and status of the last 3 releases in simple terms.”

Connection needed: Connector

Project and environment access

What you can access depends on your Sentry permissions:

• Organization member: Projects you’ve been given access to
• Organization admin: All projects in the organization
• Multiple projects: Build dashboards that span several Sentry projects

When prompting, specify which Sentry project and environment you want to work with for more accurate results.

Combining with other connectors

Sentry works well with other connectors for complete incident workflows:

• Sentry + Slack: Route alerts to channels, post error summaries, notify on-call teams
• Sentry + Linear: Create issues from production errors, link bugs to code changes

Multi-connector workflows require connecting each service separately.

What visitors see

When you publish your app, consider who will use it:

• Engineering tools: Team members see detailed error data and stack traces
• Leadership dashboards: Stakeholders see health summaries without technical details
• Internal operations: Support teams see issue context for customer reports

Production error data can include sensitive information like user IDs, request data, or internal system details. Keep observability dashboards internal to your team.

Limitations

• Organization-level access. The connector accesses one Sentry organization per connection. For multiple organizations, create separate projects.
• Permission-based. You can only access projects your Sentry account has permission to view.
• Read-focused. Most Sentry dashboards display data. Modifying issues or alert configurations depends on your Sentry permissions.
• API rate limits. Sentry limits API requests. High-frequency polling may be throttled.

FAQ

Does connecting Sentry cost anything?

No. Connecting is free. You only spend credits when you build something.

Will this change anything in my Sentry account?

Dashboards you build read your Sentry data and display it in new formats. Your issues, releases, and alerts stay exactly where they are. Sentry remains your monitoring system.

Can I see all my Sentry projects?

You can access projects your Sentry account has permission to view. Specify which project you want in your prompt for more focused results.

Do I need to know how to code?

No. Describe what you want in plain language and Sticklight builds it. If you do write code, the files are there to open and edit.

How do I get the best results?

Name your specific Sentry project and environment. Instead of “build an error dashboard,” try “build an error triage board for my Production environment in the Backend project showing unresolved issues from the past 7 days.”

Can I route Sentry alerts to Slack?

Yes, by connecting both Sentry and Slack. You can build routing panels that map alert severities to Slack channels and test the routes.

Does this replace Sentry?

No. Sentry handles your production monitoring. Sticklight builds custom views and workflows on top of that data. You still need Sentry for the underlying observability.

Can I connect multiple Sentry organizations?

Each project connects to one Sentry organization. For multiple organizations, create separate projects.