How to use Make.com for Pothole Repair
You rely on municipalities reporting potholes, but tracking those specific geographic coordinates and dispatching the closest crew is a manual nightmare.
π‘ Why This Actually Matters
Pothole repair is entirely a game of routing efficiency. If you're sending a crew across town to patch a hole while another crew is literally two blocks away, you're burning through expensive asphalt and diesel fuel for absolutely no reason.
Make.com acts as an automated logistics dispatcher. When a new work order drops with a location, Make immediately pings the Google Maps API, calculates which of your trucks is currently closest, and shoots a Telegram message to that specific foreman with a tap-to-navigate link. You patch more holes per day with zero extra dispatch overhead.
The Blueprint
- π Trigger: New pothole repair request submitted via Webflow form with GPS coordinates.
- πΊοΈ Action: Calculate distance to your three active field crews using Google Maps API.
- π± Action: Send a Telegram alert to the closest crew with a one-tap navigation link.
The Geo-Dispatcher
Architecture MapThis is the high-level structural flow of your automation. Build this sequence in Make.com:
Webhook (Receive form) -> HTTP Request (Google Maps API Distance Matrix) -> Telegram (Send Message with Coordinates)π οΈ Actionable Toolkit: Setup Guide
Follow these exact steps to implement this blueprint in Make.com:
Create a new scenario in Make.com and add a Custom Webhook trigger.
In the HTTP module for the Google Maps Distance Matrix API, paste the JSON structure below to evaluate travel times for all 3 crews simultaneously.
{
"destinations": [
"{{1.crew_1_lat}},{{1.crew_1_lng}}",
"{{1.crew_2_lat}},{{1.crew_2_lng}}",
"{{1.crew_3_lat}},{{1.crew_3_lng}}"
],
"origins": [
"{{1.pothole_lat}},{{1.pothole_lng}}"
],
"key": "{{env.GOOGLE_MAPS_API_KEY}}"
}Set up an array iterator to evaluate the travel time for each active crew.
Add the Telegram module to message the foreman with the shortest travel time.