Plot accounts, sites, and assets, then plan the day on the same map: pick the stops, get the road route and the drive time to each one. In Screen Flows, on Lightning pages, and in Experience Cloud, configured with clicks.
Tuesday, five site visits around Austin. The rep picks the five sites on the map, and the Map draws the road route between them, stop by stop.

Click markers to add stops, or draw a box or a lasso around several at once. Start from any record on the map or from your own position. Up to 25 stops.
The Route panel gives the distance and drive time to each stop. With a Mapbox key, it adds an arrival time at every stop and the length of the whole day, visits and lunch included.
Drag the stops into a new order, or let the Map optimize it. Open any stop in Google Maps or Waze, or export the day as a CSV.
Routing runs on the Leaflet map. Avonni hosts no routing service: the request goes from your org to the provider you picked.
Read the routing setupThe same map engine follows you across Salesforce. What changes is where it lives and how you add it, not what it can do.

Drop the map component onto any Flow screen and point it at a collection of records. Users see them plotted, select a marker, and pass the choice downstream, or build a route through them on the screen.
Flow Screen ComponentsSee the Map for Flows landingRead the Screen Flow components guide
Build it visually with the dcMap component in Dynamic Components, wire a query with no Apex, and drop the result onto any Lightning page in App Builder.
Dynamic Components
Add the AX-Map to any Experience Cloud page. It respects your sharing rules and guest access, so external users see only the locations they should.
Experience Cloud Components<avonni-dd-leaflet-map query={accountQuery} mapping={mapping} cluster routing search-fields={searchFields}> </avonni-dd-leaflet-map>
Developers drop avonni-dd-leaflet-map straight into an LWC template with documented attributes. Same map, in the markup you already own.
LWC ComponentsTick an industry and the map falls to the sites that match. Search and filters sit in the header or right on the map, so it keeps its full width.
Click a pin and its popup shows the fields you picked, so the team reads the record without leaving the page.
In a screen flow, the user picks a marker and the next screen opens on that site, record already loaded.
Real screens built with Avonni, one industry job each. Open one to see it run and copy its code, or try the Map on its own and change any property live.
Salesforce's standard map component plots records as pins on Google Maps. Avonni adds a second map engine, clustering, drawing, filters on the map, and routes between your records, all configured with clicks.
See it on a FlowIt ships across the Avonni suite. The Flow version is in Flow Screen Components, the Lightning-page version in Dynamic Components, and the portal version in Experience Cloud Components. One subscription covers all three.
Both. Pick Google Maps or Leaflet per map. Leaflet uses OpenStreetMap tiles, which you allow by adding the tile URL to your org's Trusted Sites. Clustering, drawing, and route planning run on Leaflet.
Yes. Users pick up to 25 stops on a Leaflet map and get the road route, with the distance and drive time to each stop. With a Mapbox key, the panel also gives an arrival time at every stop and works out the fastest order for routes of up to 12 stops. An admin turns routing on once per org, with an OpenRouteService or Mapbox key.
Only once an admin turns it on. Each route request goes from your org to the provider you picked, OpenRouteService or Mapbox, with your own key, and carries the coordinates of the stops. Avonni hosts no routing service, and each route counts against your plan with the provider.
Yes. Salesforce Maps is a separate product, licensed per user, with automated routes and schedules. The Avonni Map adds routes to the map you already configure in a flow, on a page, or on a portal, with your own provider key.
Yes. With Leaflet, drawing tools let users sketch shapes on the map, and you can save the result back to Salesforce as a file on a record. When they plan a route, users can also draw a box or a lasso to add every marker inside it as a stop.
See where another component runs, and how it is configured.
Install free from the AppExchange and add a map to your first Flow, page, or portal today. Talk to us when you are ready to scale.