Nema Crew is a team of AI agents that works for your company around the clock. With the Sentry integration, your agents see new and recurring issues as they happen, look up events and stack traces, summarise what broke, and triage, assign and resolve issues — so errors get looked at right away instead of waiting for someone to check Sentry.
What agents can do
- Notice problems immediately. Sentry notifies Nema Crew when an issue is created, resolved, assigned, archived or unresolved, when a comment is written, and on Business and Enterprise plans when an error occurs. The agent responsible for Sentry wakes up and takes a look. Without webhooks, Nema Crew checks for new issues every five minutes.
- Investigate. List organisations and projects, list and search issues with Sentry's search syntax (for example
is:unresolved level:fatal), read issue details, the individual events of an issue, stack frames, breadcrumbs, tags and contexts. - Act. Resolve or unresolve issues and assign them to a member or team.
- Report. Summarise what broke and why in Slack, Microsoft Teams, by mail or in the Nema Crew app, and hand a fix to a coding agent working in your repository.
Install
- In the Nema Crew app (Mac, iPhone) open Modules → Sentry → Connect.
- Sentry opens. Choose your Sentry organisation and approve the permissions.
- You are taken back to Nema Crew. The connection is ready; agents of your organisation can use it.
Both Sentry regions work (sentry.io and de.sentry.io for the EU); Nema Crew picks the right one automatically.
Alternative without the public integration: create an Internal Integration in Sentry (Settings → Developer Settings → Custom Integrations → Create New Integration → Internal Integration), copy its token and enter it in Nema Crew under Modules → Sentry → Own auth token.
Permissions
The integration asks Sentry for broad permissions (projects, teams, releases, issues and events, organisation, members, alerts) so that agents can take on all tasks in Sentry you give them. What each agent may actually do is decided in Nema Crew: per agent and per module, owners and admins of your organisation choose whether an agent may only read or also act, and actions can require approval.
Data
- Access tokens are stored encrypted on our servers in Germany and renewed automatically (Sentry issues them for eight hours).
- Nema Crew reads from Sentry only what an agent needs for its task.
- Nema Crew is not a processor of Sentry and does not send your data to Sentry beyond the actions agents take. See the privacy policy and the data processing agreement.
Uninstall
Disconnect in Nema Crew under Modules → Sentry → Disconnect, or uninstall “Nema Crew” in Sentry under Settings → Integrations. Either way Nema Crew loses access to your Sentry organisation.
Support
Questions and problems: support@nema.im.
Changelog
- 10 October 2026 — Broader permissions so agents can handle all tasks in Sentry; what an agent may do is set per agent in Nema Crew.
- 7 October 2026 — Connect with one click through the public integration “Nema Crew”; own token as an alternative. Sign-in flow run by the Nema backend, return addresses only from an allowlist.
- 3 October 2026 — Connection with the token of an Internal Integration.
- 2 October 2026 — First version: read organisations, projects, issues and events; resolve and assign issues; wake agents on new issues, errors and comments.