T TelemHQ

Outgoing WebhookswebhookAn HTTP callback sent when an event happens. TelemHQ can use outgoing webhooks to notify another system about tracker events.View glossary entrySource: MDN API glossary

PRO

Receive HTTPHTTPThe web protocol used for requests and responses. TelemHQ ping URLs receive HTTP requests from jobs after they run.View glossary entrySource: MDN glossary POSTPOSTAn HTTP method used to send data to a server. TelemHQ pings use POST when a job reports a run and optional payload.View glossary entrySource: MDN HTTP docs requests to your own servers when a trackertrackerA monitored job, AI pipeline, worker, script, or automation in TelemHQ. Each tracker has its own ping URL and run history.View glossary entrySource: TelemHQ docs fails or recovers.

Configuration

Setting up webhooks is simple and done on a per-tracker basis.

  1. Navigate to the Dashboard.
  2. Click on the specific Tracker you want to monitor.
  3. Scroll down to the Configuration card (below Notifications).
  4. Locate the Webhook URL field.
  5. Click the Edit button (pencil icon) or the field itself.
  6. Enter the fully qualified URL of your endpointendpointA specific URL where an API receives requests. A TelemHQ tracking URL is the endpoint your job calls after it runs.View glossary entrySource: MDN API glossary (e.g., https://api.myapp.com/webhooks/cron).
  7. Click Save.

Note: Webhooks are available on paid plans. Free accounts can view the setting but cannot enable it.

PayloadpayloadThe structured data sent with a request. In TelemHQ, payloads should contain safe operational metadata, not prompts, completions, secrets, customer data, or private paths.View glossary entrySource: MDN API glossary Reference

Failure Event

Triggered when a job misses its expected schedule (plus grace periodgrace periodExtra time after a job is expected to run before TelemHQ marks it late or failing. It keeps normal scheduling jitter from creating false alarms.View glossary entrySource: TelemHQ docs). 

{
  "event": "failure",
  "tracker": {
    "id": "123e4567-e89b-12d3...",
    "name": "Database Backup",
    "url": "https://telemhq.com/trackers/123e4567..."
  },
  "timestamp": "2026-01-25T15:30:00.000Z",
  "reason": "Missed expected run"
}

Recovery Event

Triggered when a previously failing tracker receives a successful pingpingA request sent to TelemHQ after a job runs. A ping can be a simple heartbeat or include JSON payload data about what happened.View glossary entrySource: TelemHQ docs. 

{
  "event": "recovery",
  "tracker": {
    "id": "123e4567-e89b-12d3...",
    "name": "Database Backup",
    "url": "https://telemhq.com/trackers/123e4567..."
  },
  "timestamp": "2026-01-25T15:45:00.000Z"
}

Security & Retries

  • Requests are sent with User-Agent: TelemHQ-Webhook/1.0.
  • We expect a 2xx response code.
  • Currently, we do not retry failed deliveries automatically (Fire-and-forget).
  • Ensure your endpoint is publicly accessible or reachable by our servers.

Testing & Verification

We recommend testing your integration before relying on it for production alerts.

  1. Get a Test URL: Visit Webhook.site to get a temporary URL that captures incoming requests.
  2. Configure: Set this URL as your Webhook URL in your tracker settings.
  3. Trigger Failure: Create a new tracker with a short schedule (e.g., Every minute) and Grace Period (1 min). Do not send any pings. Wait approx. 2-3 minutes.
  4. Verify: Check Webhook.site. You should see a POST request with the failure event.
  5. Trigger Recovery: Send a manual ping to your tracker (e.g., using curl or by visiting the tracking URL).
  6. Verify: Check Webhook.site again. You should see a POST request with the recovery event.