ActionBetter StackUpdated June 2026

How do I list Better Stack incidents?

Short answer: You can list incidents in Better Stack by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Better Stack List Incidents 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.

Use this action All 3 Better Stack 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
Page page	string	Optional	–

Sample request

{
  "page": "{{trigger.page}}"
}

Returns

{
  "data": [
    {
      "id": "inc_abc",
      "attributes": {
        "name": "Site down",
        "cause": "5xx response",
        "started_at": "2026-05-11T00:00:00Z"
      }
    }
  ]
}

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

FAQ

Questions about List Incidents.

What does the List Incidents action do in Better Stack?

Returns active and historical incidents with filters by status and time range. For "what's currently firing" dashboards or "weekly incident report" rollups to the team.

What inputs does List Incidents require?

List Incidents has no required inputs. Sensible defaults are applied if you leave fields blank.

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 Better Stack 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 Incidents support batch operations?

Yes. Run List Incidents inside a Loop node to process arrays. TinyCommand handles Better Stack's rate limits automatically so you don't have to throttle manually.

More actions

Other Better Stack actions.

Action

Create Uptime Monitor

Programmatically adds a new uptime check with URL, method, expected status code, request interval. The standard hook for "Vercel deployment finished → auto-add monitor for the new deployment URL" workflows.