ERP & Accounting
ERPNext
AvailableConnect employee identity and attendance events.
Explore data & scopeMaps & Field Operations · Google MapsAvailable
Put captured field activity into geographic context.
Configured map services support location display and route context in field workflows. Availability depends on the deployment’s map settings, provider access and device permissions. Map estimates and captured GPS evidence are different.
Google MapsConfigured service
01
Captured coordinatesDevice → SalesTOS
02
Map display requestsSalesTOS → Google Maps
03
Route or distance contextGoogle Maps → SalesTOS
SalesTOSAttendance and visit location context
Record ownership and direction are defined below. No universal two-way sync is implied.
The operational need
Why connect these systems?
Managers need to understand where recorded field activity occurred.
Gaps in captured points must not be presented as observed travel.
Provider usage and device connectivity affect map availability.
Direction, ownership, prerequisites
What data can be exchanged?
Each row is a separate scope decision. Supported workflows still require configuration; proposed records require assessment and implementation.
| Record or object | Direction | System of record | Purpose | Availability / prerequisites |
|---|---|---|---|---|
| Captured coordinates | Device → SalesTOS | SalesTOS captured event | Attendance and visit location context | Enabled workflow and device permissions |
| Map display requests | SalesTOS → Google Maps | Google for map content | Geographic display | Configured provider key and API access |
| Route or distance context | Google Maps → SalesTOS | Provider estimate | Supported route context | Configured services; legacy API eligibility reviewed |
| Optimised visit schedule | No supported exchange claimed | Not established | Potential separate planning scope | Route optimisation is not promised |
Connection design
How the connection works
The application supports configured Google map display and route/distance services. Existing route code uses legacy Directions and Distance Matrix interfaces; provider eligibility or migration needs must be checked for a new setup. A map does not replace device permission or captured event quality.
Illustrative working scenario
From system context to a useful next action.
A manager reviews recorded visit coordinates on a map. Where estimated road context is displayed, it must remain distinguishable from the points actually captured from the device.
What happens to writeback?
Map responses do not approve attendance, prove every travelled segment or automatically optimise tomorrow’s route.
Before implementation
Setup requirements
- Enabled maps configuration and authorised API key
- Provider account, API restrictions and usage responsibility
- Device location permissions and connectivity
- Review of legacy service eligibility and required migration
Use an authorised setup process for credentials. The enquiry form does not request passwords or API secrets.
Operating the agreed scope
Reliability & access
Map requests can fail because of permissions, connectivity or provider limits. Captured events and reconstructed estimates have distinct meanings. Agree operational handling of missing location and monitor the configured provider rather than promising uninterrupted tracking.
A clearer scope starts here
Questions, answered.
Google Maps integration
Is every route an actual GPS trace?
No. Captured points and estimated road segments must be interpreted separately.
Does this optimise the visit schedule?
No route-optimisation commitment is established by map display.
Are provider charges included?
Provider account and usage responsibility must be agreed in the scope.
Can a new account use the same services?
Existing code uses legacy services; eligibility or migration must be checked for the account.
What should we prepare for a Google Maps discussion?
Enabled maps configuration and authorised API key; Provider account, API restrictions and usage responsibility; Device location permissions and connectivity; Review of legacy service eligibility and required migration. Share redacted examples through an agreed channel, never passwords or API secrets in the public form.
How is Google Maps integration scope confirmed?
Review the objects and prerequisites on this page, then agree mapping, access, refresh timing and acceptance criteria. Map responses do not approve attendance, prove every travelled segment or automatically optimise tomorrow’s route.
No matching questions. Clear your search or discuss your requirements with us.
Explore the adjacent workflow
Related integrations
Reporting & Data
Excel & CSV
File import supportedStart with an approved template and a reviewable import.
Explore data & scopeCustom Systems
Custom API
Custom integration — assessment requiredDefine one useful interface between your system and field work.
Explore data & scopeYour systems. A defined scope.
Discuss This Integration Discuss Google Maps with SalesTOS.
Bring your business workflow and current setup. We’ll use them to assess the right data scope.