FlowRunner
PricingContact
Theme
Start Free

Waze Deep Links

Utilities & Personal

Build Waze deep links entirely offline, with no API key, account, or external call. Agents attach turn-by-turn navigation to dispatch records, tickets, and customer messages.

4 actions No credentials available
A delivery run is assigned to a driver for the current shift
Agent reads the drop coordinate and the vehicle assigned to the run
Agent compares the route preferences it is about to encode against the fleet policy on file for that vehicle class
Agent builds a turn-by-turn link with Create Navigation Link using the matching vehicle profile and avoidances
Agent sends the link to the driver by SMS and writes it onto the job ticket
When the encoded preferences do not match the vehicle's policy, the dispatcher picks the profile before the link is sent

What This Integration Enables

Waze Deep Links builds Waze navigation links inside FlowRunner from the coordinates and vehicle data your flow already has. There is no API key, no account and no external call, so a dispatch flow that hands drivers a route has nothing to provision, nothing that expires mid-shift and no third-party dependency between the job being created and the driver being told where to go. Where Apple Maps is the ecosystem you send a customer into, Waze is the one professional drivers already run, and its parameters reflect that: vehicle type including taxi and motorcycle profiles, and documented avoidances for tolls, ferries, freeways, dangerous turns and unpaved roads. That set is a fleet policy expressed as a URL. The connector also does something no other mapping deep link does, which is route a person to their own saved Home or Work place without the automation ever knowing, storing or transmitting that address.

Without FlowRunner

Addresses that mislead Depots, gates and rural sites resolve to the wrong side of a fence
Preferences left to the driver Toll, ferry and unpaved road choices are made ad hoc at the wheel
Home and work stored in systems Staff home addresses get copied into dispatch records to send them home

With FlowRunner

Coordinate-first routing The driver is routed to the exact bay, not to the nearest postal match
Policy encoded in the link Vehicle profile and avoidances are set once and travel with every job
No addresses to hold Return-to-home routing resolves on the driver's own device, so nothing is stored

Use Case Scenarios

Routing to a bay, not a building

A 3PL dispatches collections from sites whose postal addresses land a driver at a reception door on the wrong side of a large yard. An agent reads the gate coordinate stored on the site record in Airtable, calls Create Navigation Link with that coordinate and the avoidances configured for the vehicle class, and sends the resulting universal link to the driver through Twilio. The universal link opens the Waze app when it is installed and the Waze Live Map otherwise, so the same message works for a subcontracted driver whose device the dispatcher has never seen.

Fleet policy that travels with the job

An operator runs a mixed fleet: vans that can take any road and box trucks that cannot. The agent selects the vehicle profile and the avoidance set from the vehicle record rather than from a default, so a box truck run is built with unpaved roads and dangerous turns excluded while a van run is not. When a job is reassigned to a different vehicle mid-shift, the agent rebuilds the link with the new profile and replaces the one on the ticket in Onfleet. The policy lives in the record, not in a driver's habit.

End of shift, without holding anyone's address

At the end of a run the agent sends each driver a Create Favorite Navigation Link that routes them to their own saved Home place. Waze resolves the saved place on the driver's device, which means the dispatch system holds no home addresses at all, the same link is reusable across the whole crew, and nothing in the message reveals where anybody lives. This one is only correct for staff who have saved that place. It is not a link to send a customer, because there is no way to know what their saved Home is or whether they have one.

Human-in-Loop Highlight

The gate here is the vehicle profile, because a routing preference is a physical instruction to a person driving several tonnes of vehicle. Create Navigation Link encodes vehicle type and the avoidances for tolls, ferries, freeways, dangerous turns and unpaved roads. Get those wrong and the driver is not shown an error, they are shown a route, and the cost shows up as a ferry fare nobody approved, an hour lost on a diverted run, or a truck committed to a road it should not be on. So when the profile the agent is about to encode differs from the fleet policy recorded for the assigned vehicle, the agent does not silently prefer either one. It holds the message and asks the dispatcher through Slack: "Run 8802 is assigned to truck TR-14, policy says avoid unpaved and ferries. The route generated from the customer's preferred approach permits both. Send the policy route, send the customer route, or reassign?" The agent has done the work of noticing. The person who owns the fleet makes the call, and this is exactly the moment a digital andon cord is for.

Agent processes routinely
Detects exception requiring judgment
Clear match Continues automatically
Ambiguous Routes to human via Slack
Human decides
Agent resumes with decision

Agent Capabilities

4 actions

Search

1
  • Create Search Link Builds a link that opens Waze with a search for an address, business name or place, optionally biased towards a coordinate so ambiguous names resolve to the right area. Turning on Start Navigation makes Waze begin routing to the match rather than only showing it. Returns the universal link plus the web and app variants and the parameters used. Used when the destination is known by name and the exact point is not stored.

Navigation

2
  • Create Navigation Link Builds a link that starts turn-by-turn navigation to an exact coordinate, which is the most reliable way to route a driver to a gate, depot or delivery bay that has no clean postal address. Supports the documented routing preferences for vehicle type and for avoiding tolls, ferries, freeways, dangerous turns and unpaved roads. Latitude and longitude are range-checked before the link is produced. This is the workhorse action for dispatch.
  • Create Favorite Navigation Link Builds a link that starts navigation to the recipient's own saved Home or Work address. The saved place resolves on the recipient's device, so the automation never needs to know or store it, the same link is safe to reuse across an entire crew, and it reveals nothing about where any of them live. Used for end-of-shift and return-to-base messaging.

Map Views

1
  • Create Map View Link Builds a link that opens the map centred on a coordinate at a chosen magnification without starting navigation, which suits telling somebody where an incident, asset or venue is rather than telling them to drive there. Magnification runs from 6 for the closest view to 8192 for the widest, the inverse of most mapping services, and both the coordinate and the magnification are validated before the link is produced.

Frequently Asked Questions

What can FlowRunner do with Waze Deep Links?

FlowRunner agents can run Create Search Link, Create Navigation Link, and Create Favorite Navigation Link in Waze Deep Links, plus 1 more action.

Does connecting Waze Deep Links to FlowRunner require OAuth?

No. Waze Deep Links needs no credentials at all, so there is no key to obtain, store, or rotate.

Can Waze Deep Links trigger a FlowRunner workflow automatically?

Waze Deep Links doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Waze Deep Links

$100 in credits. No card required. Connect in minutes.