Sentry
Application monitoring platform for error tracking, performance monitoring, releases, and alert management.
Three ways to use Sentry
Chat with Geni
Ask Geni to pull data, take actions, or answer questions using this integration in a conversation.
Build a workflow
Create automated workflows that trigger on events, run on a schedule, or chain multiple tools together.
Power an app
Use this integration as a data source or action layer behind a dashboard, form, or internal tool.
Supported tools
Actions your AI agents can perform with Sentry.
Add a Member to an Organization
Invite a new member to the organization by email.
Add an Organization Member to a Team
This request can return various success codes depending on the context of the team: - **`201`**: The member has been successfully added.
Add a Symbol Source to a Project
Add a custom symbol source to a project.
Add a Team to a Project
Give a team access to a project.
Bulk Delete Alerts
Bulk delete alerts for a given organization
Bulk Delete Monitors
Bulk delete Monitors for a given organization
Supported triggers
Start a workflow when something happens in Sentry.
New Issue in Sentry
Triggers when Sentry captures a new issue (first occurrence of an error). Filter by projects, environments, and severity levels, or use the Search Query field for the full Sentry search DSL.
Get started automating Sentry
Ready-to-use workflows
Prompts using Sentry
Track every half finished LaunchDarkly rollout in one board
Open one board each morning to see every flag stuck partway through a rollout, how long it has sat there, and ramp or roll back with one click.
Find which feature flag caused your Sentry error spike
When Sentry alerts on a spiking error, we check every recent feature flag change, rank the likely culprits, and post the top suspects to Slack.
Did the last Heroku deploy cause this Sentry error?
When a new Sentry error appears, we check your latest Heroku deploy, alert your team in Slack with the likely cause, and open a GitHub triage ticket.
Page on-call by SMS when Sentry spots a production incident
Every 5 minutes, watch Sentry for new fatal or error-level issues and text the on-call engineer with a link plus a full write-up in Slack.
Did a secret change break production? Correlate Sentry with Doppler
Every 15 minutes, check new Sentry errors against recent Doppler secret activity and tell on-call in Slack whether a secret change is the likely cause.
Route Sentry errors to the right CSM in Slack
When a new error fires, check whether any paying customers are affected, then ping the right CSM in Slack and log the incident on each contact in HubSpot.
Weekly reliability report in Notion from Railway and Sentry
Every Friday afternoon, post a single Notion page that links the week's Railway deploys to the Sentry errors that followed them, ready for on-call handoff.
Tag Sentry releases and post Vercel deploys to Slack
Every time you promote a Vercel production deploy, register the release in Sentry, mark it deployed, and announce it in your team's Slack channel.
