How to Use OpenStreetMap element details in n8n
Returns one map object's tags and geographic structure, with referenced geometry available for ways and relations. Use it to inspect a known road, building, or boundary in detail.
Prompts to try with OpenStreetMap element details in n8n
Copy an example into n8n, or ask in your own words.
Every Monday at 9am: use OpenStreetMap element details to look this up and give me the result as a table.
Pull the latest numbers from OpenStreetMap element details and tell me what changed since last week.
Check OpenStreetMap element details and summarize what you find in three bullet points.
Pull the newest data from OpenStreetMap element details and give me the result as a table.
Check OpenStreetMap element details every morning and tell me only when something changed.
How to set up OpenStreetMap element details in n8n
Pick the way that suits you. Each takes about two minutes.
Use the Spiral skill
- Send n8n this message
Your agent reads Spiral's skill and sets itself up.
set up https://spiral.ai/SKILL.md
- Sign in or paste a key
Approve Spiral in the browser, or give the agent a key from the console.
Use Spiral's MCP server
- Create a key
Create a key under API keys in the console.
- Add an MCP Client node
In a workflow, add an MCP Client node (or, under an AI Agent node, an MCP Client Tool) and set:
https://api.spiral.ai/mcp
- Pick a tool
The node lists Spiral's tools. In an MCP Client node pick one, such as run, and give it its arguments:
{ "provider": "fal", "model": "fal-ai/flux/schnell", "input": { "prompt": "a lighthouse at dawn" }, "wait": true } - Run OpenStreetMap element details in a workflow step
Give the step an instruction like the ones below and run it on your trigger or schedule. Spiral finds OpenStreetMap element details, prices it and runs it each time the step fires.
Use the Spiral CLI
- Install and sign in
Installs the Spiral CLI, signs you in and adds its skill to your coding agents.
npx -y spiral-cli@latest init
Call the Spiral API
- Create an API key
In the console, under API keys.
- Run OpenStreetMap element details
One request; the result comes back by polling or a webhook.
curl https://api.spiral.ai/v1/runs \ -H "Authorization: Bearer $SPIRAL_API_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: $(uuidgen)" \ -d '{ "provider": "alexandria", "model": "openstreetmap-org/places/get_element", "input": { "id": 1, "type": "node" } }'
Then paste one of the prompts above: n8n finds OpenStreetMap element details on Spiral, shows the price and runs it.
OpenStreetMap element details providers and prices
Spiral runs OpenStreetMap element details through Alexandria. Open a card for today's price, with every fee included.
Settings you can ask for
Ask n8n for any of these in your prompt.
| Setting | Allowed values | Default | Description |
|---|---|---|---|
| ID | a number from 1 | Numeric OSM element id. | |
| Type | node, way, or relation | OSM element type. | |
| Full | on or off | Also return the nodes of a way, or the nodes and ways of a relation. Not allowed for nodes. |
Every API field of OpenStreetMap · Get element is on its tool page: open its card above.
What can you do with OpenStreetMap element details in n8n?
Maintain a recurring map-quality brief for a public district. Compare each OpenStreetMap retrieval with the previous run and surface changes in the records or evidence returned.
Build a neighborhood base map
Locate Covent Garden, inspect a small surrounding block, label public landmarks from coordinates, and refresh the saved map objects.
Maintain a public amenity directory
Find mapped libraries or drinking fountains in a named district, inspect their tags, and refresh known records for a civic directory.
Investigate an unexpected map change
Compare a changed public feature with its earlier versions, surrounding map data, nearby edit sessions, and reported map problems.
Review accessibility mapping
Inspect available accessibility tags on public amenities, compare saved records, trace relevant edits, and collect map reports for human review.
Check an administrative boundary
Locate a municipality, inspect its mapped boundary and nearby features, then review object history and edit sessions when the boundary changes.
Investigate a station map discrepancy
Compare saved station-area records with current objects, inspect the surrounding block, and use history, edit sessions, and issue reports to explain discrepancies.
More on OpenStreetMap element details and n8n
Overview
OpenStreetMap element details in other agents
Questions about OpenStreetMap element details in n8n
Can n8n use OpenStreetMap element details?
Yes. Add Spiral to n8n as an MCP server, and n8n can find and run OpenStreetMap element details like any built-in tool.
How much does OpenStreetMap element details cost in n8n?
$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your n8n plan is separate.
Do I need an Alexandria account to use OpenStreetMap element details in n8n?
You need no Alexandria account. n8n uses one Spiral API key for every tool, and Spiral runs OpenStreetMap element details on its own Alexandria account.
How long does it take to set up OpenStreetMap element details in n8n?
About two minutes: create a key, then add an MCP Client node, then pick a tool.
Does n8n wait while OpenStreetMap element details runs?
OpenStreetMap element details runs in the background. n8n starts the run, checks on it and gives you the json when it's ready.
Which parts of the world does OpenStreetMap cover?
OpenStreetMap has worldwide scope, including roads, trails, cafés, and railway stations. Its records come from a community of contributors.
Does worldwide coverage mean every local feature is mapped?
No. OpenStreetMap's accuracy documentation says basic map coverage is still being built in many areas, so a local result set cannot establish that every feature is present.
How frequently are OpenStreetMap changes distributed?
OpenStreetMap publishes minute, hourly, and daily change files. Those replication intervals do not establish one refresh schedule for every service that uses the data.
Are these map images or underlying geographic records?
OpenStreetMap's editing API exposes raw geographic data. Nodes, ways, and relations describe the underlying features rather than a rendered map image.
Is an OpenStreetMap number enough to identify a feature?
No. Nodes, ways, and relations have separate ID spaces, so retain the object type alongside the number.
Start using OpenStreetMap element details in n8n
One Spiral account for every tool your agent needs. No subscription; you pay per run.
Paste this into n8n:
set up https://spiral.ai/SKILL.md


