CAMINO AI n8n INTEGRATION: AUTOMATE CAMINO AI WITH N8N

The "Get Place Context" action retrieves rich contextual information about any geographic location based on its latitude and longitude coordinates. This is particularly valuable when you need to understand what surrounds a specific point—neighborhood characteristics, local landmarks, or general area descriptions.

Key parameters:

• Latitude: A numeric value specifying the latitude of your target location. This is required and must be a valid coordinate (e.g., 48.8566 for Paris).
• Longitude: A numeric value for the longitude of the location. Also required and expects a valid coordinate (e.g., 2.3522 for Paris).
• Options: An expandable section for additional configuration. Currently optional, allowing you to customize the context retrieval based on specific needs.

Use cases:

• Automatically enrich lead addresses with neighborhood context before sales calls
• Add location descriptions to property listings pulled from your real estate database
• Generate contextual information for travel itineraries based on accommodation coordinates

This action assists in planning complete journeys with multiple waypoints and customizable options. Whether you're routing a delivery truck through several stops or planning a tourist itinerary, "Plan a Journey" handles the complexity of multi-point route optimization.

Key parameters:

• Waypoints: Add specific geographic points that should be included in the journey. Click "Add Waypoint" to specify each stop along the route. While optional, waypoints are essential for meaningful journey planning—without them, you're just connecting a start and end point.
• Options: Additional configurations that modify how the journey is calculated. Use this to specify preferences like avoiding highways, prioritizing scenic routes, or accommodating specific vehicle types.

Use cases:

• Plan optimized delivery routes for e-commerce fulfillment with multiple drop-off points
• Generate day-trip itineraries for tourism platforms based on selected attractions
• Create efficient field service schedules that minimize travel time between appointments

The "Query Points of Interest" action is a powerhouse for location-based searches. It allows you to find nearby places using natural language queries combined with geographic parameters—making it incredibly intuitive to search for "coffee shops," "gas stations," or "coworking spaces" around any coordinate.

Key parameters:

• Query Type: Select how you want to search. "Natural Language Query" is the most flexible option, letting you describe what you're looking for in plain English.
• Query: A text field where you enter your search terms (e.g., "Italian restaurants," "pharmacies open late," "parking garages"). This is required for the action to function.
• Latitude & Longitude: Numeric values defining the center point of your search. Both are required.
• Radius: Defines the search radius in meters around your coordinates. Required—and crucial for controlling how wide your POI search extends.
• Options: Additional properties to refine your query results.

Use cases:

• Find all gyms within 2km of a new office location for employee benefits research
• Automatically suggest nearby restaurants when a meeting is scheduled in an unfamiliar area
• Enrich travel bookings with lists of attractions near the booked hotel

💡 TIP: Start with a reasonable radius (1000-3000 meters) and adjust based on results. Too small and you might miss relevant POIs; too large and you'll get overwhelming results that slow down your workflow.

"Calculate Relationship" computes spatial relationships between two geographic points—giving you distance, direction, travel time, and descriptive context. This is the go-to action when you need to understand how two locations relate to each other spatially.

Key parameters:

• Start Latitude & Start Longitude: Numeric inputs defining the first location. Both are required.
• End Latitude & End Longitude: Numeric inputs for the second location. Both are required.
• Include: A checkbox selection allowing you to specify what data to return. Options include:
  • Distance: The spatial distance between the two points
  • Direction: The compass direction from start to end
  • Travel Time: Estimated time to travel between points
  • Description: A human-readable description of the relationship

Use cases:

• Calculate delivery ETAs by determining travel time from warehouse to customer address
• Qualify sales leads by distance from your nearest office or service area
• Build alerts that notify when two tracked assets are within a certain distance of each other

The "Get a Route" action retrieves detailed routing information between two coordinates. Unlike "Plan a Journey" which handles multiple waypoints, this action focuses on providing comprehensive route data for point-to-point navigation.

Key parameters:

• Start Latitude & Start Longitude: Numeric values for the route's origin. Both required.
• End Latitude & End Longitude: Numeric values for the destination. Both required.
• Options: Additional configuration for route preferences—though currently no properties are set by default, you can expand this to customize routing behavior.

Use cases:

• Embed turn-by-turn directions into automated customer communications
• Calculate multiple route options for logistics planning tools
• Generate route data for mobile app integrations that need navigation details

"Search for Places" enables flexible location searches using free-form text queries. This action is perfect when you need to convert a place name, address, or general location description into structured geographic data.

Key parameters:

• Search Type: Choose your search method. "Free-Form Query" allows natural text input for maximum flexibility.
• Query: The text field where you enter your search (e.g., "Eiffel Tower," "123 Main Street, Boston," "Central Park"). Required.
• Limit: A number defining the maximum results to return. Defaults to 50, which is usually more than enough for most use cases. This is optional but useful for controlling response size.

Use cases:

• Convert customer-provided addresses into standardized coordinates for mapping
• Look up venue locations for event management workflows
• Geocode lists of addresses from spreadsheets or CRM exports