Flowstar: Store Locator Map

A Webflow site with more than a handful of physical locations hits the same wall. The CMS will hold addresses, phone numbers and opening hours perfectly well, but Webflow has nothing that turns those records into a map a visitor can search. Geocoding, proximity sorting, marker styling and the handoff to turn-by-turn directions are all Google Maps JavaScript you write once and then maintain forever.

Flowstar: Store Locator Map is a Webflow Marketplace app that renders that map for you. Its Marketplace listing describes an interactive map built on Google Maps, with unlimited store, office or clinic locations, opening hours and contact details shown in one view, and styling controls for map colors and pins. Locations are added and edited inside the app rather than in code.

The listing names retailers, healthcare providers, restaurants and service companies as its audience, which matches the shape of the problem: several fixed addresses, each carrying its own hours and contact details, and visitors who mostly want the nearest one.

How to integrate Flowstar: Store Locator Map with Webflow

What is Flowstar: Store Locator Map? It is a Webflow Marketplace app from Flowstar that adds a searchable Google Maps locator to a Webflow site. There is a single integration path: install the app, then configure the map and enter your locations through its interface. No embed snippet goes on the page and no external dashboard is involved.

Install the app and add your locations

Installation runs through the Apps panel in Webflow. Search for Flowstar: Store Locator Map, install it, and the app opens with the controls for map appearance and location data. Everything after that happens in form fields rather than in code, which is the whole point of choosing a widget app over a hand-built map.

The Marketplace listing publishes the feature set the app ships with:

• Interactive Google Maps view: The map shows a visitor the locations nearest to them, using Google Maps as the underlying map provider.
• Unlimited locations: You can add as many stores, offices, clinics or service points as the business runs, with no documented cap on the count.
• Location detail in one view: Opening hours, contact information and directions appear together rather than sending the visitor to a separate page.
• Responsive rendering: The listing states the locator is built to work on mobile, tablet and desktop without a separate configuration for each.
• Brand styling: Map styles and pin designs are customizable, so the locator can match the rest of the site rather than sitting on it as a gray default.

That set covers the common case well. What it does not cover is where your location data lives, which is the decision worth making before you install.

Check what the app can access

The listing publishes the exact scopes the app asks for, and they are broader than a map widget might suggest. Read them against your own workspace rules before an install goes onto a client site.

• Custom code, read and write: The app can add and change custom code on the site, which is how the locator gets onto your published pages.
• Site data and publishing, read and write: The app can read site structure and trigger publishing, so its changes can reach the live site without you republishing by hand.
• CMS and Ecommerce data, read only: The app can read Collection content and Ecommerce store data, but the listing grants it no ability to write back to either.
• Assets, page data and authorized users, read only: The app can read your asset library, page-level data and information about the users who authorized it.

The listing also carries Webflow’s "Approved by Webflow" badge and an enhanced security and management note, which means the app went through review, not that Webflow endorses it.

Known limits

The significant one is data ownership. Neither the Marketplace listing nor flowstar.co documents synchronization between the app and the Webflow CMS, so your locations live in the app rather than in a Collection. That is fine for a fixed set of branches, and awkward the moment the same addresses need to appear on CMS-driven location pages as well as on the map. Flowstar publishes no public API documentation for the app either, so there is no supported way to push locations in from another system.

If the addresses have to be Collection items, Storepoint Locator maps a Webflow Collection onto its locator instead, and a custom build on the Webflow Data API keeps the data entirely yours. Flowstar lists Store Locator Map among its paid apps, priced by monthly view volume, so check the current tier on Flowstar’s pricing page before you commit a client site to it.

What you can build with the Flowstar: Store Locator Map Webflow integration

Running this app on a Webflow site gives you a searchable, branded map without writing Google Maps JavaScript or maintaining a geocoding step. The patterns below are the ones the listing is aimed at, and they share a shape: a fixed set of addresses that changes slowly, and a visitor who wants the closest one.

• Retail store locators: A map of every branch on a Webflow marketing site, so a visitor can find the nearest shop and get directions without leaving the page.
• Healthcare facility finders: Clinic and practice locations with opening hours attached, which answers the two questions a patient actually has before booking.
• Restaurant location pages: Individual venues plotted with hours and phone numbers, turning a search result into a booking or a walk-in.
• Service provider directories: Offices, depots or dealer sites for a business that operates across several regions, with pin styling that separates one type of site from another.

Pick this app when the location list is short, stable and owned by whoever manages the site. If the same addresses need to power CMS-driven location pages as well as the map, build the data layer first: start with the Webflow CMS API and render the map against your own Collection.