Triage incoming issues
- Webhook fires on every new issue
- Persona summarises and labels it
- Assigns the right engineer
37 tools available
Radar is a full-stack location infrastructure platform offering SDKs and APIs for geofencing, location tracking, geocoding, search, routing, and maps.
Connect Radar to Definable to triage issues, review pull requests, monitor builds. Personas call Radar's 37 tools directly from chat or scheduled flows. Wire it into a triage, review, or release-management persona — every action runs scoped, reviewable, and logged.
Every Radar action below is a callable tool any Definable persona can invoke.
Tool to autocomplete partial addresses and place names based on relevance and proximity. Use after a user inputs a partial address/place to get suggestions, optionally biased by location.
Tool to create a new beacon in Radar. Use when you need to register a physical beacon device (iBeacon or Eddystone) for location tracking.
Tool to create a new trip. Use after gathering origin and destination details to start tracking a trip.
Tool to delete a beacon by its Radar ID. Use when supplying a beacon's unique identifier to remove it.
Tool to delete a geofence by ID. Use when supplying a geofence’s unique identifier to remove it.
Tool to delete a geofence by tag and external ID. Use when you have both the tag and external identifier to remove a specific geofence.
Tool to delete a trip by its Radar ID or external ID. Use after confirming the trip exists.
Tool to delete a user by Radar _id, userId, or deviceId. Use after confirming the user identifier exists.
Tool to convert an address into geographic coordinates. Use when you have a full address string and need precise latitude/longitude before further location analysis.
Tool to retrieve a beacon by Radar _id. Use when you need to fetch full details of an existing beacon.
Tool to get a specific beacon by tag and external ID. Use when you need to retrieve details of a beacon identified by its tag group and external ID.
Tool to retrieve context for a given location. Use when you need geofences, place, and region information based on coordinates. Use after obtaining valid latitude and longitude.
Tool to retrieve a geofence by Radar _id or tag/externalId. Use when you need to fetch full details of an existing geofence.
Tool to retrieve current Places settings for your Radar project. Use when you need to inspect chain detection, supported countries, external ID requirements, and other Places metadata.
Tool to get turn-by-turn directions between multiple locations. Use when you need detailed navigation instructions with steps, distances, and durations for routing.
Tool to calculate travel distance and duration between multiple origins and destinations for up to 625 routes. Use when you need to compute route metrics for multiple origin-destination pairs efficiently.
Tool to retrieve a trip by ID or externalId. Use when you have a trip ID or externalId to fetch its details.
Tool to get a user by Radar _id, userId, or deviceId. Returns the user with all location and context data including geofences, places, beacons, and trip information.
Tool to retrieve users currently within a specific geofence. Use when you need to list all users inside a geofence by its tag and external ID.
Tool to geocode an IP address to city, state, and country. Use when you need location details based on an IP address.
Tool to list events. Use when you need to retrieve a paginated list of events with optional filtering.
Tool to list all geofences sorted by updated time. Use when you need an overview of all configured geofences.
Tool to list all trips, sorted by updated time. Use when you need to page through the latest trips.
Tool to list Radar users sorted by update time. Use when you need to page through users in your project.
Tool to convert geographic coordinates to structured addresses. Use when you have latitude/longitude and need a human-readable address.
Tool to compute distance and travel time between origins and destinations. Use when you need route metrics before optimizing or timing routes.
Tool to search for geofences near a given location. Use when you need to find geofences within a radius of specified coordinates.
Tool to search for places near given coordinates. Use when you need to find points of interest around a location.
Tool to search for users near a location. Use after obtaining coordinates when you need to retrieve users within a given radius.
Tool to track a user's location update. Use when sending a location update for a user, creating or updating user and event data.
Tool to update Places settings for your Radar project including chain metadata preferences. Use when you need to configure chain detection or other Places settings.
Tool to update a trip. Use when you need to modify mode, destination, schedule, or active status.
Tool to update a trip status by Radar _id or external ID. Use when you need to change trip status to started, approaching, arrived, completed, or canceled.
Tool to create or update a beacon by Radar _id. Use when you need to ensure a beacon with a specific ID exists with updated properties.
Tool to create or update a beacon by tag and externalId. Use when you need to ensure a beacon exists or is updated with specific identifiers.
Tool to create or update a geofence by tag and externalId. Use when ensuring a geofence exists or is updated based on identifiers.
Tool to create or update a geofence by Radar _id. Use when you need to upsert a geofence using its internal Radar identifier.
Anything Radar exposes through its API. Common developer tools workflows on Definable include triage issues, review pull requests, monitor builds. Personas can call any of the 37 Radar tools directly, then chain the result into another integration without you writing code.
Radar uses API_KEY on Definable. You connect once from the integrations page, scoped to the permissions you choose, and from then on any persona that has the integration enabled can act on your behalf. Tokens are encrypted at rest and rotated automatically.
Yes — every Definable plan, including Starter, includes access to all 37 Radar tools. You only need a separate Radar subscription if Radar itself charges per seat or per API call.
Every call from a persona to Radar is logged with the user, persona, prompt, and response. Tokens never leave Definable's secrets vault, scopes are configurable per persona, and you can revoke access at any time from the integration page.
Sign up for Definable, open the integrations page, find Radar, and connect via OAuth or API key. You can immediately attach Radar to any persona and start running workflows. The free Starter plan includes 5,000 credits/month.
Definable exposes all 37 Radar actions as callable tools — including `Autocomplete Address or Place`, `Create Beacon`, `Create Trip`, plus 34 more. Each tool gets a typed parameter schema so personas know exactly how to call it.
Wire it up in minutes. No coding required.