Woosmap
LogisticsConnect AI agents to the Woosmap location platform to manage store and asset data and search it by proximity or attribute. Agents route customers and work to the nearest capable location.
What This Integration Enables
Woosmap is not a road network API that happens to store points. It is a database of your locations with a routing layer attached, and the distinction changes what you can build. Assets are your stores, agencies, pickup points and chargers, each carrying a position, a structured address, contact details, types, tags, arbitrary custom properties, localized names and a full weekly opening schedule. Zones are drawn territories, expressed as Well Known Text polygons and attached to an asset, which means a coordinate lookup can return the store whose territory contains the customer rather than the store that happens to be closest. Retail knows why that matters. Nearest is frequently the wrong answer: the nearest branch may be closed today, may not carry the item, may be a franchise that does not serve that postcode, or may be across a river that the distance calculation does not care about.
Because the asset collection is yours, the search surface is genuinely expressive. Search Assets accepts the Woosmap query language, so clauses on name, type, tag, city, country, store identifier and your own custom user properties combine with AND, OR and NOT, and the result can be biased to a point with a radius or restricted to assets near an encoded polyline along a route. Autocomplete Assets does type-ahead over your own store names including their localized forms and returns the matched substrings so the input can be highlighted. Alongside that sits worldwide address work: locality autocomplete with a public identifier you resolve through Get Locality Details, forward and reverse geocoding with optional boundary shapes and sub-building expansion for apartment validation, nearby place search across transport, retail, food and drink, education, hospitality, medical and tourism categories, traffic-aware routes and distance matrices, isochrone catchment polygons, and IP geolocation with time zone resolution for visitor context. Treated as connectors in a flow, that combination lets one agent own the whole path from a typed postcode to a named branch with its opening state.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Publishing the Store Network From the System That Owns It
The ERP holds the truth about which stores exist, when they open and who to call. The agent takes the nightly export, builds a Woosmap asset payload with positions, structured addresses, types, tags, custom properties, localized names and opening hours, and splits it across calls where the payload approaches the 15 MB per-request limit. For an ordinary night with additions and amendments, Update Assets applies the batch, matched on identifier, and rejects the whole batch if any asset in it does not already exist, which is a useful guardrail rather than an inconvenience. For a full republish, Replace All Assets swaps the entire collection atomically. Either way the locator, the call centre lookup and the dispatch logic all read the same collection.
Routing a Customer to the Branch That Owns Their Address
An order or an enquiry arrives with a postal code. The agent runs Autocomplete Localities on the partial input, resolves the chosen prediction through Get Locality Details to get coordinates and structured components, then searches the asset collection for the store whose zone contains that point rather than the nearest pin. Where several branches qualify, the agent narrows with the query language on tag or custom property, checks the opening state returned on each asset, and ranks the survivors with Get Distance Matrix so the answer is a store that is open, stocked and reachable. Get Isochrone confirms the address falls inside the service area before a delivery slot is offered rather than after it has been promised.
Checkout Address Validation That Catches the Flat Number
A Shopify order carries an address a customer typed at checkout. Geocode Address resolves it to coordinates and structured components, restricted to the countries you actually ship to and the place types you accept, noting that only the first 20 tokens within 150 characters are processed so an overlong free-text field is worth trimming first. Where the address is a building with multiple units, Reverse Geocode Coordinates with Sub Buildings enabled returns every flat sharing that street number, so a missing unit number becomes a question asked before dispatch instead of a failed delivery afterwards. Geolocate IP Address and Get Time Zone add the visitor's approximate location and local offsets, which is what tells the agent whether a same-day slot is still realistic.
Human-in-Loop Highlight
Two actions in this connector can empty a project. Replace All Assets deletes every existing asset and imports the payload in its place, atomically, which makes it the right way to publish a verified full export and the fastest way to publish a broken one. Delete Assets can clear the whole collection, guarded only by a Delete All Assets confirmation flag. The dangerous case is not a person clicking the wrong thing. It is a nightly ERP export that came up short because a join failed or a filter changed, arriving as a technically valid payload that publishes a store locator with real branches missing from it, and returns success. There is a second, quieter version of the same failure: assets and zones are separate objects, so a store can survive the asset sync and lose the zone attached to it, which stops customers being routed to a branch that still appears on the map. So the agent diffs before it publishes. It compares the incoming payload against the live collection from Search Assets, cross-checks List Zones for orphaned stores, and on any net removal or lost zone it stops and asks retail operations in Slack: "Tonight's store sync removes [N] assets and leaves [M] stores without a zone. Removals: [list]. Zone orphans: [list]. Are these closures, or is the export short? Approve to publish, or hold." Approving a closure takes a moment from somebody who knows the estate. Discovering it from a customer takes considerably longer.
Agent Capabilities
23 actionsStore and Asset Records
5- Get Asset Retrieves a single asset by identifier and returns it as a GeoJSON Feature carrying position, address, contact details, types, tags, custom user properties, localized names and the full weekly opening schedule. Use it to read the current state of one store before amending it.
- Create Assets Creates one or more assets in a single batch. Each asset needs a unique identifier, a name and a position, and can also carry a structured address, contact details, types, tags, arbitrary custom properties, localized names and opening hours. The payload is limited to 15 MB per request, so large imports are split across several calls.
- Update Assets Updates one or more existing assets in a single batch, matched on identifier. Every asset in the payload must already exist or the whole batch is rejected, which makes this the safe action for keeping opening hours, contact details, tags and custom properties in step with the source system.
- Replace All Assets Atomically replaces the entire asset collection with the supplied assets. Every existing asset is deleted and the payload is imported in its place, which is the clean way to publish a verified full nightly export. The operation is destructive, so incremental changes belong in Update Assets.
- Delete Assets Deletes assets from the project, either a named list of identifiers or the whole collection. Deleting everything requires the Delete All Assets confirmation to be enabled, which guards against wiping a project when no identifiers are supplied.
Asset Search
3- Search Assets Searches your stored assets and returns them as a GeoJSON FeatureCollection. Results can be filtered with the Woosmap query language, combining clauses on name, type, tag, city, country, store identifier and custom user properties with AND, OR and NOT, biased to a point with a radius, or restricted to assets near an encoded polyline. Each feature carries the address, contact details, types, tags, opening state and, when a position is supplied, the distance in meters. Results page at up to 300 assets.
- Autocomplete Assets Provides type-ahead suggestions over your own asset names, including the localized names stored on each asset, and returns the matched substrings so the input can be highlighted. This is the action behind store pickers and search boxes where the user is part-way through typing a branch name. Returns up to 50 predictions per call.
- Get Assets Bounding Box Returns the smallest geographic bounding box containing every asset matching a search, as north, south, east and west coordinates. Use it to fit a map viewport to a filtered set of stores without downloading the assets themselves.
Address and Place Lookup
5- Autocomplete Localities Returns worldwide place predictions for a partial query, matching on whole words or substrings, built for as-you-type address, city, postal code and point of interest input. Each prediction carries a public identifier for a follow-up lookup, and results can be restricted to countries, filtered by type and biased towards a position.
- Get Locality Details Retrieves the full record behind an autocomplete prediction using its public identifier, returning the formatted address, coordinates, structured address components and optionally the administrative or postal boundary shape. For postal codes in territories such as the United Kingdom and Ireland, the response also lists the individual addresses inside the code, each with its own identifier for a further lookup.
- Geocode Address Converts a free-form address, street, locality or postal code into coordinates and structured address components. Results can be restricted to specific countries and place types, and the optional shape field returns the boundary geometry of the matched area. Only the first 20 tokens within 150 characters of the address are processed.
- Reverse Geocode Coordinates Converts a latitude and longitude pair into the nearest address, returning the formatted address, structured components and optionally the boundary shape. Enabling Sub Buildings also returns every flat or unit sharing the same street number or building, which is how an apartment address gets validated before a courier is sent.
- Search Nearby Places Finds worldwide points of interest around a position, sorted by distance, across transport, retail, food and drink, education, hospitality, medical and tourism categories. At least one place type must be selected. Results carry name, formatted address, coordinates and address components, and are paginated so a large radius can be walked page by page.
Travel and Reachability
3- Get Route Calculates the recommended route between an origin and a destination for driving, walking or cycling, returning total distance and duration, an encoded overview polyline, per-leg details and optional turn-by-turn instructions. Intermediate waypoints can be visited in order or reordered automatically for the shortest overall trip, and supplying a departure or arrival time switches to traffic-aware durations. Alternative routes and waypoints cannot be combined in one request.
- Get Distance Matrix Calculates travel distances and durations for every combination of origins and destinations, which is the right tool for nearest-store lookups, delivery slot checks and territory assignment. Returns one row per origin with one element per destination, each carrying a status, a distance and a duration. Requests are limited to 1000 elements per second, and a departure or arrival time switches to traffic-aware durations.
- Get Isochrone Calculates the reachable area around an origin within a given travel time or distance and returns it as an encoded polygon. Use it to model catchment areas, define delivery boundaries or check whether a customer falls inside a store's service area. The contour value is read as minutes under Fastest Route and as kilometres under Shortest Route.
Territories and Zones
5- List Zones Lists the catchment, delivery and territory zones defined in the project, sorted by identifier. Each zone returns its polygon as Well Known Text along with the asset it belongs to, its description and its types. Up to 50 zones come back per call, so the offset walks larger collections.
- Get Zone Retrieves a single zone by identifier, returning the Well Known Text polygon, the asset it is attached to, the description and the zone types. Use it to inspect a delivery or catchment boundary before changing it.
- Create Zones Creates catchment, delivery or territory zones in a single batch, each linking a Well Known Text polygon to an asset so that a coordinate search can return the stores whose territory contains the customer. Polygons may be complex or multipart, which supports postcode-based territories as well as hand-drawn delivery areas.
- Update Zones Updates existing zones in a single batch, matched on identifier. Every zone in the payload must already exist or the whole batch is rejected. Use it to redraw a delivery boundary or reassign a zone to a different store.
- Delete Zones Deletes zones from the project, either a named list of identifiers or the entire collection. Removing every zone requires the Delete All Zones confirmation to be enabled, which guards against clearing a project by accident when no identifiers are supplied.
Visitor Context
2- Geolocate IP Address Estimates the geographic position of an IP address, returning approximate coordinates, a viewport, the accuracy radius in kilometres, the country, region, city and postal code where available, plus the local time zone and UTC offsets. An accuracy value of 50 kilometres or less indicates a confident match. Omit the address to geolocate the caller of the request.
- Get Time Zone Returns the time zone that applies at a set of coordinates, including the IANA identifier, the abbreviated name, the base UTC offset in seconds and the daylight saving offset in seconds. Supply a timestamp to resolve the offsets that were in effect at that moment rather than now.
Frequently Asked Questions
What can FlowRunner do with Woosmap?
FlowRunner agents can run Search Assets, Autocomplete Assets, and Get Assets Bounding Box in Woosmap, plus 20 more actions.
Does connecting Woosmap to FlowRunner require OAuth?
No. Woosmap connects to FlowRunner with an API key, no OAuth flow required.
Can Woosmap trigger a FlowRunner workflow automatically?
Woosmap doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Woosmap
$100 in credits. No card required. Connect in minutes.