On Geofence Entry

​

Overview

​

Availability

​

Constraints

1. Webhook only. Webhook is the only automation type accepted. Create Task, Create and Assign Task, Move Task, Assign Task, Update Task, Create or Update Data Source, and Notification are all rejected with 400 Bad Request.
2. A geofence group is required. The automation is scoped to exactly one geofence group, chosen in the Geofence Group picker. Saving without one fails validation. The automation then fires only for geofences that belong to that group, so separate groups can feed separate integrations.

​

When Does This Event Trigger?

1. The field worker’s mobile app reports a GPS position.
2. MileApp checks which of your active geofences contain that point.
3. If the geofence is newly entered, the worker is recorded as inside and the dwell clock starts.
4. Once the worker has been inside for at least the geofence’s dwell time (dwellMinutes), the entry event fires and the webhook is sent.

​

Setting Up On Geofence Entry Automation

​

Step 1: Create the Geofence and Group

1. Draw the geofences you want to watch and place them in a geofence group
2. Set each geofence’s dwell time (minutes the worker must stay inside before the entry counts)
3. Make sure each geofence is active, inactive geofences are ignored

​

Step 2: Create the Automation

1. Log in to the MileApp web portal
2. Click Flow in the main navigation, then open the Automation tab
3. Click New
4. Automation Name: a descriptive name, for example “Notify WMS on store arrival”
5. Event: select On Geofence Entry
6. Geofence Group: select the group to watch (required)
7. Automation Type: Webhook (the only option for this event)

​

Step 3: Configure the Webhook

1. URL: the endpoint that should receive the crossing. Required, and must be a valid URL
2. Header (Optional): custom HTTP headers, for example Authorization
3. Value (Optional): the matching header value

URL: https://api.yourcompany.com/webhook/geofence-entry
Header: Authorization
Value: Bearer your_api_token_here

​

Step 4: Save and Activate

1. Click Submit
2. Confirm the automation toggle is Active
3. Test by having a field worker enter one of the group’s geofences and stay for the dwell time

​

Webhook Payload

{
  "_id": "663b2c3d4f1a2b3c4d5e6f80",
  "eventName": "entry_geofence",
  "email": "driver@example.com",
  "organizationId": "660a1b2c4f1a2b3c4d5e6f03",
  "taskId": null,
  "lat": -6.2088,
  "lon": 106.8456,
  "speed": 0,
  "createdFrom": "app",
  "isLatest": true,
  "createdTime": "2026-07-20T08:15:00.000Z",
  "geofenceId": "gf_123",
  "geofenceName": "Store A Sudirman",
  "geofenceGroupId": "66c1a4f2d3b19f0012ab77e4",
  "geofenceGroup": "Visit Store",
  "dwellMinutes": 5
}

​

Geofence Fields

​

Location Fields

​

Response

{
  "status": "received"
}

​

Tracking List Markers

​

Monitoring and Troubleshooting

​

Viewing Automation Logs

1. Go to Flow > Automation
2. Find your automation in the list
3. Click the clock history icon to view execution logs
4. Review successful executions and errors

​

Common Issues

• The automation is not Active
• The geofence is not active
• The worker did not stay inside long enough to satisfy the dwell time
• The worker was already inside the geofence, so the entry had already been announced
• The geofence belongs to a different group than the one selected on the automation
• Your organization is not in the geofence rollout

• Confirm the automation toggle is ON and the geofence is active
• Lower the dwell time and retest, a drive-through will not fire an entry
• Have the worker leave the geofence completely and re-enter
• Check that the geofence sits in the selected group

• Incorrect webhook URL
• Authentication headers missing or incorrect
• The external endpoint is down or unreachable

• Verify the URL is reachable from the public internet
• Check the authentication credentials
• Review the automation logs for the response status and body

​

Related Documentation

• On Geofence Leave
• Webhook Automation
• Automation Event Introduction

​

Frequently Asked Questions