ActionSentryUpdated September 2026

How do I fetch a Sentry issue?

Short answer: You can get sentry issue in Sentry by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Sentry Get Sentry Issue action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Get Sentry Issue in Sentry — start free All 4 Sentry actions

Get Sentry Issue in Sentry — start free

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Issue ID issue_id	string	Required	Issue ID. Example: 12345

Sample request

{
  "issue_id": "e.g. 12345"
}

Returns

{
  "id": "12345",
  "count": 42,
  "level": "error",
  "title": "TypeError: Cannot read property",
  "status": "unresolved",
  "shortId": "MY-APP-1A2B",
  "lastSeen": "2025-01-15T12:00:00Z",
  "firstSeen": "2025-01-01T00:00:00Z"
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Get Sentry Issue.

Any of these apps can fire this action as part of a workflow.

Google Sheets → Sentry

2 Google Sheets triggers

HubSpot → Sentry

18 HubSpot triggers

FAQ

Questions about Get Sentry Issue.

What does the Get Sentry Issue action do in Sentry?

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.

What inputs does Get Sentry Issue require?

Required: Issue ID. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Sentry returns an error?

The run history shows the failed step with its input and the error message Sentry returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Get Sentry Issue support batch operations?

Run Get Sentry Issue inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Sentry's rate limits.

More actions

Other Sentry actions.

Action

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.

Action

List Sentry Projects

Returns every project in the connected org. Useful for resolving project IDs at workflow setup.

Action

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.

Get Sentry Issue in Sentry — start free