- Integrations
- /
- OpenWeatherMap
OpenWeatherMap
OpenWeatherMap weather and forecasts
OpenWeatherMap is the long-running weather-data API — current weather, forecasts, historical data, plus various specialised endpoints (UV index, air quality, geocoding). Tiny Command exposes two actions, no triggers: Get Current Weather (current conditions for a location specified by city name or lat/lon), Get 5-Day Forecast (3-hourly forecast for the next 5 days). The connection uses an OpenWeather API key (free tier requires registration). For workflows that need weather context — "schedule the outdoor event reminder only if it's not raining", "send a weather-appropriate product suggestion", "alert when severe weather is forecast for a warehouse location" — OpenWeather is the default cheap-and-reliable source. The free tier (1000 calls/day) is plenty for most personal/SMB use cases.
Do anything OpenWeatherMap can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| OpenWeather 5-Day Forecast | Returns 3-hourly forecast for the next 5 days (40 entries). For "this weekend's weather → suitable for outdoor event?" planning workflows. |
| OpenWeather Current Weather | Returns current conditions for a city or lat/lon — temperature, humidity, wind, conditions, sunrise/sunset. For "morning weather digest" personal-automation or "weather-appropriate product recommendation" e-commerce workflows. |
Pre-built OpenWeatherMap workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
AI-triage every OpenWeatherMap event, ping the right channel only when it matters.
Every event matching a filter, appended to a running spreadsheet.
Turn OpenWeatherMap into a Notion-backed source of truth, auto-tagged.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect OpenWeatherMap once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every OpenWeatherMap field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the OpenWeatherMap integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect OpenWeatherMap to Tiny Command?
What OpenWeatherMap triggers does Tiny Command support?
What OpenWeatherMap actions can I run from a workflow?
Is the OpenWeatherMap integration real-time?
Do I need to write code to use OpenWeatherMap with Tiny Command?
How much does the OpenWeatherMap integration cost?
More other apps people connect.
Same category as OpenWeatherMap, ordered by how often teams pair them. Hover the carousel to pause.
Do more with OpenWeatherMap.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.