Pulsetic

Uptime monitoring, status pages and incident tracking with Pulsetic — API docs: https://help.pulsetic.com/article/228-general-api-information

List and manage monitors, read uptime stats and downtime, post status-page incidents, and trigger flows when a monitor goes down or recovers. Authentication uses an API token (Pulsetic dashboard → API → API/MCP → + API key), sent verbatim in the Authorization header — Pulsetic does not use a Bearer prefix.

Two API shapes worth knowing, both taken from Pulsetic's own request examples:

• POST /monitors takes urls as an array, while PUT /monitors/{id} takes a single url.
• A status-page incident nests its first update under an update key ({ title, update: { status, date, message } }); those fields are ignored at the root.

There is no pause/resume input on Update Monitor — Pulsetic's public docs never name the field that toggles a monitor, so rather than ship a guessed field name that silently does nothing, pass it through Additional Fields once confirmed.

No custom API call action: the shared helper accepts an absolute URL and merges the connection's auth headers into it, which would let a user-entered address receive the Pulsetic token.