Documentation

Web integrations

Pull alerts and map points from a web service on a schedule, with request chains, response mapping and a per-integration health check.

Updated October 31, 2026

Menu → Settings → Devices & services → Integrations → Web integrations.

The Web integrations list
Integrations and their status

What an integration is#

A URL the app fetches on a schedule, a mapping from the response to alert fields (position, type, name, expiry), and rules for what to do with the result: pins on the map, alerts as you approach, a toast on failure. Integrations can sign in first, run a chain of requests, run a small script on the response, and decode compact binary formats.

Add one#

Tap + and fill in:

  1. Name and URL, with the method, headers and body.
  2. Schedule: how often to fetch.
  3. Pre-request steps: open a page in a built-in browser to sign in, run HTTP requests and extract values from them, so the main request can reuse a session.
  4. Data mapping: which fields in the response are the latitude, longitude, type, title and time; value converters for formats that need it.
  5. Test runs it once and shows what came back.

Saved integrations run while the app is open. Switch one off without deleting it from the list; swipe for Edit and Delete. A failed run shows a toast on the map and the Web integrations chip in the status strip.

Points on the map#

Fetched points appear with the icon and colour set under Integrations → Map data, alert as you approach them like reports, and can be spoken if the notification profile allows.

Privacy#

Integrations talk only to the service you configure, from your phone. Sign-ins are kept in the phone's keychain.