Sentry
Sentry error and issue triage
Sentry is the error-monitoring platform that ingests exception stack traces from production apps and groups them into Issues for triage. Tiny Command exposes four actions, no triggers (Sentry's Alert Rules and Issue Alerts route firing notifications to configured integrations — Slack, PagerDuty, Webhooks; configure a Webhook integration pointing at a Tiny Command webhook trigger URL for "new issue" workflows): List Projects (every project in the org), List Issues (with filters by project, status, environment, time range, plus Sentry's full query syntax like `is:unresolved level:error`), Get Issue (full issue detail — event count, user-affected count, first-seen, last-seen, owners, the latest event's stack trace), Resolve Issue (mark resolved; combine with explicit-version commit for "resolved in next release" semantics). The connection uses a Sentry auth token from Sentry Settings → Auth Tokens with appropriate scopes (project:read, event:read, project:write for resolution). Sentry Cloud uses sentry.io; self-hosted uses your URL.
Do anything Sentry can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| Get Sentry Issue | Returns a specific issue with event count, user-affected count, first/last-seen timestamps, owners, latest event stack trace. For deep-context workflows after a Sentry alert fires. |
| List Sentry Issues | Paginated issues with Sentry's query syntax (is:unresolved level:error environment:production). For "current open errors" dashboards and bug-triage workflows. |
| List Sentry Projects | Returns every project in the connected org. Useful for resolving project IDs at workflow setup. |
| Resolve Sentry Issue | Marks an issue resolved. Optionally set statusDetails.inRelease for "resolved in version X" semantics — Sentry auto-regresses if the issue resurfaces in a later release. |
Pre-built Sentry workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect Sentry once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every Sentry field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the Sentry integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect Sentry to Tiny Command?
What Sentry triggers does Tiny Command support?
What Sentry actions can I run from a workflow?
Is the Sentry integration real-time?
Do I need to write code to use Sentry with Tiny Command?
How much does the Sentry integration cost?
More developer tools apps people connect.
Same category as Sentry, ordered by how often teams pair them. Hover the carousel to pause.
Do more with Sentry.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
