Templates

Some messages you write again and again: the monthly maintenance window, the outage at the same upstream provider, the deployment announcement. A template holds the title, the text and the settings, so that two clicks are enough when it matters.

Available from the Basic plan.

Incident templates

Under Status Pages → Incidents → Templates. Stored are:

  • Name — for you only, never shown publicly.
  • Title and message — what the incident gets.
  • Status and severity — the values it starts with.
  • Affected components — the usual selection.
  • The visibility and notification switches.

Creating an incident, you pick the template at the top and the form fills in. Everything stays editable afterwards — a template is a starting point, not a stencil that holds you.

Maintenance templates

Under Status Pages → Maintenances → Templates. On top of title, text and components, a maintenance template stores:

  • Duration in minutes — instead of fixed times. You pick only the start; the end is derived.
  • All the automation switches: auto start, auto complete, update component status, reminder, notify on start and on completion.

The automation switches are the real gain. Getting them right once and never thinking about them again is more reliable than deciding them afresh each time.

Turning an existing entry into a template

The view of an incident or a maintenance offers Save as template. When you notice you are typing the same maintenance for the third time, that is the moment.

Through the API

Templates are fully manageable through /api/v1/incident-templates and /api/v1/maintenance-templates — create, change, delete, duplicate (POST …/{id}/duplicate). POST /api/v1/incidents/{id}/save-as-template and …/maintenances/{id}/save-as-template turn an existing entry into one.

Most useful for pipelines: applying a template. POST /api/v1/incident-templates/{id}/apply opens an incident from it. Placeholders such as {service} in the template's title and text are filled from variables:

curl -X POST https://statuswerk.eu/api/v1/incident-templates/{id}/apply \
  -H "Authorization: Bearer $STATUSWERK_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"variables": {"service": "Checkout"}}'

The same with POST /api/v1/maintenance-templates/{id}/apply, with scheduled_start_at and scheduled_end_at. Full detail in the API reference.