ActionSentryUpdated May 2026

How do I fetch a Sentry issue?

Short answer: Drop the "Sentry → Get Sentry Issue" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 4 Sentry actions

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 workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Get Sentry Issue support batch operations?

Yes. Run Get Sentry Issue inside a Loop node to process arrays. Tiny Command handles Sentry's rate limits automatically so you don't have to throttle manually.

More actions