ActionBetter StackUpdated September 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.

List Incidents in Better Stack — start free All 3 Better Stack actions

List Incidents in Better Stack — 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
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.

Triggered by

Apps that pair well as the trigger for List Incidents.

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

Google Sheets → Better Stack

2 Google Sheets triggers

HubSpot → Better Stack

18 HubSpot triggers

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 run history shows the failed step with its input and the error message Better Stack 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 List Incidents support batch operations?

Run List Incidents 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 Better Stack's rate limits.

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.

Action

List Monitors

Returns every monitor in the team with current status, uptime percentage over a configured window, last-failure timestamp. Useful for "show me all monitors that have been flaky this month" maintenance workflows.

List Incidents in Better Stack — start free