by Oneclick AI Squad
This automated n8n workflow monitors API uptime by periodically checking API availability and sending instant WhatsApp alerts if any service goes down. It retrieves API details from a Google Sheet and includes retry logic for failed requests. Good to Know Checks API status every 15 minutes Integrates with Google Sheets for API list management Implements a retry mechanism with up to 4 attempts Sends WhatsApp alerts for downtime Supports customizable API request configurations How It Works Schedule Trigger** - Triggers every 15 minutes Read API List** - Fetches all API URLs from a Google Sheet Process Each API1** - Loops through each API entry Init Retry Counter** - Initializes retryCount = 0 Test API** - Sends the first request to the API Check Response** - Checks if a valid response was received If No Response** - Branches into retry flow if down Wait 10 Min → Increment Retry → Retry API → Check Retry Response** - Wait and retry API call once If Still No Response** - Verifies if retry also failed If Still No Retry > 4** - Checks if retry limit is reached (≥ 4) Format Down Alert** - Formats the WhatsApp alert with API details Send WhatsApp Alert** - Sends API down alert to the configured number Continue Next API** - Moves to the next API in the list How to Use Import workflow into n8n Configure Google Sheets API for API list access Set up WhatsApp API for alerts Define API details in Google Sheet Test with sample APIs and verify alerts Adjust retry limits or schedule as needed Requirements Access to Google Sheets API WhatsApp API configuration Scheduled trigger setup in n8n Sheet Structure | Sheet Column | Example Data | | -------------------- | ------------------------------------------------------------ | | name | Timeout Test | | method | GET | | url | https://httpbin.org/delay/15 | | headers | {"Content-Type": "application/json"} | | body | {"key": "value"} | | expectedField | status | | expectedValue | success | | expectedStatusCode | 200 | Customizing This Workflow Modify trigger interval Adjust retry limits or wait times Customize WhatsApp alert format Add additional API headers or body data Integrate with other notification services
by Oneclick AI Squad
This workflow utilizes Philips IntelliVue Device details to automatically track patient vitals, such as heart rate and oxygen levels. It quickly spots critical health issues and sends alerts to healthcare staff for fast action. The system saves data for records and helps improve patient care with real-time updates. It’s simple to set up and adjust for different needs. Essential Information Processes data from Philips IntelliVue Devices to monitor vitals instantly. Filters and categorizes conditions as critical or non-critical based on thresholds. Sends clinical alerts for critical conditions and logs data for review. Runs every 30 seconds to ensure timely updates. System Architecture Data Collection Pipeline: Poll Device Data Every 30s**: Continuously retrieves vitals from Philips IntelliVue Devices. Fetch from IntelliVue Gateway**: Retrieves data via HTTP GET requests. Processing Pipeline: Process Device Data**: Analyzes and validates the data stream. Alert Generation Flow: Validate & Enrich Data**: Ensures accuracy and adds patient context. Save to Patient Database**: Stores data for records. Check Alert Status**: Applies rules to trigger alerts. Send Clinical Alert**: Notifies staff for critical conditions. Implementation Guide Import workflow JSON into n8n. Configure the Philips IntelliVue Devices gateway URL and test with sample data. Set up alert credentials (e.g., email). Test and adjust rule thresholds. Technical Dependencies Philips IntelliVue Devices for vitals data. n8n for automation. Email or messaging API for alerts. Database for data storage. Customization Possibilities Adjust Switch node rules for critical thresholds. Customize alert messages. Modify database schema. Add logging for analysis.
by Arkadiusz
What this workflow does This template automates the entire process of documenting Sprint Reviews in Scrum: Input Collection – Through a friendly form, users upload the transcript file (meeting notes, sprint review transcript, or VTT captions) and specify the sprint name and domain. Transcript Parsing – A Code node formats the transcript into clean [HH:MM:SS] Speaker: text lines, supporting VTT, Zoom, or custom timestamp formats used in Scrum events. AI-Driven Summary – The AI Agent (LangChain + OpenAI) produces a well-structured AI summarization in Markdown, including: A 3–5 bullet Executive Summary of sprint review highlights A Presentation Recap table (Timestamp | Presenter | Topics) A list of Action Items with owners (if recognizable from the transcript) Preview – The summary renders as a styled card with custom CSS for easy readability in n8n. Archive – Automatically appends a record to Google Sheets, saving the date, domain, sprint, transcript file name, and the AI-generated sprint review summary. Why it’s useful Zero manual summarizing** – AI extracts key insights from transcript files into Markdown you can instantly share with your Scrum team and stakeholders. Easy setup** – drag-and-drop import, plus form-based input for non-technical users during sprint reviews. Centralized tracking** – all past sprint summaries live in one spreadsheet for retrospectives, audits, and continuous improvement. Flexible and extendable** – you can switch to Airtable, Slack, or Notion, or refine the summary template to match your Scrum workflow. Ideal for Scrum Masters** wanting quick sprint review summaries for stakeholders Agile Coaches** analyzing sprint review transcripts, presentation patterns, and follow-up tasks Product Owners** keeping a searchable log of sprint outcomes and action items Prerequisites / Credentials OpenAI API Key** — required for the AI Agent node (or any other Agent for summarization) Google Sheets OAuth2 credentials** — required for saving sprint review data to Sheets (Optional) Ensure LangChain / AI Agent nodes are installed in your n8n instance How to Use This Template Import the workflow JSON into your n8n instance. Set up credentials: For the OpenAI LLM node, provide your OpenAI API key In Google Sheets, configure OAuth2 and specify your spreadsheet ID (replace YOUR_SHEET_ID) Create a new sheet with the following columns: Date Domain Sprint name Content VTT file Transcript Enable and run the workflow. Fill out the form: upload transcript file, enter sprint & domain, click Create Summary. View the AI-generated Markdown sprint review summary in the preview card. Verify the new entry appears in your Google Sheet with all sprint details.
by Evoort Solutions
Spotify Music Downloader: Effortless Music Downloading from Spotify Description: The Spotify Music Downloader is an automation flow that allows users to easily download music from Spotify tracks. By leveraging the powerful Spotify Downloader API, the flow downloads Spotify tracks, uploads them to Google Drive, and logs the details to Google Sheets for better management. With this tool, you can save time and effort while enjoying the convenience of direct downloads and automatic organization. Use Case: Music Enthusiasts**: Easily download your favorite Spotify tracks and store them in Google Drive. Content Creators**: Automate the process of storing and tracking downloaded music files. Organizational Automation**: Store download links and file sizes in Google Sheets to track downloads systematically. Spotify Users**: Provides a hassle-free way to access and organize your Spotify music offline. Benefits: Simple & Automated**: Easily download and organize music from Spotify with minimal effort. Seamless Integration**: Directly integrates with Google Drive for storage and Google Sheets for tracking. Fast: Uses the **Spotify Downloader API to quickly fetch and download the tracks. Track Downloads**: Keep a record of each download, including size, download link, and other details. Google Drive Storage**: Automatic storage of downloaded tracks in your Google Drive, making it easy to access files anytime. Node-by-Node Explanation: On Form Submission: The flow starts when the user submits a Spotify track URL through a form. HTTP Request (Spotify Downloader API): Sends a request to the Spotify Downloader API to retrieve the music file associated with the given Spotify URL. If (Link Validation): Ensures that the provided Spotify URL is not empty. If1 (Success Validation): Checks if the API response was successful. Download Music: Downloads the music file from the provided Spotify link using the fetched download URL. Google Drive: Uploads the downloaded music file to Google Drive. Google Sheets: Logs the successful download details (like URL, download link, size, and timestamp) to Google Sheets. Code (File Size Calculation): Calculates the file size of the downloaded music file in MB. Wait: Introduces a delay to ensure that the upload process to Google Drive is complete before continuing. Wait1: Another wait node to allow additional time between the various steps in the flow. Google Sheets1 (Success Logs): Adds a new record for a successful download to a Google Sheet. Google Sheets2 (Failed Logs): Records failed download attempts in a secondary Google Sheet. By utilizing this flow, you can automate the process of downloading music from Spotify and storing it in Google Drive while keeping track of every download in Google Sheets. It's an ideal solution for music lovers, content creators, or anyone looking to automate their music download and storage process with ease. Create your free n8n account and set up the workflow in just a few minutes using the link below: 👉 Start Automating with n8n Save time, stay consistent, and grow your LinkedIn presence effortlessly!
by Madame AI
Post Jobs to Multiple Boards from Google Sheets using BrowerAct This powerful n8n template turns a Google Sheet into a control panel for automating job postings across multiple job boards. This workflow is perfect for HR teams, recruiters, and hiring managers who want to streamline their hiring process by posting jobs to multiple boards from a single source of truth. Self-Hosted Only This Workflow uses a community contribution and is designed and tested for self-hosted n8n instances only. How it works The workflow is triggered in two ways: manually (to batch-post all "Ready to Post" jobs) or automatically via a Google Sheets Trigger when a single row is updated. An If node filters for jobs marked with the status 'Ready to Post'. A BrowserAct node takes the job details (title, description, logins, target URL) and runs an automation to post the job on the specified board. An If node checks if the posting was successful. If it fails, a Slack alert is sent. A Code node parses the successful result from BrowserAct to get the status and live URL. The workflow Updates the row in Google Sheets with the Live_URL and changes the Status to 'Posted'. A final Slack message is sent to a channel to confirm the successful posting. Requirements BrowserAct** API account for automated posting BrowserAct* "Automated Job Posting to Niche Job Site (Custom Site)*" Template | User needs to customize the workflow based on the target site. BrowserAct** n8n Community Node -> (n8n Nodes BrowserAct) Google Sheets** credentials Slack** credentials for sending notifications Need Help? How to Find Your BrowseAct API Key & Workflow ID How to Connect n8n to Browseract How to Use & Customize BrowserAct Templates How to Use the BrowserAct N8N Community Node
by Rahul Joshi
Description This workflow acts as a CI/CD-style test harness for validating other n8n workflows. It executes a target workflow (here: Archive Payment Receipts), evaluates pass/fail outcomes, and generates structured reports. Results are automatically archived to Google Drive, logged in Google Sheets, and synced with ClickUp for visibility. Both success and failure scenarios are handled with standardized formatting. What This Template Does (Step-by-Step) ⚡ Manual Trigger – Start the test run manually. ▶️ Execute Target Workflow Under Test – Calls the specified workflow (Archive Payment Receipts) and captures its output, even if it errors. ✅ Test Result Evaluation (If Node) – Checks if the output contains errors. Pass Path → success formatting + archival. Fail Path → failure formatting + logging. 📄 Format Success Test Result (Set Node) – Creates a structured result object with: Status: ✅ Passed Workflow Name Timestamp 📄 Format Failed Test Result (Set Node) – Same as above, but with ❌ Failed status. 📝 Generate Success/Failure Report Text (Code Node) – Converts structured data into a human-readable report string. 📦 Convert Report to Text File – Transforms the text into a .txt file for archiving. ☁️ Archive Reports to Google Drive – Saves .txt files (success/failure) into the resume store folder with timestamped filenames. ✏️ Update ClickUp Task (Success/Failure) – Posts results directly into a ClickUp task for visibility. 📊 Log Error Details to Error Tracking Sheet (Google Sheets) – Appends raw error objects to an error log sheet for debugging and trend analysis. Prerequisites Target workflow to test (e.g., Archive Payment Receipts) Google Drive folder for report storage Google Sheets (Error Log tab) ClickUp API credentials n8n instance Key Benefits ✅ Automates workflow regression testing ✅ Captures pass/fail outcomes with full audit trail ✅ Maintains error logs for debugging and reliability improvements ✅ Keeps stakeholders updated via ClickUp integration ✅ Supports compliance with archived test reports Perfect For Teams running workflow QA & testing Organizations needing audit-ready test reports DevOps pipelines with continuous validation of automations Stakeholders requiring real-time visibility into workflow health
by Trung Tran
AWS IAM Access Key Rotation Reminder Automation Workflow Watch the demo video below: Who’s it for DevOps/SRE teams responsible for AWS account security. Security/compliance officers ensuring key rotation policies are followed. Any AWS account owner who wants automatic detection of stale access keys. How it works / What it does Weekly Scheduler — triggers the workflow on a recurring basis. Get Many Users — fetches all IAM users in the AWS account. Get User Access Key(s) — retrieves the access keys associated with each user. Filter Out Inactive Keys — removes keys that are not active (e.g., status Inactive). Access Key Older Than 365 Days — checks the key creation date and flags keys older than one year. Send Slack Message — notifies a Slack channel with details of the outdated key(s) for review and action. No Operation — safely ends the workflow if no keys match the condition. How to set up Configure the Weekly Scheduler to run at your desired cadence (e.g., every Monday). Use Get Many Users to list all IAM users. For each user, call ListAccessKeys (Get User Access Key(s)) to fetch their key metadata. Apply a filter to keep only keys with status Active. Add a condition to compare CreateDate against today - 365 days. Send results to Slack using the Slack Post Message node. Requirements n8n (latest version). AWS credential in n8n configured for us-east-1 (IAM requires signing with this region). IAM permissions: iam:ListUsers iam:ListAccessKeys Slack bot credentials with permission to post messages in the desired channel. How to customize the workflow Change threshold** — adjust the 365 days condition to 90, 180, or any other rotation policy. Escalation** — mention @security or create a Jira/Ticket when old keys are found. Logging** — push flagged results into a Google Sheet, database, or log management system for audit. Automation** — instead of only notifying, add a step to automatically deactivate keys older than the threshold (after approval). Multi-account support** — duplicate or loop across multiple AWS credentials if you manage several AWS accounts.
by WeblineIndia
Real-Time Uptime Alerts to Jira with Smart Slack On-Call Routing This workflow automatically converts uptime monitoring alerts received via webhook into Jira incident tasks and intelligently notifies an available on-call team member on Slack based on their real-time presence status. It ensures critical service outages never go unnoticed by selecting an active responder and sending a detailed direct message immediately. ⚡ Quick Implementation Steps Import the workflow JSON into n8n. Configure your Webhook, Slack, and Jira credentials. Update the IF node to filter for status = down (already configured). Set the Jira project and issue type as required. Connect your Slack on-call channel. Activate the workflow and send a test alert using Postman or your monitoring tool. What It Does This automation listens for incoming alerts from any uptime monitoring service. When a system or service goes down, the workflow instantly validates whether the alert is critical (status = down). Once validated, it automatically creates a detailed Jira Task containing all relevant service details such as timestamp, downtime duration, error code, customer impact and priority. After the Jira incident is created, the workflow retrieves a list of all members from a dedicated Slack on-call rotation channel. It checks each member’s Slack presence (active, away, offline) and uses smart selection logic to choose the best person to notify. The selected team member then receives a richly formatted direct Slack message containing all incident details and a link to the Jira ticket. This ensures the alert is not only logged properly but also reaches the right responder at the right time. Who’s It For This workflow is perfect for: DevOps teams managing uptime & system reliability. Support teams responsible for incident response. SRE teams using Jira and Slack. Organizations with an on-call rotation setup. Teams wanting automated escalation for downtime alerts. Requirements to Use This Workflow n8n installed** (self-hosted or cloud) Slack API credentials** with permission to read user presence and send direct messages Jira Software Cloud** credentials allowing issue creation A monitoring system** capable of sending webhook alerts (e.g., UptimeRobot, Uptime Kuma, StatusCake, custom system, etc.) Access to a Slack channel that includes your on-call rotation members How It Works & How to Set Up Step 1: Receive Alert from Uptime Monitoring Tool The workflow starts with the Webhook node (Receive Uptime Alert). Your monitoring tool must send a POST request with JSON payload including fields like: serviceName status timestamp customerImpact errorCode priority etc. Step 2: Filter for Critical Status The IF node (Filter for Critical Status) checks: Only when the service is down does the workflow continue to create a Jira incident. Step 3: Create Jira Incident Task The Create New Jira Incident node generates a Jira Task with: Summary: serviceName + timestamp Description: dynamic fields based on the alert payload Set your Jira Project and Issue Type as needed. Step 4: Fetch Slack On-Call Channel Members The workflow calls Slack API to retrieve all user IDs in a designated channel (e.g., #on-call-team). Step 5: Loop Through Each Member Split In Batches Node** loops each Slack member individually. For each user, their Slack presence is fetched using: Step 6: Build Final Data for Each User The Set node (Collect & Set Final Data) stores: presence member ID service details Jira ticket ID downtime info and more Step 7: Select the Best On-Call User A custom Code node uses presence-based logic: Selection Logic If one or more users are active → randomly pick one active user. If only one user is active → pick that user. If no users are active → default to the first member from the channel. This ensures you always get a responder. Step 8: Notify Selected User The Slack Notify Node sends a formatted direct message with: service status downtime duration error code customer impact Jira ticket link priority The selected on-call responder receives everything they need to act immediately. How to Customize Nodes Webhook Node Change the path to something meaningful (e.g., /uptime-alerts). Customize expected fields based on your monitoring tool's payload. IF Node Modify status condition for: "critical" "error" or multiple conditions Jira Node You can customize: Issue type (Incident, Bug, Task) Priority field mapping Project ID Custom fields or labels Slack Retrieval Node Change the channel to your team's actual on-call rotation channel. Slack Message Node Modify message formatting, tone, emojis, or add links. Add @mentions or tags. Include escalation instructions. Add-Ons (Optional Extensions) Enhance the workflow by adding: 1. Escalation Logic If the selected user doesn’t respond within X minutes, notify next user. 2. PagerDuty / OpsGenie Integration Trigger paging systems for SEV-1 incidents. 3. Status Page Updates Automatically update public status pages. 4. Auto-Resolution When service status returns to up, automatically: Update Jira ticket Notify the team Close the incident 5. Logging & Analytics Store incidents in Google Sheets, Notion, or a database. Use Case Examples This workflow can support multiple real-world scenarios: Website Uptime Monitoring If your main website goes down, instantly create a Jira incident and notify your on-call engineer. API Downtime Alerting When an API endpoint fails health checks, alert active developers only. Microservices Monitoring Each microservice alert triggers a consistent, automated incident creation and notification. Infrastructure Failure Detection When servers, containers, or VMs become unreachable, escalate to your infrastructure team. Database Performance Degradation If DB uptime drops or error rate spikes, create a Jira ticket and ping the database admin. And many more variations of outage, error, and performance monitoring events. Troubleshooting Guide | Issue | Possible Cause | Solution | |-------|----------------|----------| | Workflow not triggering | Webhook URL not updated in monitoring tool | Copy n8n webhook URL and update in monitoring source | | No Jira ticket created | Invalid Jira credentials or missing project permissions | Reauthorize Jira credentials and verify permissions | | Slack users not found | Wrong channel ID or bot not added to channel | Ensure bot is invited to the Slack channel | | Slack presence not returning | Slack app lacks presence permission (users:read.presence) | Update Slack API scopes and reinstall | | No user receives notification | Presence logic always returns empty list | Test Slack presence API and verify real-time presence | | Wrong user selected | Intended selection logic differs | Update the JS logic in the code node | | Jira fields not populated | Alert payload fields missing | Verify webhook payload structure and match expected fields | Need Help? If you need assistance setting up this workflow, customizing integrations, building escalations or extending the logic with add-ons — WeblineIndia is here to help. We can assist with: Custom Slack/Jira/Monitoring automation On-call rotation logic enhancements Cloud deployment & workflow optimization Any custom n8n automation Production-grade monitoring workflows 👉 Contact WeblineIndia for professional support, implementation and custom workflow development.
by PollupAI
This workflow provides a powerful way to automatically document and maintain an inventory of all your n8n workflows in a Google Sheet. By running on a schedule or manually, it fetches details about every workflow on your instance, processes the key information, and then populates a spreadsheet. This creates a centralized, up-to-date dashboard for auditing, monitoring, and understanding your automation landscape. Who is this for? This workflow is ideal for n8n administrators, developers, and teams who manage multiple workflows. If you need a clear and simple way to track all your automations, their components, and their statuses without manually checking each one, this template is for you. It's particularly useful for maintaining technical documentation, auditing node usage across your instance, and quickly finding specific workflows. What problem is this workflow solving? As the number of workflows on an n8n instance grows, it becomes challenging to keep track of them all. Questions like "Which workflows use the HubSpot node?", "Which workflows are inactive?", or "When was this workflow last updated?" become difficult to answer. This workflow solves that problem by creating a single source of truth in a Google Sheet. It automates the process of cataloging your workflows, saving you time and ensuring your documentation is always current. What this workflow does Triggers Execution: The workflow can be initiated either on a set schedule (via the Scheduled Start node) or manually (via the Manual Start node). Fetches All Workflows: The Get All Workflows node connects to your n8n instance via the API to retrieve a complete list of your workflows and their associated data. Processes Workflows Individually: The Loop Through Each Workflow node iterates through each retrieved workflow one by one so they can be processed individually. Extracts Key Information: The Extract Workflow Details node uses custom code to process the data for each workflow, extracting essential details like its name, ID, tags, and a unique list of all node types it contains. Updates Google Sheet: The Add/Update Row in Google Sheet node then takes this information and appends or updates a row in your designated spreadsheet, using the workflow ID as a unique key to prevent duplicates. Waits and Repeats: The Pause to Avoid Rate Limits node adds a short delay to prevent issues with API limits before the loop continues to the next workflow. Setup Configure Get All Workflows Node: Select the Get All Workflows node. In the 'Credentials' section, provide your n8n API credentials to allow the workflow to access your instance's data. Prepare Your Google Sheet: Create a new Google Sheet. Set up the following headers in the first row: id, title, link, tags, nodes, CreatedAt, UpdatedAt, Active, Archived. Configure Add/Update Row in Google Sheet Node: Select the Add/Update Row in Google Sheet node. Authenticate your Google account in the 'Credentials' section. In the 'Document ID' field, enter the ID of your Google Sheet. You can find this in the sheet's URL (e.g., .../spreadsheets/d/THIS_IS_THE_ID/edit). Select your sheet from the 'Sheet Name' dropdown. Under 'Columns', ensure the id field is set as the 'Matching Columns' value. This is crucial for updating existing rows correctly. Activate the Workflow: Choose your preferred trigger. You can enable the Schedule Trigger to run the sync automatically at regular intervals. Save and activate the workflow. How to customize this workflow to your needs Track Different Data**: You can modify the Extract Workflow Details node to extract other pieces of information from the workflow JSON. For example, you could parse the settings object or count the total number of nodes. Remember to add a corresponding column in your Google Sheet and map it in the Google Sheets node. Add Notifications**: Add a notification node (like Slack, Discord, or Email) after the Loop Through Each Workflow node (in the second output) to be alerted when the sync is complete or if an error occurs. Filter Workflows**: You can add an IF node after the Loop Through Each Workflow node to filter which workflows get added to the sheet. For instance, you could choose to only log active workflows ({{ $('Loop Through Each Workflow').item.json.active }} is true) or workflows containing a specific tag. Adjust Wait Time**: The Pause to Avoid Rate Limits node is set to pause between each entry. You can adjust this time or remove it entirely if you have a small number of workflows and are not concerned about hitting API rate limits.
by Miha
This n8n template turns raw call transcripts into clean HubSpot call logs and a single, actionable follow-up task—automatically. Paste a transcript and the contact’s email; the workflow finds the contact, summarizes the conversation in 120–160 words, proposes the next best action, and (optionally) updates missing contact fields. Perfect for reps and founders who want accurate CRM hygiene without the manual busywork. How it works A form trigger collects two inputs: Contact email Plain-text call transcript The workflow looks up the HubSpot contact by email to pull known properties. An AI agent reads the transcript (plus known fields) to: Extract participants, role, problem/opportunity, requirements, blockers, timeline, and metrics. Write a 120–160 word recap a teammate can skim. Generate one concrete follow-up task (title + body). Suggest updates for missing contact properties (city, country, job title, job function). The recap is logged to HubSpot as a completed Call engagement. The follow-up is created in HubSpot as a Task with subject and body. (Optional) The contact record is updated using AI-suggested values if the transcript clearly mentions them. How to use Connect HubSpot (OAuth2) on all HubSpot nodes. Connect OpenAI on the AI nodes. Open Form: Capture Transcript, submit the email + transcript. (Optional) In AI: Summarize Call & Draft Task, tweak prompt rules (word count, date normalization). (Optional) In Update Contact from Transcript, review the mapped fields before enabling in production. Activate the workflow and paste transcripts after each call. Requirements HubSpot** (OAuth2) for contact search, call logging, and tasks OpenAI** for summarization and task drafting Notes & customization ideas Swap the form for a Google Drive or S3 watcher to ingest saved transcripts. Add a speech-to-text step if you store audio recordings. Extend Update Contact to include additional fields (timezone, department, seniority). Post the summary to Slack or email the AE for quick handoffs. Gate updates with a confidence check, or route low-confidence changes for manual approval.
by Asfandyar Malik
Short Description: Automatically collect and analyze your competitor’s YouTube performance. This workflow extracts video titles, views, likes, and descriptions from any YouTube channel and saves the data to Google Sheets — helping creators spot viral trends and plan content that performs. Who’s it for For content creators, YouTubers, and marketing teams who want to track what’s working for their competitors — without manually checking their channels every day. How it works This workflow automatically collects data from any YouTube channel you enter. You just write the channel name in the form — n8n fetches the channel ID, gets all recent video IDs, and extracts each video’s title, views, likes, and description. Finally, all the information is saved neatly into a connected Google Sheet for analysis. How to set up Create a Google Sheet with columns for Title, Views, Likes, Description, and URL. Connect your Google account to n8n. Add your YouTube Data API key inside the HTTP Request nodes (use n8n credentials, not hardcoded keys). Update your form submission or trigger node to match your input method. Execute the workflow once to test and verify that data is flowing into your sheet. Requirements YouTube Data API key Google Sheets account n8n cloud or self-hosted instance How to customize You can modify the JavaScript code node to include more metrics (like comments or publish date), filter by keywords, or change the output destination (e.g., Airtable or Notion).
by Oneclick AI Squad
This automated n8n workflow streamlines invoice creation and payment reminders. It generates invoices on a monthly schedule and sends reminders for overdue payments, updating records in Google Sheets. Good to Know Supports monthly invoice generation and daily overdue checks Integrates with Google Sheets for data management Uses email notifications for invoice delivery and reminders Includes logging for tracking and auditing Features multiple reminder types based on overdue duration How It Works Invoice Creation Flow: Monthly Invoice Trigger** - Initiates workflow on a set monthly schedule Get Clients for Invoicing** - Reads client data from Google Sheet Filter Active Clients** - Filters out inactive clients Generate Invoice Data** - Creates invoice details in required format Save Invoice to Google Sheets** - Appends or updates invoice record in the sheet Send Invoice Email** - Sends the invoice to the client via email Log Invoice Creation** - Logs invoice creation for records/auditing Reminder Flow: Daily Payment Reminder Check** - Triggers workflow daily to check overdue invoices Get Overdue Invoices** - Reads overdue invoices from Google Sheet Filter Overdue Invoices** - Filters invoices still unpaid Calculate Reminder Type** - Calculates how many days overdue Switch Reminder Type** - Decides which type of reminder to send Send Gentle / Follow-up / Urgent / Final Notice** - Sends respective reminder email Update Reminder Log** - Updates reminder status in the sheet How to Use Import workflow into n8n Configure Google Sheets API for data access Set up email service for notifications Define monthly schedule for invoice trigger Test with sample client data and monitor reminders Adjust reminder thresholds as needed Requirements Access to Google Sheets API Email service configuration Scheduled trigger setup in n8n Sheet Columns: Client Name** Invoice ID** Amount** Due Date** Status** Reminder Type** Last Updated** Customizing This Workflow Modify invoice generation schedule Adjust reminder email templates Configure custom Google Sheet columns Set custom overdue thresholds Integrate additional notification methods