Skip to content

n8n: use Openapi geocoding inside a workflow with address enrichment #31

@francescobianco

Description

@francescobianco

Scenario

I'm building an n8n workflow that reads a Google Sheet of addresses, geocodes them via Openapi, and writes lat/lon back to the sheet. The HTTP Request node works but is brittle — I have to hardcode the token and handle auth manually.

Current n8n HTTP Request setup

{
  "url": "https://geocoding.openapi.com/geocode",
  "method": "GET",
  "headers": { "Authorization": "Bearer {{token}}" },
  "qs": { "address": "{{address}}" }
}

Problems:

  • Token expires and the workflow silently fails
  • No retry on 429
  • Hard to test without live credentials

What I'd like

Either:

  1. A pre-built n8n community node that handles auth transparently
  2. A lightweight PHP webhook (deployable as a single file) that wraps the SDK and exposes a simple REST API for n8n to call

Open questions

  • Is a single-file PHP proxy script in examples/ something the maintainers would accept?
  • Does anyone have a working n8n workflow template they'd share?
  • How are others handling token refresh inside long-running n8n workflows?

Metadata

Metadata

Assignees

No one assigned

    Labels

    help wantedExtra attention is neededquestionFurther information is requested

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions