Monitor solar energy production & send alerts with Gmail, Google Sheets, and Slack
Solar Energy Production Monitoring Alert Workflow
This workflow automatically monitors solar energy production every 2 hours by fetching data from the Energidataservice API. If the energy output falls below a predefined threshold, it instantly notifies users via email. Otherwise, it logs the data into a Google Sheet and posts a daily summary to Slack.
Who’s It For
- Renewable energy teams monitoring solar output.
- Facility managers and power plant supervisors.
- ESG compliance officers tracking sustainability metrics.
- Developers or analysts automating solar energy reporting.
How It Works
- Trigger: The workflow starts every 2 hours using a Schedule Trigger.
- Data Fetch: An HTTP Request node fetches solar energy production data from the Energidataservice API.
- Processing: A Code node filters out entries with production below the minimum threshold.
- Decision Making: An If node checks whether any low-production entries are present.
- Alerts: If low-production is detected, an email is sent via the Gmail node.
- Logging: If all entries are valid, they are logged into a Google Sheet.
- Slack Summary: A Slack node posts the summary sheet data for end-of-day visibility.
How to Set Up
- Schedule Trigger: Configure to run every 2 hours.
- HTTP Request Node:
- Method:
GET - URL:
https://api.energidataservice.dk/dataset/YourDatasetHere - Add necessary headers and params as required by the API.
- Method:
- Code Node: Define logic to filter entries where
solar_energy_production < required_threshold. - If Node: Use
items.length > 0to check for low-production entries. - Gmail Node:
- Auth with Gmail credentials.
- Customize recipient and message template.
- Google Sheets Node:
- Connect to a spreadsheet.
- Map appropriate columns.
- Slack Node:
- Use Slack OAuth2 credentials.
- Specify channel and message content.
Requirements
- n8n Cloud or Self-hosted instance.
- Access to Energidataservice API.
- Gmail account (with n8n OAuth2 integration).
- Google Sheets account & sheet ID.
- Slack workspace and app with appropriate permissions.
How to Customize
- Change Frequency: Adjust the Schedule Trigger interval (e.g., every hour or 4x per day).
- Threshold Tuning: Modify the value in the Code node to change the minimum acceptable solar production.
- Alert Routing: Update Gmail recipients or replace Gmail with Microsoft Outlook/SendGrid.
- Sheet Format: Add or remove columns in the Google Sheet based on extra metrics (e.g., wind or nuclear data).
- Slack Posting: Customize Slack messages using Markdown for improved readability.
Add‑ons
- Telegram Node: Send alerts to a Telegram group instead of email.
- Discord Webhook: Push updates to a Discord channel.
- n8n Webhook Trigger: Extend it to receive external production update notifications.
- Integromat/Make or Zapier: For multi-platform integration with CRMs or ticketing tools.
Use Case Examples
- Utility Companies: Automatically detect and act on solar underperformance to maintain grid stability.
- Solar Farm Operators: Log clean production data for auditing and compliance reports.
- Sustainability Teams: Track daily performance and anomalies without manual checks.
- Home Solar System Owners: Get notified if solar generation drops below expected.
Common Troubleshooting
| Issue | Possible Cause | Solution | | -------------------------------------- | -------------------------------------- | ------------------------------------------------------------------- | | HTTP Request fails | API key missing or URL is incorrect | Check API endpoint, parameters, and authentication headers | | Gmail not sending alerts | Missing or invalid Gmail credentials | Re-authenticate Gmail OAuth2 in n8n credentials | | No data getting logged in Google Sheet | Incorrect mapping or sheet permissions | Ensure the sheet exists, columns match, and credentials are correct | | Slack node fails | Invalid token or missing channel ID | Reconnect Slack credentials and check permissions | | Code node returns empty | Filter logic may be too strict | Validate data format and relax the threshold condition |
Need Help?
Need help setting this up or customizing it for your own solar or energy monitoring use case?
✅ Set it up on your n8n Cloud or self-hosted instance ✅ Customize it for your own API or data source ✅ Modify alerts to suit your internal tools (Teams, Discord, SMS, etc.)
👉 Just reach out to our n8n automation team at WeblineIndia, we'll be happy to help.
Monitor Solar Energy Production and Send Alerts
This n8n workflow automates the process of monitoring solar energy production data, checking for anomalies, and sending alerts via Gmail and Slack if production falls below a specified threshold.
What it does
This workflow simplifies monitoring and alerting for solar energy production by:
- Scheduling Data Checks: It runs on a predefined schedule (e.g., daily, hourly) to fetch the latest solar energy production data.
- Fetching Solar Data: It makes an HTTP request to an external API to retrieve solar energy production metrics.
- Processing Data: It processes the fetched data, likely extracting the relevant production value.
- Checking Production Threshold: It compares the current solar energy production against a predefined minimum threshold.
- Sending Alerts (Conditional):
- If production falls below the threshold, it sends an alert email via Gmail.
- If production falls below the threshold, it also sends a notification to a specified Slack channel.
- Logging Data (Optional): It includes a Google Sheets node, which could be used to log all production data, regardless of whether an alert is triggered, for historical tracking. (Note: The current JSON does not show this node being connected to the main flow, but it's present for potential use).
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running instance of n8n.
- External Solar Energy API: Access to an API that provides solar energy production data. You will need the API endpoint and any necessary authentication.
- Gmail Account: A Gmail account configured as a credential in n8n to send email alerts.
- Slack Account: A Slack workspace and a Slack app/bot token configured as a credential in n8n to send channel notifications.
- Google Sheets Account (Optional): A Google Sheets account configured as a credential in n8n if you intend to log data to a spreadsheet.
Setup/Usage
- Import the Workflow:
- Copy the provided JSON code.
- In your n8n instance, go to "Workflows" and click "New".
- Click the three dots menu (...) in the top right and select "Import from JSON".
- Paste the JSON code and click "Import".
- Configure Credentials:
- Locate the "HTTP Request" node and configure it with the URL and any authentication details for your solar energy API.
- Locate the "Gmail" node and select or create a new Google OAuth2 credential for your Gmail account.
- Locate the "Slack" node and select or create a new Slack API credential for your Slack workspace.
- (Optional) If you plan to use the "Google Sheets" node, configure it with a Google OAuth2 credential and specify the spreadsheet ID and sheet name.
- Set Alert Threshold:
- Locate the "Code" node. This node is likely where the logic for checking the production threshold is implemented. You will need to modify the JavaScript code within this node to define your specific production threshold and the conditions for triggering an alert.
- Configure Schedule:
- Locate the "Schedule Trigger" node. Configure the desired interval (e.g., every day at a specific time, every hour) for the workflow to run.
- Activate the Workflow:
- Once all credentials and configurations are set, activate the workflow by toggling the "Active" switch in the top right corner of the workflow editor.
The workflow will now automatically fetch solar energy data on your defined schedule, check for low production, and send alerts if necessary.
Related Templates
AI multi-agent executive team for entrepreneurs with Gemini, Perplexity and WhatsApp
This workflow is an AI-powered multi-agent system built for startup founders and small business owners who want to automate decision-making, accountability, research, and communication, all through WhatsApp. The “virtual executive team,” is designed to help small teams to work smarter. This workflow sends you market analysis, market and sales tips, It can also monitor what your competitors are doing using perplexity (Research agent) and help you stay a head, or make better decisions. And when you feeling stuck with your start-up accountability director is creative enough to break the barrier 🎯 Core Features 🧑💼 1. President (Super Agent) Acts as the main controller that coordinates all sub-agents. Routes messages, assigns tasks, and ensures workflow synchronization between the AI Directors. 📊 2. Sales & Marketing Director Uses SerpAPI to search for market opportunities, leads, and trends. Suggests marketing campaigns, keywords, or outreach ideas. Can analyze current engagement metrics to adjust content strategy. 🕵️♀️ 3. Business Research Director Powered by Perplexity AI for competitive and market analysis. Monitors competitor moves, social media engagement, and product changes. Provides concise insights to help the founder adapt and stay ahead. ⏰ 4. Accountability Director Keeps the founder and executive team on track. Sends motivational nudges, task reminders, and progress reports. Promotes consistency and discipline — key traits for early-stage success. 🗓️ 5. Executive Secretary Handles scheduling, email drafting, and reminders. Connects with Google Calendar, Gmail, and Sheets through OAuth. Automates follow-ups, meeting summaries, and notifications directly via WhatsApp. 💬 WhatsApp as the Main Interface Interact naturally with your AI team through WhatsApp Business API. All responses, updates, and summaries are delivered to your chat. Ideal for founders who want to manage operations on the go. ⚙️ How It Works Trigger: The workflow starts from a WhatsApp Trigger node (via Meta Developer Account). Routing: The President agent analyzes the incoming message and determines which Director should handle it. Processing: Marketing or sales queries go to the Sales & Marketing Director. Research questions are handled by the Business Research Director. Accountability tasks are assigned to the Accountability Director. Scheduling or communication requests are managed by the Secretary. Collaboration: Each sub-agent returns results to the President, who summarizes and sends the reply back via WhatsApp. Memory: Context is maintained between sessions, ensuring personalized and coherent communication. 🧩 Integrations Required Gemini API – for general intelligence and task reasoning Supabase- for RAG and postgres persistent memory Perplexity API – for business and competitor analysis SerpAPI – for market research and opportunity scouting Google OAuth – to connect Sheets, Calendar, and Gmail WhatsApp Business API – for message triggers and responses 🚀 Benefits Acts like a team of tireless employees available 24/7. Saves time by automating research, reminders, and communication. Enhances accountability and strategy consistency for founders. Keeps operations centralized in a simple WhatsApp interface. 🧰 Setup Steps Create API credentials for: WhatsApp (via Meta Developer Account) Gemini, Perplexity, and SerpAPI Google OAuth (Sheets, Calendar, Gmail) Create a supabase account at supabase Add the credentials in the corresponding n8n nodes. Customize the system prompts for each Director based on your startup’s needs. Activate and start interacting with your virtual executive team on WhatsApp. Use Case You are a small organisation or start-up that can not afford hiring; marketing department, research department and secretar office, then this workflow is for you 💡 Need Customization? Want to tailor it for your startup or integrate with CRM tools like Notion or HubSpot? You can easily extend the workflow or contact the creator for personalized support. Consider adjusting the system prompt to suite your business
🎓 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.
Send WooCommerce discount coupons to customers via WhatsApp using Rapiwa API
Who is this for? This workflow is ideal for WooCommerce store owners who want to automatically send promotional WhatsApp messages to their customers when new coupons are created. It’s designed for marketers and eCommerce managers looking to boost engagement, streamline coupon sharing, and track campaign performance effortlessly through Google Sheets. Overview This workflow listens for WooCommerce coupon creation events (coupon.created) and uses customer billing data to send promotional WhatsApp messages via the Rapiwa API. The flow formats the coupon data, cleans phone numbers, verifies WhatsApp registration with Rapiwa, sends the promotional message when verified, and logs each attempt to Google Sheets (separate sheets for verified/sent and unverified/not sent). What this Workflow Does Listens for new coupon creation events in WooCommerce via the WooCommerce Trigger node Retrieves all customer data from the WooCommerce store Processes customers in batches to control throughput Cleans and formats customer phone numbers for WhatsApp Verifies if phone numbers are valid WhatsApp accounts using Rapiwa API Sends personalized WhatsApp messages with coupon details to verified numbers Logs all activities to Google Sheets for tracking and analysis Handles both verified and unverified numbers appropriately Key Features Automated coupon distribution: Triggers when new coupons are created in WooCommerce Customer data retrieval: Fetches all customer information from WooCommerce Phone number validation: Verifies WhatsApp numbers before sending messages Personalized messaging: Includes customer name and coupon details in messages Dual logging system: Tracks both successful and failed message attempts Rate limiting: Uses batching and wait nodes to prevent API overload Data formatting: Structures coupon information for consistent messaging Google Sheet Column Structure A Google Sheet formatted like this ➤ sample The workflow uses a Google Sheet with the following columns to track coupon distribution: | name | number | email | address1 | couponCode | couponTitle | couponType | couponAmount | createDate | expireDate | validity | status | | ----------- | ------------- | --------------------------------------------------- | --------- | ---------- | -------------- | ---------- | ------------ | ------------------- | ------------------- | ---------- | -------- | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur-DOHS | 62dhryst | eid offer 2025 | percent | 20.00 | 2025-09-11 06:08:02 | 2025-09-15 00:00:00 | unverified | not sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur-DOHS | 62dhryst | eid offer 2025 | percent | 20.00 | 2025-09-11 06:08:02 | 2025-09-15 00:00:00 | verified | sent | Requirements n8n instance with the following nodes: WooCommerce Trigger, Code, SplitInBatches, HTTP Request, IF, Google Sheets, Wait WooCommerce store with API access Rapiwa account with API access for WhatsApp verification and messaging Google account with Sheets access Customer phone numbers in WooCommerce (stored in billing.phone field) Important Notes Phone Number Format: The workflow cleans phone numbers by removing all non-digit characters. Ensure your WooCommerce phone numbers are in a compatible format. API Rate Limits: Rapiwa and WooCommerce APIs have rate limits. Adjust batch sizes and wait times accordingly. Data Privacy: Ensure compliance with data protection regulations when sending marketing messages. Error Handling: The workflow logs unverified numbers but doesn't have extensive error handling. Consider adding error notifications for failed API calls. Message Content: The current message template references the first coupon only (coupons[0]). Adjust if you need to handle multiple coupons. Useful Links Dashboard: https://app.rapiwa.com Official Website: https://rapiwa.com Documentation: https://docs.rapiwa.com Support & Help WhatsApp: Chat on WhatsApp Discord: SpaGreen Community Facebook Group: SpaGreen Support Website: https://spagreen.net Developer Portfolio: Codecanyon SpaGreen