Integrations · Free on every plan

Send geofence events to any system, in real time

Every geofence event Fencemaker detects — entry, exit, dwell, route deviation, device offline — can be pushed to your own endpoint the moment it happens, as a structured JSON payload. No polling, no batch delays. Build automations, sync to your own database, or trigger workflows in tools that don't have a native Fencemaker integration.

How this is different from Slack / Telegram. Slack and Telegram alerts are ready-made destinations — pick a channel and Fencemaker posts human-readable messages there. Webhooks are the underlying delivery mechanism: a raw HTTP POST containing the full event payload, sent to any URL you control. If Slack and Telegram are "notify a person," webhooks are "notify a system" — your backend, a data warehouse, Zapier, PagerDuty, or any custom endpoint. In fact, Fencemaker's own Slack and Telegram alerts are built on this same webhook layer.

Why teams use this

Full control — send events to any HTTPS endpoint you own or manage.
Machine-readable — structured JSON, easy to parse and route in your own code.
Free on every plan — webhook delivery is not gated behind a paid tier.
Composable — pair with Slack/Telegram for human notification while webhooks handle automation.
Low latency — events are pushed within seconds of detection, not polled on a schedule.

What you can send via webhook

Geofence entry and exit events
Dwell-time threshold breaches
Route or territory deviation alerts
Device offline / signal-loss warnings
Full event history replay for a given device or geofence, on request

How it works

Go to Settings → Integrations in your Fencemaker dashboard.
Enter an endpoint URL (must be HTTPS) that will receive POST requests, and save it.
Optionally set a signing secret so you can verify payload authenticity on your end.
Send a test event from the dashboard to confirm your endpoint responds with a 2xx status.
Every future geofence event on your account is delivered to that endpoint automatically.

Sample payload

POST /your-endpoint HTTP/1.1
Content-Type: application/json
X-Fencemaker-Signature: sha256=...

{
  "event": "geofence.entered",
  "timestamp": "2026-09-07T09:42:00+01:00",
  "data": {
    "device_id": "LB68 XKR",
    "territory_id": "uuid",
    "territory_name": "Canary Wharf Zone A",
    "event_type": "entered",
    "location": { "latitude": 51.5054, "longitude": -0.0235 }
  }
}

The X-Fencemaker-Signature header is only present when a signing secret is configured — it's an HMAC-SHA256 signature of the raw request body, computed with your secret.

Requirements

An HTTPS endpoint capable of receiving and acknowledging POST requests.
An active Fencemaker account on any plan, including the free tier.

FAQ

Does this cost extra?

No. Webhook delivery is included free on every Fencemaker plan, including the free tier.

Is this the same as the Slack/Telegram integrations?

No — Slack and Telegram are pre-built destinations for human notification. Webhooks are the raw HTTP delivery layer for connecting Fencemaker to any system, and are what those two integrations are built on internally.

How do I verify a payload is really from Fencemaker?

Set a signing secret when you configure the webhook. Every payload is then signed with HMAC-SHA256, and the signature is sent in an X-Fencemaker-Signature header you can verify server-side.

What happens if my endpoint is down?

A failed delivery is logged in your dashboard for review, alongside delivery success rate and recent failures.

Can I use this with Zapier or Make?

Yes — point the webhook at your Zapier or Make catch-hook URL to build no-code automations on top of Fencemaker events.