--- title: "Sentry Integration" description: "Application error monitoring and performance tracking from your flows. Manage projects, triage issues, inspect events, and coordinate releases and deploys over the Sentry API using an auth token." url: https://flowrunner.ai/integrations/sentry date_modified: 2026-08-01T02:40:32-07:00 --- # Sentry [Developer Tools](https://flowrunner.ai/integrations/category/developer-infrastructure) Application error monitoring and performance tracking from your flows. Manage projects, triage issues, inspect events, and coordinate releases and deploys over the Sentry API using an auth token. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 18 actions · API key · available [Sentry website](https://sentry.io/) · [Platform Documentation](https://docs.sentry.io/api/) · Capability data verified 2026-07-14 1. A scheduled flow runs List Issues with an is:unresolved filter 2. Agent reads each new issue's title, culprit, and event count 3. Agent applies triage rules to classify each issue as route, ignore, or delete 4. Agent resolves or assigns the issues that match a clear rule 5. Agent posts issues proposed for deletion to the engineering channel with their event history 6. An engineer confirms which issues to delete; only then does the agent call Delete Issue ## What This Integration Enables FlowRunner agents use Sentry to keep error triage moving and to tie releases into the rest of the pipeline. An agent can auto-triage new issues by resolving, ignoring, or assigning them based on flow rules, fan critical errors out to chat, on-call, or ticketing tools, record releases and deploys so Sentry associates errors with the right version, pull issue and event details into reports, and provision projects under a team. It supports self-hosted Sentry by pointing at your instance URL. The one action the agent never runs on its own is Delete Issue, because deleting an issue and its events cannot be undone. ### Without FlowRunner **Issue backlog noise**: Unresolved issues pile up faster than anyone triages them **Manual routing**: An engineer reads each new issue and decides where it goes by hand **Risky cleanup**: Someone deletes issues in bulk and loses events they later needed ### With FlowRunner **Rule-based triage**: The agent resolves, ignores, and assigns issues that match clear rules **Fewer manual reads**: Engineers see only the issues that actually need a person **Human on deletions**: Permanent deletes wait for an engineer to confirm ## Use Case Scenarios ### Rule-based triage with a deletion gate A scheduled flow lists unresolved issues. The agent classifies each one: known-noise issues get ignored, issues that match an owner rule get assigned, and genuinely new bugs get routed to a tracker. Issues that look like stale test noise are not deleted automatically. The agent posts them to the engineering channel with their event history and asks which to remove. An engineer confirms, and only then does the agent call Delete Issue. Triage stays fast, and nothing permanent happens without a person. ### Critical error escalation When List Issues surfaces a new critical issue, the agent opens an incident in an on-call tool to page the responsible engineer and posts to the team channel with a link to the issue. A serious error reaches a person through the channels they already watch, with the context attached. ### Release and deploy tracking After a deployment flow completes, the agent calls Create Release and Create Deploy to record the version and environment, so Sentry can associate any new errors with the right release. It logs the release version, environment, and timestamp for audit. Errors become traceable to the deploy that introduced them. ## Human-in-Loop Highlight The human-in-loop moment in Sentry is the deletion gate. Resolving, ignoring, and assigning are reversible, so the agent runs them by rule. Deleting an issue is not reversible, it removes the issue and every event under it, so the agent stops. When its triage rules flag issues that look deletable, it posts them to the engineering channel with their event counts and asks: "These three issues look like stale test noise. Confirm which to delete permanently?" An engineer confirms the list. Only then does the agent call Delete Issue. The agent keeps the backlog clean on its own. A person owns the deletes that cannot be walked back. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 18 actions ### Projects 4 - **List Projects** List all projects in the organization. Used to resolve a project before triage. - **Get Project** Retrieve a project's full details by slug. - **Create Project** Create a project under a team. Used to provision monitoring for a new service. - **Update Project** Rename, re-slug, or change a project's platform. ### Issues 6 - **List Issues** List issues for a project, filtered with Sentry search syntax such as is:unresolved. Used to surface new bugs for triage. - **Get Issue** Retrieve a single issue's details. - **Update Issue** Resolve, unresolve, or ignore an issue and set its assignee. Used to auto-triage by rule. - **Delete Issue** Permanently delete an issue and its events. Irreversible, and run only behind a human confirmation. - **List Issue Events** List the occurrences that belong to an issue. - **Get Latest Event** Retrieve the most recent event for an issue. Used to pull the freshest stack trace. ### Events 2 - **List Project Events** List all events for a project. - **Get Event** Retrieve a single event by ID within a project. ### Releases 5 - **List Releases** List releases for the organization. - **Create Release** Create a release for one or more projects. Used in a CI/CD flow so Sentry can associate errors with a version. - **Get Release** Retrieve a release by version. - **Delete Release** Delete a release that has no events. - **Create Deploy** Record a deploy of a release to an environment. ### Teams 1 - **List Teams** List the teams in the organization. ## Frequently Asked Questions ### What can FlowRunner do with Sentry? FlowRunner agents can run List Projects, Get Project, and Create Project in Sentry, plus 15 more actions. ### Does connecting Sentry to FlowRunner require OAuth? No. Sentry connects to FlowRunner with an API key, no OAuth flow required. ### Can Sentry trigger a FlowRunner workflow automatically? Sentry doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Sentry?** This integration exposes Sentry to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/sentry. Site index: https://flowrunner.ai/llms.txt