- Integrations
- /
- Better Stack
- /
- Actions
- /
- List Incidents
ActionBetter StackUpdated May 2026
How do I list Better Stack incidents?
Short answer: Drop the "Better Stack → List Incidents" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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.
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. Tiny Command 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.
ActionList 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.
Send list incidents from your workflows.
Triggered by anything in the catalog. Free tier available. No credit card.