Introduction

An automation Event is a type of Trigger that will trigger the Automation. When creating an automation, you select an event that determines when the automation will be triggered.

​

Available Automation Events

MileApp supports the following automation events:

​

1. On Task Created

The event will trigger immediately after you create a Task with the selected Flow. This automation is useful for:

• Automatically creating related tasks
• Sending notifications when new tasks are created
• Updating external systems via webhook

Note: The Flow that was linked to the Automation Event must match. Automation Type would only be activated if both Task’s Flow and Event are matched with an Automation setting. For detailed information, see On Task Created.

​

2. On Task Assigned

The event will trigger after you assign a Task to a user with the selected Flow. This automation is useful for:

• Notifying the assigned user
• Creating follow-up tasks
• Logging assignment events to external systems

For detailed information, see On Task Assigned.

​

3. On Task Finished

The event will trigger after you finish/complete a Task with the selected Flow. This automation is useful for:

• Creating subsequent tasks in a workflow
• Sending completion notifications
• Updating task completion status in external systems

For detailed information, see On Task Finished.

​

4. On Data Source Created

The event will trigger when a new Data Source entry is created. This automation is useful for:

• Automatically creating tasks based on new data entries
• Synchronizing data with external systems
• Triggering workflows based on data creation

For detailed information, see On Data Source Created.

​

5. On Routing Finished

The event will trigger when the route optimization calculation is completed. This automation is useful for:

• Sending optimized routing results to external systems
• Notifying planners that routes are ready
• Auto-dispatching routes after optimization

For detailed information, see On Routing Finished.

​

6. On Routing Dispatched

The event will trigger each time you hit the Dispatch button in the Routing/Result menu. This automation is useful for:

• Receiving updated routing result data after manual adjustments
• Notifying drivers that routes have been dispatched
• Synchronizing dispatch status with external systems

For detailed information, see On Routing Dispatched.

​

7. On Start Trip

The event will trigger when a field worker starts their trip in the mobile app. This automation is useful for:

• Notifying operations team that field work has begun
• Logging trip start times to external systems
• Creating checkpoint tasks

For detailed information, see On Start Trip.

​

8. On Finish Trip

The event will trigger when a field worker finishes their trip in the mobile app. This automation is useful for:

• Generating trip summary reports
• Calculating trip duration and metrics
• Triggering post-trip workflows

For detailed information, see On Finish Trip.

​

9. On Geofence Entry

The event will trigger when a field worker’s GPS position enters a geofence and stays inside it for that geofence’s configured dwell time. This automation is useful for:

• Notifying a WMS or ERP the moment a worker arrives at a store or warehouse
• Logging site arrivals for compliance
• Alerting when a worker enters a restricted area

For detailed information, see On Geofence Entry.

​

10. On Geofence Leave

The event will trigger when a field worker’s GPS position leaves a geofence they had previously entered. This automation is useful for:

• Closing out a site visit in an external system
• Measuring dwell time by pairing the leave with its entry
• Alerting when a worker departs a restricted area

For detailed information, see On Geofence Leave.

​

Geofence Events

The two geofence events behave differently from the other eight and are worth calling out. Availability. Geofence is not generally available yet. It is enabled for MileApp internal staff and explicitly allowlisted pilot organizations. Outside the rollout the two options do not appear in the event dropdown and the geofence API returns 404. Contact MileApp support if you would like your organization included. Webhook only. Webhook is the only automation type accepted for On Geofence Entry and On Geofence Leave. Every other type is rejected with a 400 error. A geofence group is required. Instead of a Flow, a geofence automation is scoped to exactly one geofence group, chosen in the Geofence Group picker. The automation fires only for geofences in that group, so different groups can feed different integrations. One automation cannot watch more than one group. Entry fires once per visit. A worker who is already inside a geofence does not re-trigger the entry on every position report. They must leave and re-enter. A leave never fires without its entry. If a worker passes through a geofence without staying past the dwell time, no entry is sent, and no leave is sent either.

​

Event-Flow Matching

Important: For task-related events (On Task Created, On Task Assigned, On Task Finished), the automation will only be triggered if the task’s Flow matches the Flow selected in the automation configuration. This allows you to create Flow-specific automation rules. For example:

• If you configure an automation with Event “On Task Created” and Flow “Delivery”, the automation will only trigger when a task with Flow “Delivery” is created
• Tasks with other Flows (e.g., “Pickup”, “Visit”) will not trigger this automation

​

Common Use Cases

​

Workflow Automation

Chain multiple tasks together by using “On Task Finished” to automatically create follow-up tasks.

​

External System Integration

Use webhook automation types with any event to send real-time data to external systems like WMS, ERP, or custom applications.

​

Notification Systems

Trigger notifications to relevant stakeholders when specific events occur in your workflow.

​

Data Synchronization

Keep external databases synchronized with MileApp data using Data Source and Task events.