Daily Weather Forecast
Daily at 7:50 AM, fetches a five-day forecast from OpenWeatherMap and sends a formatted Telegram message with hourly predictions.
What it does
Get a personalized five-day weather forecast delivered to your Telegram every morning at 7:50 AM. You receive formatted messages with hourly predictions and smart recommendations tailored to help you plan your day.
Step by step
- Configure the schedule trigger to fire at 7:50 AM using cron syntax or native scheduling options.
- Set up an HTTP request node with a GET method targeting the OpenWeatherMap One Call API endpoint.
- Pass the user's latitude and longitude as query parameters in the API request URL.
Where the LLM does the work
- Generate context-aware emojis that match the specific weather conditions described in the raw JSON data.
- Draft natural language recommendations for clothing or activities based on temperature and precipitation forecasts.
- Format the hourly predictions into a concise, readable HTML snippet suitable for Telegram's HTML parse mode.
Watch out for
API rate limits can block the run so you must implement error handling with exponential backoff.
Telegram message length restrictions may truncate long forecasts so you should split messages or limit character counts.
Invalid API keys will cause silent failures so verify credentials in a test environment before deploying.
Timezone mismatches can confuse users so ensure all timestamps are converted to the recipient's local time.
Tools that fit
Code LLM Processing and formatting data
The agent brief
Everything your agent needs, including the gotchas. Copy it and go.
You are helping me build the following AI agent workflow. ## Goal Daily Weather Forecast: Daily at 7:50 AM, fetches a five-day forecast from OpenWeatherMap and sends a formatted Telegram message with hourly predictions. ## Specification - What it does: Get a personalized five-day weather forecast delivered to your Telegram every morning at 7:50 AM. You receive formatted messages with hourly predictions and smart recommendations tailored to help you plan your day. - Trigger: On a schedule (Scheduled · daily 7:50 AM) - Autonomy: Fully hands-off - Expected setup effort: about an afternoon - Tools/services involved: - OpenWeatherMap: Fetching weather data - Telegram: Sending formatted messages - Code: Processing and formatting data ## Known pitfalls, handle each one explicitly in your implementation 1. API rate limits can block the run so you must implement error handling with exponential backoff. 2. Telegram message length restrictions may truncate long forecasts so you should split messages or limit character counts. 3. Invalid API keys will cause silent failures so verify credentials in a test environment before deploying. 4. Timezone mismatches can confuse users so ensure all timestamps are converted to the recipient's local time. ## Reference implementation https://n8n.io/workflows/4608 (workflow template) Fetch and inspect this before building. If it matches my stack, adapt it; if not, rebuild the pattern with my tools. ## Process requirements 1. Before building: ask me which of the listed tools I actually use and what my platform is (n8n / Make / code / other). Do not assume. 2. Adapt the pattern to my answers; do not force the reference stack. 3. Address every pitfall above; tell me how you handled each. 4. Provide a test plan I can run before letting this touch real data. 5. Ask before any step that sends messages, modifies data, or spends money. Source: https://usecasesforagents.com/use-case/daily-weather-forecast-bot/ via usecasesforagents.com
Frequently asked questions
Can I use a different Niche API than OpenWeatherMap?
Yes. OpenWeatherMap is only the example niche api in this recipe. The same flow works with Bitly, Google Maps Distance Matrix API, Open-Meteo API and Philips IntelliVue Devices. Swap the niche api connection and keep the rest of the setup as written.
Want this running in your business?
This is what I do. I design and build AI agents like this one, and keep them running. If you want it set up for your team instead of doing it yourself, get in touch.
Who it's for
Built for anyone who wants this off their own plate, no team or company required.