HumationHuman + Automation
Back to Catalog

Backup workflows to git repository on Github

ShashikanthShashikanth
7156 views
2/3/2026
AuthenticationEmailSupabasePasswordlessMagic Link
Official Page

Source code, I maintain this worflow here.

Usage Guide

This workflow backs up all workflows as JSON files named in the [workflow_name].json format.

Steps

  1. Create GitHub Repository

    • Skip this step if using an existing repository.

  2. Add GitHub Credentials

    • In Credentials, add the GitHub credential for the repository owner.

  3. Download and Import Workflow

    • Import this workflow into n8n.

  4. Set Global Values

    • In the Globals node, set the following:
      • repo.owner: GitHub username of the repository owner.
      • repo.name: Name of the repository for backups.
      • repo.path: Path to the folder within the repository where workflows will be saved.

  5. Configure GitHub Nodes

    • Edit each GitHub node in the workflow to use the added credentials.

Workflow Logic

Each workflow run handles files based on their status:

  1. New Workflow

    • If a workflow is new, create a new file in the repository.

  2. Unchanged Workflow

    • If the workflow is unchanged, skip to the next item.

  3. Changed Workflow

    • If a workflow has changes, update the corresponding file in the repository.

Current Limitations / Needs work

  1. Name Change of Workflows
    • If a workflow is renamed or deleted in n8n, the old file remains in the repository.
  2. Deleted Workflows
    • Deleted workflows in n8n are not removed from the repository.

n8n Workflow: Backup Workflows to GitHub

This n8n workflow provides a robust solution for regularly backing up your n8n workflows to a GitHub repository. It automates the process of fetching workflow definitions, preparing them, and committing them to a specified GitHub repository, ensuring your workflow configurations are version-controlled and recoverable.

What it does

This workflow performs the following key steps:

  1. Triggers on a Schedule: The workflow starts at predefined intervals, ensuring regular backups.
  2. Fetches n8n Workflows: It connects to your n8n instance to retrieve a list of all active workflows.
  3. Filters for Active Workflows: It checks if a workflow is active before processing it for backup.
  4. Prepares Workflow Data: For each active workflow, it extracts the JSON definition.
  5. Formats for GitHub: It transforms the workflow JSON into a format suitable for committing to a GitHub file, including setting the file path and commit message.
  6. Commits to GitHub: It creates or updates a file in your designated GitHub repository with the workflow's JSON content.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: An active n8n instance where your workflows are running.
  • GitHub Account: A GitHub account with a repository where you want to store your workflow backups.
  • n8n API Access: Ensure your n8n instance has API access enabled.
  • GitHub Credential in n8n: A configured GitHub credential in your n8n instance with permissions to write to the target repository.
  • n8n Credential in n8n: A configured n8n credential in your n8n instance to access its own API.

Setup/Usage

  1. Import the workflow: Download the JSON provided and import it into your n8n instance.
  2. Configure Credentials:
    • GitHub Node (ID: 16): Select or create a GitHub credential that has write access to your backup repository.
    • n8n Node (ID: 826): Select or create an n8n credential that allows it to access its own workflows.
  3. Configure GitHub Repository Details:
    • In the GitHub Node (ID: 16), specify the Owner (your GitHub username or organization) and Repository name where you want to store the backups.
    • You might also want to adjust the File Path expression to define how the workflow files are named (e.g., workflows/{{ $json.name }}.json).
  4. Configure Schedule Trigger (ID: 839): Adjust the schedule to your desired backup frequency (e.g., daily, weekly).
  5. Activate the Workflow: Once configured, activate the workflow. It will then run automatically based on your defined schedule.

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

ShadrackBy Shadrack
331

Automated YouTube video uploads with 12h interval scheduling in JST

This workflow automates a batch upload of multiple videos to YouTube, spacing each upload 12 hours apart in Japan Standard Time (UTC+9) and automatically adding them to a playlist. βš™οΈ Workflow Logic Manual Trigger β€” Starts the workflow manually. List Video Files β€” Uses a shell command to find all .mp4 files under the specified directory (/opt/downloads/单词卑/A1-A2). Sort and Generate Items β€” Sorts videos by day number (dayXX) extracted from filenames and assigns a sequential order value. Calculate Publish Schedule (+12h Interval) β€” Computes the next rounded JST hour plus a configurable buffer (default 30 min). Staggers each video’s scheduled time by order Γ— 12 hours. Converts JST back to UTC for YouTube’s publishAt field. Split in Batches (1 per video) β€” Iterates over each video item. Read Video File β€” Loads the corresponding video from disk. Upload to YouTube (Scheduled) β€” Uploads the video privately with the computed publishAtUtc. Add to Playlist β€” Adds the newly uploaded video to the target playlist. πŸ•’ Highlights Timezone-safe: Pure UTC ↔ JST conversion avoids double-offset errors. Sequential scheduling: Ensures each upload is 12 hours apart to prevent clustering. Customizable: Change SPANHOURS, BUFFERMIN, or directory paths easily. Retry-ready: Each upload and playlist step has retry logic to handle transient errors. πŸ’‘ Typical Use Cases Multi-part educational video series (e.g., A1–A2 English learning). Regular content release cadence without manual scheduling. Automated YouTube publishing pipelines for pre-produced content. --- Author: Zane Category: Automation / YouTube / Scheduler Timezone: JST (UTC+09:00)

ZaneBy Zane
226

Monitor bank transactions with multi-channel alerts for accounting teams

Enhance financial oversight with this automated n8n workflow. Triggered every 5 minutes, it fetches real-time bank transactions via an API, enriches and transforms the data, and applies smart logic to detect critical, high, and medium priority alerts based on error conditions, amounts, or risk scores. It sends multi-channel notifications via email and Slack, logs all data to Google Sheets, and generates summary statistics for comprehensive tracking. πŸ’°πŸš¨ Key Features Real-time monitoring every 5 minutes for instant alerts. Smart prioritization (Critical, High, Medium) based on risk and errors. Multi-channel notifications via email and Slack. Detailed logging and summary reports in Google Sheets. How It Works Schedule Trigger: Runs every 5 minutes. Fetch Transactions: HTTP request retrieves real-time transaction data. API Error?: If condition for error logic is met, sends error alert. Enrich & Transform Data: Advanced risk calculation enhances data. Critical Alert?: If condition (50% or risk > 8) is met, raises alert. High Priority?: If condition (5% or risk > 7) is met, raises alert. Medium Priority?: If condition is met, raises alert. Log Priority to Sheet: Google Sheets appends critical, high, or medium priority data. Send Critical Email: HTML email to execute sheets append. Send High Priority Email: Email to finance team. Send High Priority Slack: Slack notification to finance team. Send Medium Priority Email: Email to finance team. Merge All Alerts: Combines all alerts for comprehensive tracking. Generate Summary Stats: Code block for analytics. Log Summary to Sheet: Summary statistics storage. Setup Instructions Import the workflow into n8n and configure the bank API credentials in "Fetch Transactions." Set up Google Sheets OAuth2 and replace the sheet ID for logging nodes. Configure Gmail API Key and Slack Bot Token for alerts. Test the workflow with sample transaction data exceeding risk or amount thresholds. Adjust priority conditions (e.g., 50%, 5%, risk > 8) based on your risk policy. Prerequisites Bank API access with real-time transaction data (e.g., https://api.bank.com) Google Sheets OAuth2 credentials Gmail API Key for email alerts Slack Bot Token (with chat:write permissions) Structured transaction data format Google Sheet Structure: Create a sheet with columns: Transaction ID Amount Date Risk Score Priority (Critical/High/Medium) Alert Sent Summary Stats Updated At Modification Options Adjust the "Schedule Trigger" interval (e.g., every 10 minutes). Modify "Critical Alert?" and "High Priority?" conditions for custom thresholds. Customize email and Slack templates with branded messaging. Integrate with fraud detection tools for enhanced risk analysis. Enhance "Generate Summary Stats" with additional metrics (e.g., average risk). Discover more workflows – Get in touch with us

Oneclick AI SquadBy Oneclick AI Squad
333