List Sentry Issues: Sentry action

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
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"

Sample request

{
  "organizationSlug": "{{trigger.organizationSlug}}",
  "projectSlug": "{{trigger.projectSlug}}",
  "query": "is:unresolved"
}

Returns

[
  {
    "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.

FAQ

Questions about List Sentry Issues.

What does the List Sentry Issues action do in Sentry?

Paginated issues with Sentry's query syntax (is:unresolved level:error environment:production). For "current open errors" dashboards and bug-triage workflows.

What inputs does List Sentry Issues require?

Required: Organization Slug, Project Slug. 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 List Sentry Issues support batch operations?

Yes. Run List Sentry Issues 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