Overview
Add Sentry to any ModuleX agent or workflow. Error tracking and performance monitoring platform integration against the Sentry REST API (sentry.io/api/0).
Categories: Monitoring & Observability · Developer Tools & Infrastructure · Monitoring · Error Tracking · Auth: Auth Token · Actions: 4
Authentication
Auth Token
Use your Sentry Auth Token (internal integration token or user auth token)1
Step 1
Go to Sentry Settings -> Developer Settings -> Internal Integrations
2
Step 2
Create a new internal integration or use an existing one
3
Step 3
Copy the token from the integration’s credentials
Required Credentials
Available Actions
list_issue_events — Return a list of events bound to an issue
list_issue_events — Return a list of events bound to an issue
list_project_events — Return a list of events bound to a project
list_project_events — Return a list of events bound to a project
list_project_issues — Return a list of issues bound to a project
list_project_issues — Return a list of issues bound to a project
Parameters
string
required
The slug of the organization
string
required
The slug of the project
string
A Sentry structured search query. If not provided an implied ‘is:unresolved’ is assumed
string
An optional stat period (e.g. ‘24h’, ‘14d’)
boolean
If true, short IDs are also looked up by this function
integer
Maximum number of results to return (Default:
100)Response
update_issue — Update an individual issue's attributes
update_issue — Update an individual issue's attributes
Parameters
string
required
The ID of the issue to update
string
New status for the issue: resolved, resolvedInNextRelease, unresolved, ignored
string
The actor ID or username to assign to this issue
boolean
Changes the flag indicating if the user has seen the event
boolean
Changes the bookmark flag
boolean
Sets the issue to public or private
Response
Limits & Quotas
- Rate limits: Sentry applies per-organization rate limits. Typical limits are ~100 requests/second for the events API.
- Pagination: List endpoints use cursor-based pagination; the integration follows cursors up to
max_results. - Error model: non-2xx responses and timeouts are caught and returned as
success=False+errorrather than raising.