Geolocation Node for Workflow Builder
Yongrui Su
on April 24, 2026Your AI agent can now ask a visitor for their location as part of a workflow. The new Geolocation node prompts the visitor to share their position, saves the coordinates, and routes the workflow based on whether they allowed or declined.
How It Works
- Drag the Geolocation node from the Workflow Builder sidebar into your flow.
- When a visitor reaches that node, their browser shows a location permission prompt.
- If the visitor allows access, coordinates are captured and the workflow continues down the Success path. If they deny or the request times out, the workflow follows the Error path.
No extra setup is needed for the website widget — the embed snippet already includes the required allow="geolocation" permission.
Configuration
- Timeout — Set how long to wait for a response before routing to the error path. Default is 10 seconds (range: 1–120 seconds).
- High accuracy — Enable for GPS-level precision. May use more battery and take longer on mobile devices.
What Gets Stored
When location is captured successfully:
- Visitor profile — Latitude, longitude, and capture timestamp are saved on the visitor's profile, visible in the Leads dashboard.
- Workflow variables — VISITOR.LATITUDE and VISITOR.LONGITUDE become available for the rest of the workflow. Use them in Condition nodes, API Call payloads, AI Conversation prompts, or any text field that supports variables.
If the same visitor reaches multiple geolocation nodes in one conversation, each capture is stored independently — the profile always reflects the most recent coordinates, and the transcript shows every result.
Dashboard Transcript
Admins can see geolocation results directly in the conversation transcript. Each geolocation action shows one of three states:
- Captured — Displays the latitude and longitude the visitor provided
- Denied / unavailable — The visitor declined the request or their device could not determine a position
- Awaiting response — The workflow is still waiting for the visitor to respond to the browser prompt
Platform Support
The Geolocation node works on web-based channels only — the website widget, iframe embeds, and the chatbot page. On messaging channels (WhatsApp, Messenger, Telegram, Slack, Discord, LINE, Instagram), the node automatically routes to the Error path.
Use Cases
- Store locator — Ask for the visitor's location and return the nearest branch or pickup point
- Service area check — Verify whether a visitor is within your delivery or coverage zone before continuing the workflow
- Location-aware routing — Direct visitors to region-specific agents, content, or pricing
- Field service — Capture a technician's or customer's coordinates for dispatch or logging
Add the Geolocation node to your workflows today from the Workflow Builder sidebar.