Automated workflow backup system with Google Drive, GitHub & messaging alerts
Why You Need This Right Now 💡
Stop the panic attacks. We've all been there - accidentally deleted a workflow that took hours to build, or worse, corrupted your entire automation setup. This workflow is your safety net.
Save your weekends. Instead of spending hours recreating lost work, get back to what matters. One setup protects everything, automatically.
Sleep better at night. Your workflows are safely stored in two places with full version history. If something breaks, you're back online in minutes, not days.
Perfect For These Situations ⚡
✅ Business owners running critical automations
✅ Agencies managing client workflows
✅ Teams who need audit trails
✅ Anyone who values their time and sanity
How It Actually Works 🔧
Think of it like having a personal assistant who:
- Checks your workflows twice daily (you can change this)
- Creates organized backups with timestamps
- Stores them safely in Google Drive AND GitHub
- Tells you it's done via Telegram or Discord
- Keeps everything tidy with smart folder organization
The result? A timestamped folder in your Google Drive and organized files in your GitHub repo. Everything is searchable, restorable, and audit-ready.
Quick 5-Minute Setup 🚀
- Import this workflow to your n8n
- Connect your accounts (Google Drive, GitHub, optional notifications)
- Set your preferences (which folder, which repo, how often)
- Test it once to make sure everything works
- Relax knowing your workflows are protected
What You'll Need 📋
- Your n8n instance (obviously!)
- Google Drive account (free works fine)
- GitHub account (free works too)
- 5 minutes of setup time
- Optional: Telegram or Discord for notifications
Pro Tips for Power Users 🧠
Want to level up? Here are some ideas:
- Add encryption for sensitive workflows
- Create restore workflows for one-click recovery
- Set up pull requests for team review of changes
- Customize schedules based on your workflow update frequency
Created by: khaisa Studio - Automation experts who actually use this stuff daily
Tags: backup, automation, n8n, google-drive, github, workflow-protection, business-continuity
Questions? Get in touch - I'm always happy to help fellow automation enthusiasts!
Remember: The best backup is the one you set up before you need it. Your future self will thank you!
Automated Workflow Backup System with Google Drive, GitHub, and Messaging Alerts
This n8n workflow provides a robust, automated system for backing up your n8n workflows. It fetches all active workflows, converts them into a human-readable JSON file, stores them in Google Drive, commits them to a GitHub repository, and sends notifications to Telegram and Discord upon completion or failure.
What it does
This workflow automates the following steps:
- Triggers on Schedule or Manually: The workflow can be initiated manually or on a predefined schedule (e.g., daily, weekly).
- Fetches All Active Workflows: It retrieves a list of all active workflows from your n8n instance.
- Filters Out Itself: The workflow intelligently excludes itself from the backup process to prevent infinite loops or redundant backups.
- Converts Workflows to JSON File: Each workflow's JSON definition is collected and then converted into a single
.jsonfile for easy storage and versioning. - Stores Backup in Google Drive: The generated JSON backup file is uploaded to a specified folder in Google Drive.
- Commits Backup to GitHub: The workflow then commits the JSON backup file to a designated GitHub repository, allowing for version control and historical tracking of workflow changes.
- Sends Success Notifications: Upon successful completion of the backup, a confirmation message is sent to a specified Telegram chat and Discord channel.
- Sends Failure Notifications: If any step in the backup process fails, an alert message is sent to the same Telegram chat and Discord channel, providing details about the error.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: An active n8n instance where this workflow will run.
- Google Drive Account: A Google Drive account with a designated folder for backups.
- GitHub Account: A GitHub account with a repository created for storing workflow backups. You will need a Personal Access Token (PAT) with appropriate permissions (e.g.,
repo). - Telegram Bot Token and Chat ID: A Telegram bot and the chat ID where you want to receive notifications.
- Discord Webhook URL: A Discord webhook URL for sending notifications to a specific channel.
- n8n API Key: An n8n API key to allow the workflow to interact with your n8n instance (specifically to fetch workflows).
Setup/Usage
- Import the Workflow:
- Copy the provided JSON code.
- In your n8n instance, go to "Workflows" and click "New".
- Click the "Import from JSON" button and paste the copied JSON.
- Configure Credentials:
- GitHub: Set up a GitHub credential with a Personal Access Token (PAT) that has access to your backup repository.
- Google Drive: Set up a Google Drive OAuth2 credential.
- Telegram: Set up a Telegram credential using your bot token.
- Discord: Set up a Discord credential using your webhook URL.
- n8n: Set up an n8n API credential.
- Update Node Parameters:
- Google Drive (ID 58):
- Specify the
Folder IDwhere you want to store the backups.
- Specify the
- GitHub (ID 16):
- Enter your
Owner(GitHub username or organization). - Enter the
Repositoryname. - Adjust the
File Nameif needed (default isn8n_workflows_backup.json). - Customize the
Commit Messageas desired.
- Enter your
- Telegram (ID 49):
- Enter the
Chat IDfor success and failure notifications.
- Enter the
- Discord (ID 60):
- Ensure the webhook URL is correctly configured in your Discord credential.
- Code (ID 834): This node contains logic to filter out the current workflow from the backup. Ensure its logic is sound if you modify the workflow's name.
- Google Drive (ID 58):
- Activate the Workflow:
- Once all credentials and parameters are configured, activate the workflow.
- You can run it manually using the "Execute Workflow" button or let the "Schedule Trigger" (ID 839) handle it automatically based on its configured schedule.
This setup ensures that your n8n workflows are regularly backed up and version-controlled, providing peace of mind and an easy recovery path.
Related Templates
Track daily moods with AI analysis & reports using GPT-4o, Data Tables & Gmail
Track your daily mood in one tap and receive automated AI summaries of your emotional trends every week and month. Perfect for self-reflection, wellness tracking, or personal analytics. This workflow logs moods sent through a webhook (/mood) into Data Tables, analyzes them weekly and monthly with OpenAI (GPT-4o), and emails you clear summaries and actionable recommendations via Gmail. ⚙️ How It Works Webhook – Mood → Collects new entries (🙂, 😐, or 😩) plus an optional note. Set Mood Data → Adds date, hour, and note fields automatically. Insert Mood Row → Stores each record in a Data Table. Weekly Schedule (Sunday 20:00) → Aggregates the last 7 days and sends a summarized report. Monthly Schedule (Day 1 at 08:00) → Aggregates the last 30 days for a deeper AI analysis. OpenAI Analysis → Generates insights, patterns, and 3 actionable recommendations. Gmail → Sends the full report (chart + AI text) to your inbox. 📊 Example Auto-Email Weekly Mood Summary (last 7 days) 🙂 5 ██████████ 😐 2 ████ 😩 0 Average: 1.7 (Positive 🙂) AI Insights: You’re trending upward this week — notes show that exercise days improved mood. Try keeping short walks mid-week to stabilize energy. 🧩 Requirements n8n Data Tables enabled OpenAI credential (GPT-4o or GPT-4 Turbo) Gmail OAuth2 credential to send summaries 🔧 Setup Instructions Connect your credentials: Add your own OpenAI and Gmail OAuth2 credentials. Set your Data Table ID: Open the Insert Mood Row node and enter your own Data Table ID. Without this, new moods won’t be stored. Replace the email placeholder: In the Gmail nodes, replace your.email@example.com with your actual address. Deploy and run: Send a test POST request to /mood (e.g. { "mood": "🙂", "note": "productive day" }) to log your first entry. ⚠️ Before activating the workflow, ensure you have configured the Data Table ID in the “Insert Mood Row” node. 🧠 AI Analysis Interprets mood patterns using GPT-4o. Highlights trends, potential triggers, and suggests 3 specific actions. Runs automatically every week and month. 🔒 Security No personal data is exposed outside your n8n instance. Always remove or anonymize credential references before sharing publicly. 💡 Ideal For Personal mood journaling and AI feedback Therapists tracking client progress Productivity or self-quantification projects 🗒️ Sticky Notes Guide 🟡 Mood Logging Webhook POST /mood receives mood + optional note. ⚠️ Configure your own Data Table ID in the “Insert Mood Row” node before running. 🟢 Weekly Summary Runs every Sunday 20:00 → aggregates last 7 days → generates AI insights + emails report. 🔵 Monthly Summary Runs on Day 1 at 08:00 → aggregates last 30 days → creates monthly reflection. 🟣 AI Analysis Uses OpenAI GPT-4o to interpret trends and recommend actions. 🟠 Email Delivery Sends formatted summaries to your inbox automatically.
By Jose CastilloIT ops AI SlackBot workflow - chat with your knowledge base
Video Demo: Click here to see a video of this workflow in action. Summary Description: The "IT Department Q&A Workflow" is designed to streamline and automate the process of handling IT-related inquiries from employees through Slack. When an employee sends a direct message (DM) to the IT department's Slack channel, the workflow is triggered. The initial step involves the "Receive DMs" node, which listens for new messages. Upon receiving a message, the workflow verifies the webhook by responding to Slack's challenge request, ensuring that the communication channel is active and secure. Once the webhook is verified, the workflow checks if the message sender is a bot using the "Check if Bot" node. If the sender is identified as a bot, the workflow terminates the process to avoid unnecessary actions. If the sender is a human, the workflow sends an acknowledgment message back to the user, confirming that their query is being processed. This is achieved through the "Send Initial Message" node, which posts a simple message like "On it!" to the user's Slack channel. The core functionality of the workflow is powered by the "AI Agent" node, which utilizes the OpenAI GPT-4 model to interpret and respond to the user's query. This AI-driven node processes the text of the received message, generating an appropriate response based on the context and information available. To maintain conversation context, the "Window Buffer Memory" node stores the last five messages from each user, ensuring that the AI agent can provide coherent and contextually relevant answers. Additionally, the workflow includes a custom Knowledge Base (KB) tool (see that tool template here) that integrates with the AI agent, allowing it to search the company's internal KB for relevant information. After generating the response, the workflow cleans up the initial acknowledgment message using the "Delete Initial Message" node to keep the conversation thread clean. Finally, the generated response is sent back to the user via the "Send Message" node, providing them with the information or assistance they requested. This workflow effectively automates the IT support process, reducing response times and improving efficiency. To quickly deploy the Knowledge Ninja app in Slack, use the app manifest below and don't forget to replace the two sample urls: { "display_information": { "name": "Knowledge Ninja", "description": "IT Department Q&A Workflow", "background_color": "005e5e" }, "features": { "bot_user": { "display_name": "IT Ops AI SlackBot Workflow", "always_online": true } }, "oauth_config": { "redirect_urls": [ "Replace everything inside the double quotes with your slack redirect oauth url, for example: https://n8n.domain.com/rest/oauth2-credential/callback" ], "scopes": { "user": [ "search:read" ], "bot": [ "chat:write", "chat:write.customize", "groups:history", "groups:read", "groups:write", "groups:write.invites", "groups:write.topic", "im:history", "im:read", "im:write", "mpim:history", "mpim:read", "mpim:write", "mpim:write.topic", "usergroups:read", "usergroups:write", "users:write", "channels:history" ] } }, "settings": { "event_subscriptions": { "request_url": "Replace everything inside the double quotes with your workflow webhook url, for example: https://n8n.domain.com/webhook/99db3e73-57d8-4107-ab02-5b7e713894ad", "bot_events": [ "message.im" ] }, "orgdeployenabled": false, "socketmodeenabled": false, "tokenrotationenabled": false } }
By Angel MenendezPublishing videos across multiple platforms with Blotato (Instagram, YouTube)
Description This workflow automates video distribution to 9 social platforms simultaneously using Blotato's API. It includes both a scheduled publisher (checks Google Sheets for videos marked "Ready") and a subworkflow (can be called from other workflows). Perfect for creators and marketers who want to eliminate manual posting across Instagram, YouTube, TikTok, Facebook, LinkedIn, Threads, Twitter, Bluesky, and Pinterest. --- How It Works Scheduled Publisher Workflow Schedule Trigger – Runs daily at 10 PM (configurable). Fetch Video – Pulls video URL and description from Google Sheets where "ReadyToPost" = "Ready". Upload to Blotato – Sends video to Blotato's media service. Broadcast to 9 Platforms – Publishes simultaneously to all connected social accounts. Update Sheet – Changes "ReadyToPost" to "Finished" so it won't repost. --- Subworkflow: Video Publisher (Reusable) Receive Input – Gets URL, title, and description from parent workflow. Fetch Credentials – Pulls Blotato API key from n8n Data Table. Upload & Distribute – Uploads to Blotato, then posts to all platforms. Completion Signal – Returns to parent workflow when done. > 💡 Tip: The subworkflow can be called from ANY workflow - great for posting videos generated by AI workflows, webhook triggers, or manual forms. --- Test Workflow (Optional) Form Submission – Upload a video file with title and description. Upload to Dropbox – Generates shareable URL via "[SUB] Dropbox Upload Link" subworkflow. Trigger Publisher – Calls the subworkflow above to distribute the video. --- Setup Instructions Estimated Setup Time: 20-25 minutes Step 1: Blotato Account Setup Create account at Blotato Dashboard Connect all your social media accounts (most time-consuming step) Go to Settings and copy your account IDs for each platform Go to API Settings and copy your API key Step 2: Configure Workflow Update Social IDs: Open "Assign Social Media IDs" node Replace placeholder IDs with your actual Blotato account IDs: json { "instagramid": "YOURID", "youtubeid": "YOURID", "tiktokid": "YOURID", ... } Create Data Table: Create n8n Data Table named "Credentials" Add columns: service and token Add row: service = blotato, token = YOURAPIKEY Set Up Google Sheet: Create sheet with columns: URL VIDEO, ReadyToPost, Description, Titre (Title) Add video data Set ReadyToPost to "Ready" for videos you want to post Connect Your Sheet: Update "Get my video" node with your Google Sheet ID > ⚙️ Pro Tip: If you don't need the scheduled version, just use the subworkflow and call it from other workflows. --- Use Cases AI Video Workflows: Automatically post videos generated by Veo, Sora, or other AI models to all platforms. Content Schedulers: Queue videos in Google Sheets, let the scheduler post them automatically. Batch Publishing: Generate 10 videos, mark them all "Ready", and let the workflow distribute them. Marketing Campaigns: Coordinate multi-platform launches with a single click. Agencies: Manage multiple client accounts by swapping Blotato credentials in the Data Table. --- Customization Options Remove Unused Platforms: Disconnect any social media nodes you don't use (speeds up execution). Change Schedule: Modify the Schedule Trigger to run multiple times per day or on specific days. Different File Hosts: Replace Dropbox with Google Drive, S3, or Cloudinary in the test workflow. Platform-Specific Captions: Add IF nodes before each platform to customize descriptions or add hashtags. Add Approval Step: Insert a WhatsApp or Telegram notification before posting for manual review. Watermarks: Add a Code node to overlay branding before uploading to Blotato. --- Important Notes ⚠️ Two Workflows in One File: Lines 1-600: Scheduled publisher (checks Google Sheets) Lines 600+: Subworkflow (called by other workflows) ⚠️ Data Table vs. Hardcoding: Scheduled workflow: Hardcoded API keys in HTTP nodes Subworkflow: Uses Data Table for API keys (recommended approach) ⚠️ Why Use the Subworkflow? Can be called from ANY workflow Easier to manage API keys (one place to update) More flexible for complex automation systems
By Anthony