Alerting & Notifications

Alerting & Notifications

Deliver Fleetera alerts to your own systems with signed webhook notifications.

When an alert triggers or resolves in Fleetera, you can have the platform notify an external system automatically. Notifications are sent through notification channels — destinations you configure once and reuse across your alerts.

A webhook channel is a channel that posts a signed JSON message to an HTTPS endpoint you control. Webhooks are the most flexible channel type: because Fleetera sends a structured, signed payload, you can route alerts into Slack, Microsoft Teams, PagerDuty, a ticketing system, or any service that can receive an HTTP request.

How webhook notifications work

  1. You create a webhook channel with the destination URL (and, optionally, custom headers).
  2. Fleetera generates a signing secret for the channel and shows it to you once.
  3. When an alert triggers — or resolves, if you opt in — Fleetera sends an HTTP POST to your URL with a JSON body describing the alert.
  4. Each request carries an HMAC signature computed with your channel secret, so your receiver can confirm the request genuinely came from Fleetera.
  5. If your endpoint is unavailable, Fleetera retries with exponential backoff before giving up.

The channel signing secret is shown only once, at the moment you create the channel. Fleetera stores it encrypted and can never display it again. Copy it immediately and store it like a password (in a secrets manager or your platform's environment configuration). If you lose it, create a new channel to get a new secret.

In this section

On this page