Back to Catalog

Automatic Notion database backup to Google Drive with Telegram notifications

PruebaPrueba
61 views
2/3/2026
Official Page

πŸ” Workflow Overview

What This Workflow Does

This workflow automatically saves copies of all your Notion databases to Google Drive. It's like creating a safety backup of your important Notion information, similar to saving important documents in a filing cabinet.

Target Audience: Anyone who uses Notion and wants to protect their data by creating automatic backups to Google Drive.


Prerequisites (What You Need Before Starting)

Required Accounts

  1. Notion Account - Where your databases are stored
  2. Google Account - For Google Drive storage
  3. Telegram Account - To receive backup notifications (free messaging app)

Required Software

  • n8n Community Edition v2.0.0 installed on your computer or server
  • Web browser (Chrome, Firefox, Safari, or Edge)

Step-by-Step Configuration Guide

PART 1: Setting Up Notion Access

Step 1: Create a Notion Integration

Step 2: Share Your Databases with the integration


PART 2: Setting Up Google Drive Access

Step 1: Create a Google Drive Folder

Step 2: Connect Google Drive to n8n


PART 3: Setting Up Telegram Notifications

Step 1: Create a Telegram Bot

Step 2: Get Your Chat ID

Step 3: Connect Telegram to n8n


PART 4: Installing the Workflow in n8n

Step 1: Import the Workflow

Step 2: Configure Credentials

  1. For Notion nodes (Get All Databases, Get Database Pages)
  2. For Google Drive nodes (Create Backup Folder, Upload Backup File, etc.)
  3. For Telegram node (Send Telegram Notification)

Step 3: Configure the Workflow Settings


PART 5: Testing Your Workflow

Step 1: Run a Test

Step 2: Verify the Backup

If Something Goes Wrong

  • Red X marks on nodes: Check that all credentials are properly connected
  • "Not found" errors: Make sure you shared your Notion databases with the integration
  • No Telegram message: Verify your Chat ID is correct
  • No files in Google Drive: Check your Folder ID is correct

Automatic Notion Database Backup to Google Drive with Telegram Notifications

This n8n workflow automates the process of backing up a Notion database to Google Drive and sends a notification to Telegram upon completion. It provides a robust solution for ensuring your Notion data is regularly saved off-platform and keeps you informed about the backup status.

What it does

  1. Manually Triggered: The workflow is initiated manually, allowing you to run the backup on demand.
  2. Notion Database Query: It queries a specified Notion database to retrieve all its items.
  3. Process Notion Items: Each item from the Notion database is processed individually.
  4. Transform Data: The retrieved Notion data is transformed and prepared for storage.
  5. Upload to Google Drive: The processed data is then uploaded as a file to a designated folder in Google Drive.
  6. Conditional Success Notification: If the Google Drive upload is successful, a success message is sent to a Telegram chat.
  7. Conditional Failure Notification: If any step in the Google Drive upload or data processing fails, an error notification is sent to a Telegram chat.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance.
  • Notion Account: Access to a Notion workspace with a database you wish to back up.
    • You'll need to create a Notion integration and grant it access to your database.
    • An internal integration token will be required for n8n credentials.
  • Google Drive Account: A Google Drive account where the backups will be stored.
    • You'll need to set up Google Drive credentials in n8n (OAuth2 recommended).
  • Telegram Account: A Telegram account to receive notifications.
    • You'll need a Telegram Bot token and the chat ID where you want to receive messages.

Setup/Usage

  1. Import the Workflow:
    • Download the provided JSON file.
    • In your n8n instance, click "Workflows" in the left sidebar.
    • Click "New" -> "Import from JSON" and paste the workflow JSON or upload the file.
  2. Configure Credentials:
    • Notion: Edit the "Notion" node. Select or create a new Notion API credential. You will need your Notion integration token.
    • Google Drive: Edit the "Google Drive" node. Select or create a new Google Drive OAuth2 credential. Follow the n8n documentation for setting up Google Drive OAuth2.
    • Telegram: Edit the "Telegram" node. Select or create a new Telegram API credential. You will need your Bot Token and the Chat ID.
  3. Customize Nodes:
    • Notion Node:
      • Specify the Database ID of the Notion database you want to back up.
      • Adjust any other query parameters if needed (e.g., filters, sorts).
    • Edit Fields (Set) Node: This node is currently empty. You might want to add fields here to format or select specific data from Notion before saving it to Google Drive. For example, to convert the Notion items into a CSV or JSON string.
    • Google Drive Node:
      • Set the Operation to "Upload".
      • Specify the Folder ID where you want to save the backup files.
      • Define the File Name for the backup. You can use expressions to include timestamps or other dynamic data (e.g., {{ $now().toFormat('yyyy-MM-dd_HH-mm-ss') }}_notion_backup.json).
      • Ensure the Binary Data field points to the output of the "Edit Fields" node, formatted as a file.
    • Telegram Nodes:
      • Update the Chat ID in both "Telegram" nodes (for success and failure) to your desired Telegram chat ID.
      • Customize the success and error messages as needed.
  4. Activate the Workflow: Once configured, activate the workflow by toggling the "Active" switch in the top right corner of the workflow editor.
  5. Execute Manually: Click the "Execute Workflow" button to run the backup process.

This workflow provides a solid foundation for your Notion database backups. You can extend it further by adding:

  • Scheduled Trigger: Replace the "Manual Trigger" with a "Cron" node to run backups on a schedule (e.g., daily, weekly).
  • Error Handling: Implement more sophisticated error handling, such as retries or detailed logging.
  • Data Formatting: Use the "Code" or "Edit Fields" node to format the Notion data into a specific file type (e.g., CSV, JSON, Markdown) before uploading to Google Drive.

Related Templates

Send WooCommerce cross-sell offers to customers via WhatsApp using Rapiwa API

Who Is This For? This n8n workflow enables automated cross-selling by identifying each WooCommerce customer's most frequently purchased product, finding a related product to recommend, and sending a personalized WhatsApp message using the Rapiwa API. It also verifies whether the user's number is WhatsApp-enabled before sending, and logs both successful and unsuccessful attempts to Google Sheets for tracking. What This Workflow Does Retrieves all paying customers from your WooCommerce store Identifies each customer's most purchased product Finds the latest product in the same category as their most purchased item Cleans and verifies customer phone numbers for WhatsApp compatibility Sends personalized WhatsApp messages with product recommendations Logs all activities to Google Sheets for tracking and analysis Handles both verified and unverified numbers appropriately Key Features Customer Segmentation: Automatically identifies paying customers from your WooCommerce store Product Analysis: Determines each customer's most purchased product Smart Recommendations: Finds the latest products in the same category as customer favorites WhatsApp Integration: Uses Rapiwa API for message delivery Phone Number Validation: Verifies WhatsApp numbers before sending messages Dual Logging System: Tracks both successful and failed message attempts in Google Sheets Rate Limiting: Uses batching and wait nodes to prevent API overload Personalized Messaging: Includes customer name and product details in messages Requirements 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) How to Use β€” Step-by-Step Setup Credentials Setup WooCommerce API: Configure WooCommerce API credentials in n8n (e.g., "WooCommerce (get customer)" and "WooCommerce (get customer data)") Rapiwa Bearer Auth: Create an HTTP Bearer credential with your Rapiwa API token Google Sheets OAuth2: Set up OAuth2 credentials for Google Sheets access Configure Google Sheets Ensure your sheet has the required columns as specified in the Google Sheet Column Structure section Verify Code Nodes Code (get paying_customer): Filters customers to include only those who have made purchases Get most buy product id & Clear Number: Identifies the most purchased product and cleans phone numbers Configure HTTP Request Nodes Get customer data: Verify the WooCommerce API endpoint for retrieving customer orders Get specific product data: Verify the WooCommerce API endpoint for product details Get specific product recommend latest product: Verify the WooCommerce API endpoint for finding latest products by category Check valid WhatsApp number Using Rapiwa: Verify the Rapiwa endpoint for WhatsApp number validation Rapiwa Sender: Verify the Rapiwa endpoint for sending messages Google Sheet Required Columns You’ll need two Google Sheets (or two tabs in one spreadsheet): A Google Sheet formatted like this ➀ sample The workflow uses a Google Sheet with the following columns to track coupon distribution: Both must have the following headers (match exactly): | name | number | email | address1 | price | suk | title | product link | validity | staus | | ---------- | ------------- | ----------------------------------------------- | ----------- | ----- | --- | ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------- | -------- | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | unverified | not sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | 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. Product Availability: The workflow recommends the latest product in a category, but doesn't check if it's in stock. Consider adding stock status verification. Testing: Always test with a small batch before running the workflow on your entire customer list. 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

RapiwaBy Rapiwa
183

Track SDK documentation drift with GitHub, Notion, Google Sheets, and Slack

πŸ“Š Description Automatically track SDK releases from GitHub, compare documentation freshness in Notion, and send Slack alerts when docs lag behind. This workflow ensures documentation stays in sync with releases, improves visibility, and reduces version drift across teams. πŸš€πŸ“šπŸ’¬ What This Template Does Step 1: Listens to GitHub repository events to detect new SDK releases. 🧩 Step 2: Fetches release metadata including version, tag, and publish date. πŸ“¦ Step 3: Logs release data into Google Sheets for record-keeping and analysis. πŸ“Š Step 4: Retrieves FAQ or documentation data from Notion. πŸ“š Step 5: Merges GitHub and Notion data to calculate documentation drift. πŸ” Step 6: Flags SDKs whose documentation is over 30 days out of date. ⚠️ Step 7: Sends detailed Slack alerts to notify responsible teams. πŸ”” Key Benefits βœ… Keeps SDK documentation aligned with product releases βœ… Prevents outdated information from reaching users βœ… Provides centralized release tracking in Google Sheets βœ… Sends real-time Slack alerts for overdue updates βœ… Strengthens DevRel and developer experience operations Features GitHub release trigger for real-time monitoring Google Sheets logging for tracking and auditing Notion database integration for documentation comparison Automated drift calculation (days since last update) Slack notifications for overdue documentation Requirements GitHub OAuth2 credentials Notion API credentials Google Sheets OAuth2 credentials Slack Bot token with chat:write permissions Target Audience Developer Relations (DevRel) and SDK engineering teams Product documentation and technical writing teams Project managers tracking SDK and doc release parity Step-by-Step Setup Instructions Connect your GitHub account and select your SDK repository. Replace YOURGOOGLESHEETID and YOURSHEET_GID with your tracking spreadsheet. Add your Notion FAQ database ID. Configure your Slack channel ID for alerts. Run once manually to validate setup, then enable automation.

Rahul JoshiBy Rahul Joshi
31

Automate Gmail responses with GPT and human-in-the-loop verification

Try It Out! This n8n template uses AI to automatically respond to your Gmail inbox by drafting response for your approval via email. How it works Gmail Trigger monitors your inbox for new emails AI Analysis determines if a response is needed based on your criteria Draft Generation creates contextually appropriate replies using your business information Human Approval sends you the draft for review before sending Auto-Send replies automatically once approved Setup Connect your Gmail account to the Gmail Trigger node Update the "Your Information" node with: Entity name and description Approval email address Resource guide (FAQs, policies, key info) Response guidelines (tone, style, formatting preferences) Configure your LLM provider (OpenAI, Claude, Gemini, etc.) with API credentials Test with a sample email Requirements n8n instance (self-hosted or cloud) Gmail account with API access LLM provider API key Need Help? Email Nick @ nick@tropicflare.com

Nick CanfieldBy Nick Canfield
88