Resources · n8n integration

Camino AI n8n integrationAutomate Camino AI with n8n.

Your agent knows what to do, but not where to go. The Camino AI n8n integration fills that gap with 6 operations spread over 4 resources: place search, plain language questions about points of interest, spatial math between two coordinates, and route or journey planning. Location becomes a field a workflow can act on.

Community node This node is not shipped with n8n: it is a community package (n8n-nodes-camino) you install from Settings › Community nodes on a self-hosted instance. npm

Try the Camino AI integration on n8nSee the 6 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the Camino AI n8n integration actually do?

Camino AI turns geography into something a workflow can read. The n8n node exposes 6 operations grouped into 4 resources: Search to find places, Query to ask about points of interest, Spatial to compare two coordinates or describe a location, and Route to get directions between a start and an end point. Every operation runs inside a normal n8n workflow, next to the nodes you already use.

The first pattern is address cleanup at scale. A column of half typed addresses goes into Search for places, and what comes back is a set of real places with coordinates you can store. Pull the raw list from Google Sheets, run the search, write the result back to the same row. Nobody opens a map by hand again.

The second pattern is answering a question with a place. Query points of interest takes something like "coffee near me" and a set of coordinates, and returns the points that match. Drop it behind an AI Agent and the agent stops guessing at street names. Turn on Generate Answer and you get a readable summary instead of a raw list, which is what you want if the answer ends up posted in Slack.

The third pattern is logistics. Calculate spatial relationship gives distance, direction and travel time between two points, so a workflow can sort jobs by how far away they are. Plan a journey goes further and orders several waypoints with a purpose attached to each one, and Get a route returns the actual route by car, bike or foot.

Where does this stop? The node covers 6 operations and nothing else. If Camino AI exposes an endpoint the node does not, the HTTP Request node calls it directly and reuses the same credential through predefined authentication, so you stay on one set of keys. There is also no Camino AI trigger node, so a workflow never starts from Camino AI itself.

One practical note before you build: this is a community node, published as the npm package n8n-nodes-camino. It installs on a self-hosted instance, and n8n Cloud only accepts verified community nodes. If you are still weighing platforms, the n8n review covers that hosting question in detail.

Connect

How do you connect Camino AI to n8n?

  1. 01

    Install the community package

    The node is not bundled with n8n. Open Settings, go to Community nodes, and install the npm package n8n-nodes-camino, currently version 0.1.1. This works on a self-hosted instance, whether you run n8n through Docker or npm. On n8n Cloud, only verified community nodes can be installed, so check that before you plan the rest of the workflow. Once the package is in, Camino AI shows up in the node panel like any other node.

  2. 02

    Create the credential once

    Open the Credentials menu in n8n and create a Camino AI credential. A credential is created once and reused in every workflow that needs it, so you never paste the same secret twice. When you add the Camino AI node to a canvas, it offers that credential in its dropdown list, and you pick it there. If several people build on the same instance, creating the credential once also means one place to rotate it later.

  3. 03

    Wire the node into a workflow

    Camino AI has no trigger node, so the workflow starts somewhere else: a Schedule Trigger firing at a fixed interval, an n8n Webhook called by another service, or the trigger of another tool. Then add the Camino AI node, pick the resource and the operation you need, and feed the fields from the incoming item with an expression such as {{ $json.address }}. A field marked required stops the node from running when it is empty, so map those first.

Actions

What can the Camino AI node do?

The Camino AI node exposes 6 operations across 4 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.

Resources × operations matrix
ResourceGet Place ContextGet RoutePlan JourneyQuery POICalculate RelationshipSearch Places
Search✓
Query✓
Spatial✓✓✓
Route✓

Query

1 operation
02

Query points of interest

query.queryPoi

What you see in n8n

Notes & use cases

Asks a natural language question about points of interest, or pulls specific OpenStreetMap elements by ID, and returns what matches.

Key parameters

  • Query: required, the natural language query, for example coffee near me.
  • OSM IDs: required, comma separated OpenStreetMap IDs such as node/123,way/456 or plain 123456789.
  • Query Type: natural for the language query, osmIds to target known elements.
  • Latitude, Longitude, Radius: the center of the search and how far around it to look, in meters, for example 2000.
  • Generate Answer and Rank Results: return a readable answer summary, and let AI rank results by relevance.
Use cases
answering a visitor question in a support workflow without a human opening a map.

Spatial

3 operations
03

Calculate spatial relationship

spatial.relationship

What you see in n8n

Notes & use cases

Compares two coordinates and returns how they relate: how far apart they are, in which direction, and how long the trip takes.

Key parameters

  • Start Latitude and Start Longitude: required, the starting point, often {{ $json.lat }} and {{ $json.lon }}.
  • End Latitude and End Longitude: required, the ending point of the comparison.
  • Include: pick what comes back, among distance, direction, travel_time and description.
Use cases
ranking open field jobs by travel time from the technician who is on shift, then routing the closest one first.
04

Get place context

spatial.context

What you see in n8n

Notes & use cases

Describes what a single location is like, rather than comparing it to another one. You give a point, you get context around it.

Key parameters

  • Latitude and Longitude: required, the location to describe.
  • Context: extra context for the query.
  • Include Weather and Weather Forecast Type: add current weather and a forecast, either daily or hourly, which is what makes this operation worth calling the day before a site visit.
  • Radius and Time: how wide to look, and a time value such as 2020-01-01, 2020.. or 2020..2024.
Use cases
deciding the evening before whether an outdoor installation slot still makes sense at that address.
05

Plan a journey

spatial.journey

What you see in n8n

Notes & use cases

Takes several stops and orders them into one optimized journey, instead of treating each leg separately.

Key parameters

  • Waypoints: the stops of the journey, added one by one with Add Waypoint.
  • Latitude, Longitude and Purpose: required on each waypoint, the coordinates plus why the journey stops there.
  • Time Budget: how much time the whole journey is allowed to take.
  • Transport Mode and Preferences: how the person travels, and a comma separated list of preferences.
Use cases
building a sales rep's day from the accounts that asked for a visit, each stop carrying its own purpose.

Route

1 operation
06

Get a route

route.getRoute

What you see in n8n

Notes & use cases

Returns the route between one start point and one end point, which is the simple case when there is nothing to optimize.

Key parameters

  • Start Latitude and Start Longitude: required, where the trip begins.
  • End Latitude and End Longitude: required, where it ends.
  • Mode: transport mode, one of car, bike or foot.
  • Include Geometry: adds the detailed route geometry, which you need if something downstream draws the route on a map.
Use cases
attaching walking directions to a delivery confirmation message, without geometry when only the summary matters.
Need help

Need help automating Camino AI with n8n?

A person reads every message.

FAQ

Camino AI and n8n, the usual questions

01Is the Camino AI n8n integration free?
Yes on the n8n side. n8n costs nothing extra to add this node, and the workflow you build is identical whether you self-host n8n through Docker or npm, or run it on n8n Cloud, the hosted offer from n8n. There is a catch though, because Camino AI is a community node rather than a node shipped with n8n: it lives in the npm package n8n-nodes-camino, version 0.1.1, and you install it yourself from Settings, then Community nodes, on a self-hosted instance. n8n Cloud only accepts verified community nodes. What Camino AI itself costs to use is a separate question that this page does not cover.
02What credentials do you need to connect Camino AI?
One Camino AI credential, created once in the Credentials menu of n8n. After that, every workflow on the instance can reuse it, and the Camino AI node offers it in its dropdown list when you add the node to a canvas. Before any of that, the community package has to be installed, since the node is not part of the default n8n catalog. The same credential also works with the HTTP Request node through predefined authentication, which matters when you need an endpoint the node does not cover.
03What are the limits of the Camino AI node in n8n?
Three worth knowing. First, the node exposes 6 operations across 4 resources, so anything outside search, point of interest queries, spatial relationship, place context, journey planning and routes is not there. For those, call the API with the HTTP Request node and reuse the same credential. Second, there is no Camino AI trigger node, so nothing in Camino AI can start a workflow by itself. Third, result volume is capped by the fields the operations expose, Limit on search and point of interest queries, plus Offset to page through results.
04Does Camino AI react in real time in n8n?
No, and it cannot, because Camino AI has no trigger node in n8n. A workflow that uses it always starts somewhere else. The three usual options are a Schedule Trigger running at a fixed interval, an n8n Webhook, which is a URL n8n exposes so a third party service can call it, or the trigger of another tool already in your stack. From there, the Camino AI node runs as a step like any other, reading its input with expressions such as {{ $json.lat }}. So the freshness of your data depends on the trigger you chose, not on Camino AI.
05n8n or Make for Camino AI?
It depends on hosting and on how you want to pay. Make is a hosted automation platform with no self-hosting option, billed per operation, which is predictable when volume is low and less so when a journey planning workflow loops over many stops. n8n can be self-hosted through Docker or npm, or used on n8n Cloud, and the workflow is the same either way, which matters when location data has to stay on infrastructure you control. One point against n8n here: Camino AI is a community node, so the install step exists only on the n8n side, and only on a self-hosted instance.
Same platform

Other docs you might need on this stack.

Browse all integrations