Automated Indonesian weather alerts with BMKG data & Telegram notifications
π€οΈ Automated Indonesian Weather Monitoring with Smart Notifications
Stay ahead of weather changes with this comprehensive monitoring system that fetches real-time data from Indonesia's official meteorological agency (BMKG) and delivers beautiful, actionable weather reports directly to your Telegram.
β‘ What This Workflow Does
This intelligent weather monitoring system automatically:
- Fetches Official Data: Connects to BMKG's public weather API for accurate Indonesian forecasts
- Smart Processing: Analyzes temperature, humidity, precipitation, and wind conditions
- Risk Assessment: Generates contextual warnings for extreme weather conditions
- Automated Alerts: Sends formatted weather reports to Telegram every 6 hours
- Error Handling: Includes robust error detection and notification system
π― Perfect For
- Local Communities: Keep neighborhoods informed about weather changes
- Business Operations: Plan outdoor activities and logistics based on weather
- Emergency Preparedness: Receive early warnings for extreme weather conditions
- Personal Planning: Never get caught unprepared by sudden weather changes
- Agricultural Monitoring: Track conditions affecting farming and outdoor work
π οΈ Key Features
- π Automated Scheduling: Runs every 6 hours with manual trigger option
- π Comprehensive Reports: Current conditions + 6-hour detailed forecasts
- β οΈ Smart Warnings: Contextual alerts for temperature extremes and rain probability
- π¨ Beautiful Formatting: Rich Telegram messages with emojis and structured data
- π§ Error Recovery: Automatic error handling with notification system
- π Location-Aware: Supports any Indonesian location via BMKG regional codes
π What You'll Get
Each weather report includes:
- Current temperature, humidity, and weather conditions
- 6-hour detailed forecast with timestamps
- Wind speed and direction information
- Rain probability and visibility data
- Personalized warnings and recommendations
- Average daily statistics and trends
π Setup Requirements
- Telegram Bot Token: Create a bot via @BotFather
- Chat ID: Your personal or group chat identifier
- BMKG Location Code: Regional administrative code for your area
π‘ Pro Tips
- Customize the location by changing the
adm4parameter in the HTTP request - Adjust scheduling interval based on your monitoring needs
- Modify warning thresholds in the processing code
- Add multiple chat IDs for broader distribution
- Integrate with other n8n workflows for advanced automation
π Why Choose This Template
- Production Ready: Includes comprehensive error handling and logging
- Highly Customizable: Easy to modify for different locations and preferences
- Official Data Source: Uses Indonesia's trusted meteorological service
- User-Friendly Output: Clean, readable reports perfect for daily use
- Scalable Design: Easily extend for multiple locations or notification channels
Transform your weather awareness with this professional-grade monitoring system that brings Indonesia's official weather data right to your fingertips!
Keywords: weather monitoring, BMKG API, Telegram notifications, Indonesian weather, automated alerts, meteorological data, weather forecasting, n8n automation, weather API integration
Automated Indonesian Weather Alerts with BMKG Data & Telegram Notifications
This n8n workflow automates the process of fetching weather data from the Indonesian Agency for Meteorology, Climatology, and Geophysics (BMKG) and sending alerts via Telegram if specific weather conditions are met.
What it does
This workflow simplifies monitoring weather conditions in Indonesia and provides timely notifications, making it useful for individuals or businesses that need to stay informed about local weather changes.
- Triggers on a Schedule: The workflow is set to run at regular intervals (e.g., every hour, daily).
- Fetches Weather Data: It makes an HTTP request to the BMKG API to retrieve the latest weather forecast data for a specified region.
- Processes Data: A Code node processes the raw JSON response from BMKG, extracting relevant weather information.
- Checks for Conditions: An If node evaluates the extracted weather data against predefined conditions (e.g., specific weather types, temperatures).
- Sends Telegram Alert: If the conditions are met, a message is formatted and sent to a specified Telegram chat.
Prerequisites/Requirements
- n8n Instance: A running n8n instance.
- Telegram Bot Token: A Telegram Bot token to send messages. You can create one by talking to BotFather on Telegram.
- Telegram Chat ID: The chat ID where the notifications should be sent. This can be a personal chat, a group, or a channel.
- BMKG API Endpoint: The specific BMKG API endpoint for the region you wish to monitor. (This will need to be configured in the HTTP Request node).
Setup/Usage
- Import the Workflow:
- Save the provided JSON content as a
.jsonfile. - In your n8n instance, click "New" in the workflows list, then "Import from JSON" and upload the file.
- Save the provided JSON content as a
- Configure Credentials:
- Telegram:
- Locate the "Telegram" node.
- Click on the "Credential" field and select "Create New".
- Enter your Telegram Bot Token.
- Save the credential.
- Telegram:
- Configure Nodes:
- HTTP Request (Node ID 19):
- Update the URL to the specific BMKG API endpoint for your desired region.
- Adjust any headers or authentication if required by the BMKG API (though typically public weather APIs don't require complex auth).
- Code (Node ID 834):
- Review the JavaScript code to understand how it processes the BMKG data. You might need to adjust the parsing logic based on the exact structure of the BMKG API response you are using.
- Ensure the code extracts the specific weather conditions you want to check.
- If (Node ID 20):
- Define your desired weather conditions. For example, you might check if
weather_typecontains "Hujan" (Rain), or iftemperatureis below a certain value. - The conditions should reference the data output by the preceding Code node.
- Define your desired weather conditions. For example, you might check if
- Telegram (Node ID 49):
- Enter the
Chat IDwhere you want to receive the alerts. - Customize the
Textfield to create your alert message, using expressions to include dynamic weather data from previous nodes (e.g.,{{ $json.weather_description }}or{{ $json.temperature }}Β°C).
- Enter the
- HTTP Request (Node ID 19):
- Set the Schedule:
- Schedule Trigger (Node ID 839):
- Configure the desired interval for the workflow to run (e.g., every 1 hour, every day at 08:00 AM).
- (Optional) Manual Trigger (Node ID 838): Use this node to manually test the workflow immediately. You can disable the Schedule Trigger during testing.
- Schedule Trigger (Node ID 839):
- Activate the Workflow: Once configured, activate the workflow to start receiving automated weather alerts.
Related Templates
Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets
This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitorβs webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger β Manually start the workflow or schedule it to run periodically. Input Setup β Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) β Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring β Clean and convert GPT output into JSON format. Data Storage (Google Sheets) β Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the βSet Input Fieldsβ node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors β Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection β Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report β Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization β Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs β Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting Itβs a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.
Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax
Spark your creativity instantly in any chatβturn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. π What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing π§ Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation π Required Credentials OpenAI API Setup Go to platform.openai.com β API keys (sidebar) Click "Create new secret key" β Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai β Dashboard β API Keys Generate a new API key β Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) βοΈ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflowβchat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" π― Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration β οΈ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions
Automate invoice processing with OCR, GPT-4 & Salesforce opportunity creation
PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive β Download PDF β OCR text β AI normalize to JSON β Upsert Buyer (Account) β Create Opportunity β Map Products β Create OLI via Composite API β Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content β the parsed JSON (ensure itβs an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id β build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total β per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger β Download File From Google Download File From Google β Extract from File β Update File to One Drive Extract from File β Message a model Message a model β Create or update an account Create or update an account β Create an opportunity Create an opportunity β Build SOQL Build SOQL β Query PricebookEntries Query PricebookEntries β Code in JavaScript Code in JavaScript β Create Opportunity Line Items --- Quick setup checklist π Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. π IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) π§ AI Prompt: Use the strict system prompt; jsonOutput = true. π§Ύ Field mappings: Buyer tax id/name β Account upsert fields Invoice code/date/amount β Opportunity fields Product name must equal your Product2.ProductCode in SF. β Test: Drop a sample PDF β verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep βReturn only a JSON arrayβ as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields donβt support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your orgβs domain or use the Salesforce nodeβs Bulk Upsert for simplicity.