Backup & restore n8n workflows with Telegram, Google Drive and form upload
Secure your n8n automations with this comprehensive template that automates periodic backups to Telegram for instant access while enabling flexible restores from Google Drive links or direct file uploads—ensuring quick recovery without data loss.
📋 What This Template Does
This dual-branch workflow handles full n8n instance backups and restores seamlessly. The backup arm runs every 3 days, fetching all workflows via the n8n API, aggregating them into a JSON array, converting to a text file, and sending it to Telegram for offsite storage and sharing. The restore arm supports two entry points: manual execution to pull a backup from Google Drive or form-based upload for local files, then parses the JSON, cleans workflows for compatibility, and loops to create missing ones or update existing by name—handling batches efficiently to respect API limits.
- Scheduled backups with Telegram delivery for easy stakeholder access
- Dual restore paths: Drive download or direct file upload via form
- Intelligent create-or-update logic with data sanitization to avoid conflicts
- Looped processing with existence checks and error continuation
🔧 Prerequisites
- n8n instance with API enabled (self-hosted or cloud)
- Telegram account for bot setup
- Google Drive account (optional, for Drive-based restores)
🔑 Required Credentials
n8n API Setup
- In n8n, navigate to Settings → n8n API
- Enable the API and generate a new key
- Add to n8n as "n8n API" credential type, pasting the key in the API Key field
Telegram API Setup
- Message @BotFather on Telegram to create a new bot and get your token
- Find your chat ID by messaging @userinfobot
- Add to n8n as "Telegram API" credential type, entering the Bot Token
Google Drive OAuth2 API Setup
- In Google Cloud Console, go to APIs & Services → Credentials
- Create an OAuth 2.0 Client ID for Web application, enable Drive API
- Add redirect URI: [your-n8n-instance-url]/rest/oauth2-credential/callback
- Add to n8n as "Google Drive OAuth2 API" credential type and authorize
⚙️ Configuration Steps
- Import the workflow JSON into your n8n instance
- Assign the n8n API, Telegram API, and Google Drive credentials to their nodes
- Update the Telegram chat ID in the "Send Backup to Telegram" node
- Set the Google Drive file ID in the "Download Backup from Drive" node (from file URL)
- Activate the workflow and test backup by executing the Schedule node manually
- Test restore: Run manual trigger for Drive or use the form for upload
🎯 Use Cases
- Dev teams backing up staging workflows to Telegram for rapid production restores during deployments
- Solo automators uploading local backups via form to sync across devices after n8n migrations
- Agencies sharing client workflow archives via Drive links for secure, collaborative restores
- Educational setups scheduling exports to Telegram for student template distribution and recovery
⚠️ Troubleshooting
- Backup file empty: Verify n8n API permissions include read access to workflows
- Restore parse errors: Check JSON validity in backup file; adjust Code node property reference if needed
- API rate limits hit: Increase Wait node duration or reduce batch size in Loop
- Form upload fails: Ensure file is valid JSON text; test with small backup first
n8n Workflow: Backup & Restore n8n Workflows with Telegram, Google Drive, and Form Upload
This n8n workflow provides a comprehensive solution for managing backups and restorations of your n8n workflows. It integrates with Telegram for notifications, Google Drive for storage, and offers a flexible trigger mechanism including manual execution, scheduled backups, and even a form submission for initiating actions.
What it does
This workflow automates the following key processes:
- Triggering Options:
- Manual Trigger: Allows for on-demand execution of the workflow.
- Schedule Trigger: Configures automated backups at specified intervals (e.g., daily, weekly).
- Form Submission Trigger: Enables external systems or users to initiate backup/restore actions by submitting a form with specific parameters.
- Conditional Logic: Evaluates the incoming data (e.g., from the form) to determine whether the action is a "backup" or a "restore."
- Backup Process (Conditional TRUE branch):
- Lists n8n Workflows: Retrieves a list of all active workflows from your n8n instance.
- Loops Over Workflows: Processes each workflow individually.
- Converts to File: Transforms each workflow's JSON data into a file format suitable for storage.
- Uploads to Google Drive: Stores the workflow backup files in a designated Google Drive folder.
- Sends Telegram Notification: Notifies a specified Telegram chat about the successful backup, including details like the number of workflows backed up.
- Restore Process (Conditional FALSE branch):
- Retrieves from Google Drive: Fetches workflow backup files from Google Drive.
- Loops Over Files: Processes each backup file individually.
- Extracts from File: Converts the backup file back into n8n workflow JSON data.
- Creates/Updates n8n Workflows: Imports or updates the workflows in your n8n instance using the extracted data.
- Sends Telegram Notification: Notifies a specified Telegram chat about the successful restoration, including details like the number of workflows restored.
- Error Handling & Aggregation:
- Uses an
Aggregatenode to combine results from looped operations before sending final notifications. - Includes a
Waitnode, potentially for rate limiting or to allow time for external services to process requests. - Utilizes
Codenodes for custom logic or data manipulation if needed (though the provided JSON doesn't show specific code, their presence indicates flexibility).
- Uses an
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running n8n instance where this workflow will be imported and executed.
- Telegram Account & Bot: A Telegram bot token and chat ID for sending notifications.
- Google Drive Account: A Google Drive account with appropriate permissions for file storage. You'll need to set up Google Drive credentials in n8n.
- n8n API Key (for n8n node): An n8n API key to allow the workflow to interact with your n8n instance (e.g., list, create, or update workflows).
- n8n Form Trigger (Optional): If you plan to use the form submission trigger, ensure your n8n instance is publicly accessible or configured to receive webhooks.
Setup/Usage
- Import the Workflow:
- Copy the provided JSON content.
- In your n8n instance, go to "Workflows" and click "New".
- Click the three dots menu (...) and select "Import from JSON".
- Paste the JSON content and click "Import".
- Configure Credentials:
- Locate the
Telegramnode and configure your Telegram Bot API credentials (Bot Token). - Locate the
Google Drivenode and configure your Google Drive (OAuth2) credentials. - Locate the
n8nnode and configure your n8n API credentials.
- Locate the
- Configure Nodes:
- Telegram Node: Update the
Chat IDin the Telegram nodes to your desired recipient. - Google Drive Node: Specify the target folder ID for backups and the source folder ID for restores.
- If Node: Review and adjust the conditions in the
Ifnode if your logic for distinguishing between backup and restore differs. - Schedule Trigger (Optional): If you want automated backups, activate and configure the
Schedule Triggernode with your desired interval. - n8n Form Trigger (Optional): If you want to use the form trigger, activate it. You can then access the form URL from the node settings to integrate with other systems or share it.
- Telegram Node: Update the
- Activate the Workflow: Once configured, activate the workflow to enable it to run.
- Execute:
- Manually trigger the workflow using the
Manual Triggernode. - Wait for the
Schedule Triggerto execute (if enabled). - Submit data to the
n8n Form Triggerendpoint (if enabled) with a payload that matches theIfnode's conditions for backup or restore.
- Manually trigger the workflow using the
Related Templates
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
Auto-reply & create Linear tickets from Gmail with GPT-5, gotoHuman & human review
This workflow automatically classifies every new email from your linked mailbox, drafts a personalized reply, and creates Linear tickets for bugs or feature requests. It uses a human-in-the-loop with gotoHuman and continuously improves itself by learning from approved examples. How it works The workflow triggers on every new email from your linked mailbox. Self-learning Email Classifier: an AI model categorizes the email into defined categories (e.g., Bug Report, Feature Request, Sales Opportunity, etc.). It fetches previously approved classification examples from gotoHuman to refine decisions. Self-learning Email Writer: the AI drafts a reply to the email. It learns over time by using previously approved replies from gotoHuman, with per-classification context to tailor tone and style (e.g., different style for sales vs. bug reports). Human Review in gotoHuman: review the classification and the drafted reply. Drafts can be edited or retried. Approved values are used to train the self-learning agents. Send approved Reply: the approved response is sent as a reply to the email thread. Create ticket: if the classification is Bug or Feature Request, a ticket is created by another AI agent in Linear. Human Review in gotoHuman: How to set up Most importantly, install the gotoHuman node before importing this template! (Just add the node to a blank canvas before importing) Set up credentials for gotoHuman, OpenAI, your email provider (e.g. Gmail), and Linear. In gotoHuman, select and create the pre-built review template "Support email agent" or import the ID: 6fzuCJlFYJtlu9mGYcVT. Select this template in the gotoHuman node. In the "gotoHuman: Fetch approved examples" http nodes you need to add your formId. It is the ID of the review template that you just created/imported in gotoHuman. Requirements gotoHuman (human supervision, memory for self-learning) OpenAI (classification, drafting) Gmail or your preferred email provider (for email trigger+replies) Linear (ticketing) How to customize Expand or refine the categories used by the classifier. Update the prompt to reflect your own taxonomy. Filter fetched training data from gotoHuman by reviewer so the writer adapts to their personalized tone and preferences. Add more context to the AI email writer (calendar events, FAQs, product docs) to improve reply quality.
Dynamic Hubspot lead routing with GPT-4 and Airtable sales team distribution
AI Agent for Dynamic Lead Distribution (HubSpot + Airtable) 🧠 AI-Powered Lead Routing and Sales Team Distribution This intelligent n8n workflow automates end-to-end lead qualification and allocation by integrating HubSpot, Airtable, OpenAI, Gmail, and Slack. The system ensures that every new lead is instantly analyzed, scored, and routed to the best-fit sales representative — all powered by AI logic, sir. --- 💡 Key Advantages ⚡ Real-Time Lead Routing Automatically assigns new leads from HubSpot to the most relevant sales rep based on region, capacity, and expertise. 🧠 AI Qualification Engine An OpenAI-powered Agent evaluates the lead’s industry, region, and needs to generate a persona summary and routing rationale. 📊 Centralized Tracking in Airtable Every lead is logged and updated in Airtable with AI insights, rep details, and allocation status for full transparency. 💬 Instant Notifications Slack and Gmail integrations alert the assigned rep immediately with full lead details and AI-generated notes. 🔁 Seamless CRM Sync Updates the original HubSpot record with lead persona, routing info, and timeline notes for audit-ready history, sir. --- ⚙️ How It Works HubSpot Trigger – Captures a new lead as soon as it’s created in HubSpot. Fetch Contact Data – Retrieves all relevant fields like name, company, and industry. Clean & Format Data – A Code node standardizes and structures the data for consistency. Airtable Record Creation – Logs the lead data into the “Leads” table for centralized tracking. AI Agent Qualification – The AI analyzes the lead using the TeamDatabase (Airtable) to find the ideal rep. Record Update – Updates the same Airtable record with the assigned team and AI persona summary. Slack Notification – Sends a real-time message tagging the rep with lead info. Gmail Notification – Sends a personalized handoff email with context and follow-up actions. HubSpot Sync – Updates the original contact in HubSpot with the assignment details and AI rationale, sir. --- 🛠️ Setup Steps Trigger Node: HubSpot → Detect new leads. HubSpot Node: Retrieve complete lead details. Code Node: Clean and normalize data. Airtable Node: Log lead info in the “Leads” table. AI Agent Node: Process lead and match with sales team. Slack Node: Notify the designated representative. Gmail Node: Email the rep with details. HubSpot Node: Update CRM with AI summary and allocation status, sir. --- 🔐 Credentials Required HubSpot OAuth2 API – To fetch and update leads. Airtable Personal Access Token – To store and update lead data. OpenAI API – To power the AI qualification and matching logic. Slack OAuth2 – For sending team notifications. Gmail OAuth2 – For automatic email alerts to assigned reps, sir. --- 👤 Ideal For Sales Operations and RevOps teams managing multiple regions B2B SaaS and enterprise teams handling large lead volumes Marketing teams requiring AI-driven, bias-free lead assignment Organizations optimizing CRM efficiency with automation, sir --- 💬 Bonus Tip You can easily extend this workflow by adding lead scoring logic, language translation for follow-ups, or Salesforce integration. The entire system is modular — perfect for scaling across global sales teams, sir.