Short answer: You can list sentry issues in Sentry by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Sentry List Sentry Issues action to a workflow, map its 3 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Organization Slug organizationSlug | string | Required | Organization Slug |
Project Slug projectSlug | string | Required | Project Slug |
Search Query query | string | Optional | Search Query. e.g. "is:unresolved" |
{"organizationSlug": "{{trigger.organizationSlug}}","projectSlug": "{{trigger.projectSlug}}","query": "is:unresolved"}
[{"id": "12345","count": "42","title": "TypeError: undefined is not a function","status": "unresolved","culprit": "app.js","lastSeen": "2026-04-11T10:00:00Z","firstSeen": "2026-04-01T00:00:00Z"}]
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.