Short answer: Drop the "Better Stack → List Incidents" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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 | — |
{"page": "{{trigger.page}}"}
{"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.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.