In Nektar, a geofence is a user-defined boundary drawn on the map around a real-world area (such as a yard, jobsite, or customer location). Once created, the geofence helps group and organize assets by showing which assets are currently inside the area.
Geofences can also be used to trigger automations when an asset enters or exits the boundary. These events can be generated from manual location updates or automatically through telematics data, beacons, and other tracking sources.
Getting Started
To create a geofence in Nektar, first ensure you have the correct permissions. You must have access to the Geofences menu item, and you must also have Create/Edit/Delete Geofence permissions enabled in the Permission Manager (found under the Map tab).
Once permissions are in place, go to Map > Geofences from the navigation menu. Click the “+” button to create a new geofence. Enter a title and description, then click Choose Geofence Region to draw the boundary on the map. Optionally, you can also link the geofence to a project.
After saving, the geofence will automatically begin to display any assets within its boundary as asset locations are updated, helping you group and track assets by location. Geofences call also be viewed in the main map interface by clicking the Show Geofence Boundaries button
Automations
Geofences can be used in Nektar Automations to trigger workflows based on real-world asset movement. You can create an automation where the trigger is an asset entering or exiting a specific geofence, and then automatically run actions such as sending notifications, sending SMS messages, creating work orders, calling webhooks, and more.
To set up a geofence automation, navigate to the Automations Manager and click the “+” button to create a new automation. Give the automation a title, then choose Geofence as the trigger. Select the geofence you want to monitor, decide whether the trigger applies to assets in a specific project or all projects, and choose whether it should fire on entry or on exit. Finally, select and configure the automation action you want Nektar to perform when the trigger occurs.




