Weather Proxy Webhook Workflow: WeatherAPI & Open-Meteo

Get Simplified Weather Data via a Single Webhook (WeatherAPI or Open-Meteo)

This n8n workflow exposes a webhook-based weather proxy API that accepts latitude/longitude and a start date, fetches forecast or historical daily weather from WeatherAPI or Open-Meteo Archive, and returns a compact JSON response with key temperature and condition fields.

What this workflow does

• Receives webhook requests on the /weather-proxy endpoint with query parameters such as lat, lon, and start_date (or falls back to default Tokyo coordinates).
• Selects the provider automatically: it compares start_date to today—using WeatherAPI for dates within the next 14 days, and Open-Meteo Archive for older dates.
• Fetches daily weather data over HTTP from the chosen provider.
• Normalizes the response into a compact JSON payload, including:
  • max/min temperature
  • a derived condition (e.g., hot/cold/rain/snow)
  • rain chance / rain percentage
• Returns the formatted JSON response to the webhook caller with appropriate CORS and JSON content-type headers.

Use cases

• Build a lightweight weather endpoint for your app or SaaS dashboard without managing multiple weather APIs.
• Backfill historical weather views (older start_date values) using Open-Meteo Archive with the same webhook interface.
• Power automation scenarios like daily summaries, scheduling logic, or user-facing weather insights based on simplified temperature/condition outputs.

Technical details

• n8n nodes: Webhook, Code, HTTP Request, Respond to Webhook
• Configuration: replace the hardcoded WeatherAPI API key in the parameter-building code with your own key.
• Integration: your client calls the production webhook URL for /weather-proxy and passes lat, lon, and start_date.