Skip to main content
Better Stack uses two separate API tokens — one for Uptime, one for Telemetry — and you provide whichever you use (at least one). With them the agent can work with your uptime monitors, incidents, and telemetry.

Connect

Create your tokens

  • Uptime API token — from Better Stack’s Uptime API settings.
  • Telemetry API token — from Better Stack’s Telemetry API settings.

Connect in Nuphos

In Connectors → Connect → Better Stack, enter: At least one token is required. Each token you provide is verified against the Better Stack API before saving.

Optional extras

  • Dashboard team ID — lets Nuphos deep-link into your Better Stack dashboards.
  • Prometheus webhook URL — save the inbound URL supplied by Better Stack for its Prometheus integration. Alertmanager sends alerts to Better Stack there; this is not a Nuphos trigger URL.

In the Nuphos app

Your monitors, heartbeats, and incidents feed the unified Monitoring overview — one place to see uptime and liveness across your aggregated observability providers, with deep links back into Better Stack for the full detail.

What the agent can do for you

The agent can list and manage Uptime monitors, heartbeats, and incidents, and read Telemetry dashboards, sources, and metrics. In practice:
  • “Anything down right now?” — it reads monitors and active incidents and summarizes.
  • “Set up an uptime monitor for the new API endpoint” — review the target, type, frequency and destination before creating it.
  • “Why did the heartbeat for the nightly job miss?” — it combines Better Stack signals with what it can see through your other connectors to find the cause.

Permissions & authorization

Team Administrators connect and remove this binding and can restrict it with a member allow-list. Select the connection for the conversation before asking the agent to use it. Provider permissions remain the outer limit, regardless of the prompt or permission mode. Individual actions follow Auto Mode and Full Access. Significant cloud infrastructure work uses plans; a ticket, repository write or routine API action does not automatically create a plan. Give explicit instructions about reviewing changes before publishing when that is the workflow you need.

Good to know

  • The two tokens are independent — you can start with one product and add the other later by updating the binding.
  • To make a Better Stack incident start agent work, create a separate outgoing Better Stack webhook pointing to a Nuphos webhook trigger. Read back its scope and delivery settings and verify delivery before calling the Watch live. The inbound Prometheus URL and the outgoing Nuphos URL serve opposite directions.