Location Input Block

What it does: Request the user's geographic location through their browser, collecting latitude, longitude, and optionally device details.

When to Use This

Use Location Input when you need:

• ✅ User's current geographic position
• ✅ Delivery or pickup address coordination
• ✅ Location-based recommendations
• ✅ Service area verification
• ✅ Nearby store/branch finder
• ✅ Local weather or events

Example: A food delivery bot that needs the customer's location to find nearby restaurants, or a service app that checks if the user is within the service area.

Key Features

• Browser Geolocation: Uses device GPS and network location
• User Permission Required: Respects browser privacy settings
• Precise Coordinates: Returns latitude and longitude
• Device Details: Optional device information collection
• User-Friendly Prompts: Customizable question and button labels

Setup Guide

Configuration Settings

In the Settings Panel:

1. Enter your question

   • The text shown to users requesting location
   • Default: "Would you like to share your location?"
   • Customize based on your use case
   • Example: "Where would you like your order delivered?"

2. Yes Button Label

   • Text for the confirm button
   • Default: "yes"
   • Can customize: "Share Location", "Allow", "Enable Location"

3. No Button Label

   • Text for the decline button
   • Default: "no"
   • Can customize: "No Thanks", "Decline", "Skip"

4. Allow Device Details

   • Toggle switch to enable/disable device information collection
   • When enabled, collects browser and OS information
   • Default: Disabled
   • Useful for analytics and debugging

How It Works

User Flow

1. Block Displays:

   [Your custom question]
   Would you like to share your location?
   
   [Yes] [No]

2. User Clicks "Yes":

   • Browser shows native permission prompt
   • "Allow [Your Site] to know your location?"
   • User grants or denies permission

3. If Permission Granted:

   • Device determines location using GPS, WiFi, cell towers
   • Returns coordinates to your workflow
   • Continues to next step

4. If Permission Denied:

   • User proceeds without sharing location
   • Workflow continues (handle this case in your logic)

Common Use Cases

Food Delivery

Find nearby restaurants:

Configuration:

• Question: "Where should we deliver your food?"
• Yes Button: "Share My Location"
• No Button: "Enter Manually"
• Device Details: No

Workflow:

1. User shares location
2. Query restaurants within delivery radius
3. Display options sorted by distance
4. Proceed with order

Store Locator

Find nearest physical location:

Configuration:

• Question: "Find your nearest store"
• Yes Button: "Use My Location"
• No Button: "Search by City"
• Device Details: No

Workflow:

1. Get user location
2. Calculate distances to all stores
3. Show 3 nearest locations with directions
4. Allow selection for pickup/visit

Service Area Check

Verify coverage availability:

Configuration:

• Question: "Check if we serve your area"
• Yes Button: "Check My Area"
• No Button: "Enter ZIP Code"
• Device Details: No

Workflow:

1. Capture location
2. Check against service area polygons
3. If covered: Continue with service
4. If not: Show alternative options or waitlist

Privacy and Permissions

Browser Permissions

How It Works:

• Browser shows permission prompt first time
• User can "Allow" or "Block"
• Permission is remembered for the site
• Users can revoke in browser settings

Handling Blocked Permission:

• Provide alternative input method
• Ask for ZIP code or city
• Show manual address entry
• Continue workflow gracefully

Privacy Best Practices

1. Be Transparent: Clearly explain why you need location
2. Provide Alternatives: Don't make location mandatory
3. Secure Storage: Don't store unnecessarily
4. Clear Purpose: Only request when needed

Troubleshooting

Best Practices

• HTTPS Required - Geolocation API needs secure connection
• Clear Value Proposition - Explain why you need location
• Fallback Options - Always provide alternative
• Timely Request - Ask when relevant, not immediately
• Privacy First - Be transparent about data usage

The Location block is perfect for building location-aware, personalized experiences in your workflows!