Connect Sentry once at the org level, add it to the workspaces that need it, and let your team chat with AI that can use issues, events, and release context from Sentry.
Connect once
Sentry shows what broke and when. Connect it in Faction so chat can list unresolved issues, inspect event details, and tie errors to a release while the team coordinates in one thread.
Find unresolved errors by project, release, or frequency.
Inspect a specific error event during triage.
See which release introduced a regression and which services are affected.
Resolve or assign issues when write tools are enabled.
Use cases
Summarize spike errors and likely regressions after a deploy.
Check new error types tied to a release before customer comms go out.
Brief the next shift on top unresolved issues without opening Sentry for every service.
How it works
Install Sentry from the catalog, add it to workspaces, and let teammates chat with shared access.
FAQs
Sentry is listed in the catalog and rolling out as we finish end-to-end testing.
Faction uses OAuth for this connector. Credentials stay on Faction, not on member laptops.
Teammates in the workspaces you choose. Everyone else keeps working without extra setup.
Yes. Add the connector to the workspaces that need it and pick which tools are on for each team.
Create an organization, connect the integrations your team needs, and bundle them into workspaces everyone can use.
Start free