HumationHuman + Automation
Back to Catalog

Daily weather reports with OpenWeatherMap and Telegram Bot

Dariusz KorytoDariusz Koryto
1171 views
2/3/2026
HTTPWebhookDebuggerDevelopmentTesting
Official Page

Get automated weather updates delivered directly to your Telegram chat at scheduled intervals. This workflow fetches current weather data from OpenWeatherMap and sends formatted weather reports via a Telegram bot.

Use Cases

  • Daily morning weather briefings
  • Regular weather monitoring for outdoor activities
  • Automated weather alerts for specific locations
  • Personal weather assistant for travel planning

Prerequisites

Before setting up this workflow, ensure you have:

  • An OpenWeatherMap API account (free tier available)
  • A Telegram bot token
  • Your Telegram chat ID
  • n8n instance (cloud or self-hosted)

Setup Instructions

Step 1: Create OpenWeatherMap Account

  1. Go to OpenWeatherMap and sign up for a free account
  2. Navigate to the API keys section in your account
  3. Copy your API key (you'll need this for the workflow configuration)

Step 2: Create Telegram Bot

  1. Open Telegram and search for @BotFather
  2. Start a chat and use the /newbot command
  3. Follow the prompts to create your bot and get the bot token
  4. Save the bot token securely

Step 3: Get Your Telegram Chat ID

  1. Start a conversation with your newly created bot
  2. Send any message to the bot
  3. Visit https://api.telegram.org/bot<YourBOTToken>/getUpdates in your browser
  4. Look for your chat ID in the response (it will be a number like 123456789)

Step 4: Configure the Workflow

  1. Import this workflow into your n8n instance
  2. Configure each node with your credentials:

Schedule Trigger Node

  • Set your preferred schedule (default: daily at 8:00 AM)
  • Use cron expression format (e.g., 0 8 * * * for 8 AM daily)

Get Weather Node

  • Add your OpenWeatherMap credentials
  • Update the cityName parameter to your desired location
  • Format: "CityName,CountryCode" (e.g., "London,UK")

Send a text message Node

  • Add your Telegram bot credentials (bot token)
  • Replace XXXXXXX in the chatId field with your actual chat ID

Customization Options

Location Settings

In the "Get Weather" node, modify the cityName parameter to change the location. You can specify:

  • City name only: "Paris"
  • City with country: "Paris,FR"
  • City with state and country: "Miami,FL,US"

Schedule Frequency

In the "Schedule Trigger" node, adjust the cron expression:

  • Every 6 hours: 0 */6 * * *
  • Twice daily (8 AM & 6 PM): 0 8,18 * * *
  • Weekly on Mondays at 9 AM: 0 9 * * 1

Message Format

In the "Format Weather" node, you can customize the message template by modifying the message variable in the function code. Current format includes:

  • Current temperature with "feels like" temperature
  • Min/max temperatures for the day
  • Weather description and precipitation
  • Wind speed and direction
  • Cloud coverage percentage
  • Sunrise and sunset times

Language Support

In the "Get Weather" node, change the language parameter to get weather descriptions in different languages:

  • English: "en"
  • Spanish: "es"
  • French: "fr"
  • German: "de"
  • Polish: "pl"

Troubleshooting

Common Issues

Weather data not updating:

  • Verify your OpenWeatherMap API key is valid and active
  • Check if you've exceeded your API rate limits
  • Ensure the city name format is correct

Messages not being sent:

  • Confirm your Telegram bot token is correct
  • Verify the chat ID is accurate (should be a number, not username)
  • Make sure you've started a conversation with your bot

Workflow not triggering:

  • Check if the workflow is activated (toggle switch should be ON)
  • Verify the cron expression syntax is correct
  • Ensure your n8n instance is running continuously

Testing the Workflow

  1. Use the "Test workflow" button to run manually
  2. Check each node's output for errors
  3. Verify the final message format in Telegram

Node Descriptions

Schedule Trigger

Automatically starts the workflow based on a cron schedule. Runs at specified intervals to fetch fresh weather data.

Get Weather

Connects to OpenWeatherMap API to retrieve current weather conditions for the specified location.

Format Weather

Processes the raw weather data and creates a user-friendly message with emojis and organized information.

Send a text message

Delivers the formatted weather report to your Telegram chat using the configured bot.

Additional Features

You can extend this workflow by:

  • Adding weather alerts for specific conditions (temperature thresholds, rain warnings)
  • Including weather forecasts for multiple days
  • Sending reports to multiple chat recipients
  • Adding location-based emoji selection
  • Integrating with other notification channels (email, Slack, Discord)

Security Notes

  • Keep your API keys and bot tokens secure
  • Don't share your chat ID publicly
  • Consider using n8n's credential system for storing sensitive information
  • Regularly rotate your API keys for better security

Special thanks to Arkadiusz, the only person who supports me in n8n mission to make automation great again.

Daily Weather Reports with OpenWeatherMap and Telegram Bot

This n8n workflow automates the process of fetching daily weather information for a specified location and sending it as a message to a Telegram chat. It simplifies staying updated on weather conditions without manually checking different apps or websites.

What it does

  1. Triggers Daily: The workflow is scheduled to run periodically (e.g., daily at a specific time).
  2. Sets Location: A Function node defines the latitude and longitude for which the weather report will be fetched.
  3. Fetches Weather Data: It uses the OpenWeatherMap API to retrieve current weather conditions and forecast for the defined location.
  4. Sends Telegram Message: The retrieved weather data is then formatted and sent as a message to a designated Telegram chat.

Prerequisites/Requirements

  • n8n Instance: A running n8n instance.
  • OpenWeatherMap Account & API Key: You will need an API key from OpenWeatherMap to access their weather data.
  • Telegram Bot & Chat ID: A Telegram bot token and the chat ID where you want to receive the weather reports. You can create a new bot via BotFather on Telegram.

Setup/Usage

  1. Import the Workflow:

    • Download the provided JSON file.
    • In your n8n instance, go to "Workflows" and click "New".
    • Click the three-dot menu (...) in the top right and select "Import from JSON".
    • Paste the JSON content or upload the file.

  2. Configure Credentials:

    • OpenWeatherMap:
      • Click on the "OpenWeatherMap" node.
      • Under "Credentials", click "Create New".
      • Enter your OpenWeatherMap API Key.
      • Give the credential a name (e.g., "My OpenWeatherMap API Key") and save.
    • Telegram:
      • Click on the "Telegram" node.
      • Under "Credentials", click "Create New".
      • Enter your Telegram Bot Token.
      • Give the credential a name (e.g., "My Telegram Bot") and save.

  3. Customize Location:

    • Click on the "Function" node (named "Function").
    • Modify the latitude and longitude variables in the JavaScript code to your desired location.

  4. Configure Telegram Chat ID:

    • Click on the "Telegram" node.
    • In the "Chat ID" field, enter the ID of the Telegram chat where you want the messages to be sent. You can get your chat ID by forwarding a message from the target chat to a bot like @userinfobot.

  5. Set Schedule:

    • Click on the "Cron" node.
    • Configure the desired schedule for the weather reports (e.g., daily at 8:00 AM).

  6. Activate the Workflow:

    • Once all configurations are complete, click the "Activate" toggle in the top right corner of the workflow editor to enable it.

Related Templates

Automate Dutch Public Procurement Data Collection with TenderNed

TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch 🔗 LinkedIn – Wessel Bulte

Wessel BulteBy Wessel Bulte
247

🎓 How to transform unstructured email data into structured format with AI agent

This workflow automates the process of extracting structured, usable information from unstructured email messages across multiple platforms. It connects directly to Gmail, Outlook, and IMAP accounts, retrieves incoming emails, and sends their content to an AI-powered parsing agent built on OpenAI GPT models. The AI agent analyzes each email, identifies relevant details, and returns a clean JSON structure containing key fields: From – sender’s email address To – recipient’s email address Subject – email subject line Summary – short AI-generated summary of the email body The extracted information is then automatically inserted into an n8n Data Table, creating a structured database of email metadata and summaries ready for indexing, reporting, or integration with other tools. --- Key Benefits ✅ Full Automation: Eliminates manual reading and data entry from incoming emails. ✅ Multi-Source Integration: Handles data from different email providers seamlessly. ✅ AI-Driven Accuracy: Uses advanced language models to interpret complex or unformatted content. ✅ Structured Storage: Creates a standardized, query-ready dataset from previously unstructured text. ✅ Time Efficiency: Processes emails in real time, improving productivity and response speed. *✅ Scalability: Easily extendable to handle additional sources or extract more data fields. --- How it works This workflow automates the transformation of unstructured email data into a structured, queryable format. It operates through a series of connected steps: Email Triggering: The workflow is initiated by one of three different email triggers (Gmail, Microsoft Outlook, or a generic IMAP account), which constantly monitor for new incoming emails. AI-Powered Parsing & Structuring: When a new email is detected, its raw, unstructured content is passed to a central "Parsing Agent." This agent uses a specified OpenAI language model to intelligently analyze the email text. Data Extraction & Standardization: Following a predefined system prompt, the AI agent extracts key information from the email, such as the sender, recipient, subject, and a generated summary. It then forces the output into a strict JSON structure using a "Structured Output Parser" node, ensuring data consistency. Data Storage: Finally, the clean, structured data (the from, to, subject, and summarize fields) is inserted as a new row into a specified n8n Data Table, creating a searchable and reportable database of email information. --- Set up steps To implement this workflow, follow these configuration steps: Prepare the Data Table: Create a new Data Table within n8n. Define the columns with the following names and string type: From, To, Subject, and Summary. Configure Email Credentials: Set up the credential connections for the email services you wish to use (Gmail OAuth2, Microsoft Outlook OAuth2, and/or IMAP). Ensure the accounts have the necessary permissions to read emails. Configure AI Model Credentials: Set up the OpenAI API credential with a valid API key. The workflow is configured to use the model, but this can be changed in the respective nodes if needed. Connect the Nodes: The workflow canvas is already correctly wired. Visually confirm that the email triggers are connected to the "Parsing Agent," which is connected to the "Insert row" (Data Table) node. Also, ensure the "OpenAI Chat Model" and "Structured Output Parser" are connected to the "Parsing Agent" as its AI model and output parser, respectively. Activate the Workflow: Save the workflow and toggle the "Active" switch to ON. The triggers will begin polling for new emails according to their schedule (e.g., every minute), and the automation will start processing incoming messages. --- Need help customizing? Contact me for consulting and support or add me on Linkedin.

DavideBy Davide
1616

Tax deadline management & compliance alerts with GPT-4, Google Sheets & Slack

AI-Driven Tax Compliance & Deadline Management System Description Automate tax deadline monitoring with AI-powered insights. This workflow checks your tax calendar daily at 8 AM, uses GPT-4 to analyze upcoming deadlines across multiple jurisdictions, detects overdue and critical items, and sends intelligent alerts via email and Slack only when immediate action is required. Perfect for finance teams and accounting firms who need proactive compliance management without manual tracking. 🏛️🤖📊 Good to Know AI-Powered: GPT-4 provides risk assessment and strategic recommendations Multi-Jurisdiction: Handles Federal, State, and Local tax requirements automatically Smart Alerts: Only notifies executives when deadlines are overdue or critical (≤3 days) Priority Classification: Categorizes deadlines as Overdue, Critical, High, or Medium priority Dual Notifications: Critical alerts to leadership + daily summaries to team channel Complete Audit Trail: Logs all checks and deadlines to Google Sheets for compliance records How It Works Daily Trigger - Runs at 8:00 AM every morning Fetch Data - Pulls tax calendar and company configuration from Google Sheets Analyze Deadlines - Calculates days remaining, filters by jurisdiction/entity type, categorizes by priority AI Analysis - GPT-4 provides strategic insights and risk assessment on upcoming deadlines Smart Routing - Only sends alerts if overdue or critical deadlines exist Critical Alerts - HTML email to executives + Slack alert for urgent items Team Updates - Slack summary to finance channel with all upcoming deadlines Logging - Records compliance check results to Google Sheets for audit trail Requirements Google Sheets Structure Sheet 1: TaxCalendar DeadlineID | DeadlineName | DeadlineDate | Jurisdiction | Category | AssignedTo | IsActive FED-Q1 | Form 1120 Q1 | 2025-04-15 | Federal | Income | John Doe | TRUE Sheet 2: CompanyConfig (single row) Jurisdictions | EntityType | FiscalYearEnd Federal, California | Corporation | 12-31 Sheet 3: ComplianceLog (auto-populated) Date | AlertLevel | TotalUpcoming | CriticalCount | OverdueCount 2025-01-15 | HIGH | 12 | 3 | 1 Credentials Needed Google Sheets - Service Account OAuth2 OpenAI - API Key (GPT-4 access required) SMTP - Email account for sending alerts Slack - Bot Token with chat:write permission Setup Steps Import workflow JSON into n8n Add all 4 credentials Replace these placeholders: YOURTAXCALENDAR_ID - Tax calendar sheet ID YOURCONFIGID - Company config sheet ID YOURLOGID - Compliance log sheet ID C12345678 - Slack channel ID tax@company.com - Sender email cfo@company.com - Recipient email Share all sheets with Google service account email Invite Slack bot to channels Test workflow manually Activate the trigger Customizing This Workflow Change Alert Thresholds: Edit "Analyze Deadlines" node: Critical: Change <= 3 to <= 5 for 5-day warning High: Change <= 7 to <= 14 for 2-week notice Medium: Change <= 30 to <= 60 for 2-month lookout Adjust Schedule: Edit "Daily Tax Check" trigger: Change hour/minute for different run time Add multiple trigger times for tax season (8 AM, 2 PM, 6 PM) Add More Recipients: Edit "Send Email" node: To: cfo@company.com, director@company.com CC: accounting@company.com BCC: archive@company.com Customize Email Design: Edit "Format Email" node to change colors, add logo, or modify layout Add SMS Alerts: Insert Twilio node after "Is Critical" for emergency notifications Integrate Task Management: Add HTTP Request node to create tasks in Asana/Jira for critical deadlines Troubleshooting | Issue | Solution | |-------|----------| | No deadlines found | Check date format (YYYY-MM-DD) and IsActive = TRUE | | AI analysis failed | Verify OpenAI API key and account credits | | Email not sending | Test SMTP credentials and check if critical condition met | | Slack not posting | Invite bot to channel and verify channel ID format | | Permission denied | Share Google Sheets with service account email | 📞 Professional Services Need help with implementation or customization? Our team offers: 🎯 Custom workflow development 🏢 Enterprise deployment support 🎓 Team training sessions 🔧 Ongoing maintenance 📊 Custom reporting & dashboards 🔗 Additional API integrations Discover more workflows – Get in touch with us

Oneclick AI SquadBy Oneclick AI Squad
93