Sentry integration

Monitoring & Observability · 4 actions · Bearer token auth

Error tracking and performance monitoring platform

Put Sentry to work View Sentry integration docs

Overview

The ModuleX Sentry integration lets a ModuleX agent operate Sentry on your behalf — running update and list actions across issue events, project events and project issues — directly from a plain-English request, using your organization's own Sentry credentials. No pre-built workflow is required: the agent picks the right Sentry action for the task.

Sentry is a monitoring & observability platform. ModuleX adds the agent layer: ask for an outcome and it selects and runs the right Sentry action — or, when you want a repeatable process, the composer assembles a Sentry workflow for you, streaming the nodes onto the canvas as it builds.

Ask the assistant

Drive Sentry in plain English

Type what you want. A ModuleX agent picks the right Sentry action — or chains several — and runs it. No workflow to build.

Update an individual issue's attributes
resolves toupdate_issue
Show me the issue events that match what I describe
resolves tolist_issue_events

Use cases

What you can automate with Sentry

Pull a list of issue events for a reportlist_issue_events
Update an issue the moment something changesupdate_issue
Return a list of events bound to a projectlist_project_events
Return a list of issues bound to a projectlist_project_issues

At a glance

Sentry integration at a glance

VendorSentry

CategoryMonitoring & Observability

Actions available4

AuthenticationBearer token

Uses your own credentialsYes

Works with the assistantYes

Works in the composerYes

Multi-step / tool-chainingYes

Technical referenceView docs

Integration version1.0.0

Last updatedJun 2026

Reference

All 4 Sentry actions

Issue Events1

list_issue_events

Return a list of events bound to an issue

Project Events1

list_project_events

Return a list of events bound to a project

Project Issues1

list_project_issues

Return a list of issues bound to a project

Issues1

update_issue

Update an individual issue's attributes

See full parameters and response schemas in the Sentry integration docs

Two ways

Two ways to use Sentry in ModuleX

Ask the assistantType what you want done and a ModuleX agent picks the right Sentry action and runs it — no workflow to build.

Compose a workflowNeed it to happen every time? Describe the process and the composer wires Sentry into a repeatable workflow you can run on a schedule, from chat, or as an API.

Security

Connecting Sentry

Bearer tokenSentry uses bearer-token authentication. You provide a Sentry access token; ModuleX encrypts it and scopes it to your organization so the whole team can use Sentry.

Step-by-step setup in the Sentry docs

Pairs well with Sentry

Agents often chain Sentry with these — connect them once and the agent can use all of them in a single task.

incident.io46 actions

FAQ

Sentry + ModuleX FAQ

A ModuleX agent can run any of Sentry's 4 actions — across issue events, project events, project issues and issues — from a plain-English request, using your organization's own Sentry credentials.

No. The agent selects the right Sentry action from your prompt. A workflow is only needed when you want a repeatable process — and the composer builds that for you from a description.

With your own Sentry access token, stored encrypted and scoped to your organization.

4, spanning issue events, project events, project issues and issues.

Sentry runs on your own credentials, so any Sentry usage is billed by Sentry directly. ModuleX meters the agent run — and if you connect your own model keys, there's no ModuleX markup on model usage.

Put Sentry to work in ModuleX.

Connect Sentry once with your own credentials and let your agent run all 4 actions on demand.

Put Sentry to work View technical docs

Last updated: Jun 2026Browse all 175 integrations →