Here's a list of Route4Me activities or events that are supported and logged by the Activity Feed. Keep in mind that these activities don't account for all the actions that could be done in a Route4Me account. They are merely a fraction of it.
Included for each activity is the constant string value of the activity_type property when you receive the callback payload from your Activity Feed's callback URL and with a description of how the activity came about.
| No. | Activity Type | Constant String | Description |
|---|---|---|---|
| 1 | Remove Avoidance Zone | "area-removed" | Triggered/logged when removing an existing avoidance zone. |
| 2 | Create New Avoidance Zone | "area-added" | Triggered when adding/creating a new avoidance zone. |
| 3 | Edit Avoidance Zone | "area-updated" | Triggered when updating (renaming, changing points) an existing avoidance zone. |
| 4 | Remove Address From Route | "delete-destination" | Triggered when deleting/removing an address or stop within a route. |
| 5 | Add New Address | "insert-destination" | Triggered when adding a new stop within a route. |
| 6 | Route Deviation | "destination-out-sequence" | Triggered when a driver marks an address as visited before any other ones before it in the sequence. This means that the driver didn't follow the series of addresses in a route. |
| 7 | User Arrived Early | "driver-arrived-early" | Triggered when a driver arrives early at an address and marks it as "visited". |
| 8 | User Arrived Late | "driver-arrived-late" | Triggered when a driver arrives late at an address and marks it as "visited". |
| 9 | User Arrived On Time | "driver-arrived-on-time" | Triggered when a driver arrives on time at an address and marks it as "visited". |
| 10 | Geofence Triggered Check Out | "geofence-left" | Triggered when a driver leaves a geofenced area. |
| 11 | Geofence Triggered Check In | "geofence-entered" | Triggered when a driver enters a geofenced area. |
| 12 | Mark Address Departed | "mark-destination-departed" | Triggered when an address is marked as "departed". |
| 13 | Mark Address Visited | "mark-destination-visited" | Triggered when an address is marked as "visited". |
| 14 | Created Team Member | "member-created" | Triggered when creating a new user. |
| 15 | Delete Team Member | "member-deleted" | Triggered when deleting an existing user. |
| 16 | Modified Member | "member-modified" | Triggered when updating the details of an existing user. |
| 17 | Change Address Sequence | "move-destination" | Triggered when manually changing the order or sequence of a stop within a route. |
| 18 | Note Insert | "note-insert" | Triggered when adding a note to a stop or address within a route. |
| 19 | Delete Route | "route-delete" | Triggered when removing/deleting a route. |
| 20 | Route Optimized | "route-optimized" | Triggered when manually reoptimizing a route or refreshing its directions. Also triggered when reordering the sequence of stops or addresses within a route. |
| 21 | Assigned Other User To Route | "route-owner-changed" | Triggered when assigning a user to an existing route. |
| 22 | Route Duplication | "route-duplicate" | Triggered when duplicating an existing route. |
| 23 | Update Address Attribute | "update-destinations" | Triggered when you add custom data to an address. |
| 24 | User Message | "user_message" | Triggered when a user communicates or chats with its team members using the Two-Way Real-Time Chat feature or through a custom application that uses the Activity Feed resource of the Route4Me API. |
| 25 | Route Merging | "route-merge" | Triggered when two or more routes are consolidated to create one route. |
| 26 | Rename Route | "route-update" | Triggered when renaming a route. |
| 27 | Approved To Execute | "approved-to-execute" | Triggered when a user approves a route to start executing. |