HumationHuman + Automation
Back to Catalog

Bilibili video downloader with Google Drive upload & email notification

Sk developer Sk developer
413 views
2/3/2026
Google Cloud StorageStorageCloudFileMove
Official Page

Bilibili Video Downloader with Google Drive Upload & Email Notification

Automate downloading of Bilibili videos via the Bilibili Video Downloader API (RapidAPI), upload them to Google Drive, and notify users by email — all using n8n workflow automation.

🧠 Workflow Overview

This n8n automation allows users to:

  1. Submit a Bilibili video URL.
  2. Fetch download info from the Bilibili Video Downloader API (RapidAPI).
  3. Automatically download and upload the video to Google Drive.
  4. Share the file and send an email notification to the user.

⚙️ Node-by-Node Explanation

| Node | Function | | ---------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | | On form submission | Triggers when a user submits the Bilibili video URL through the form. | | Fetch Bilibili Video Info from API | Sends the video URL to the Bilibili Video Downloader API (RapidAPI) to retrieve download info. | | Check API Response Status | Validates that the API returned a 200 success status before proceeding. | | Download Video File | Downloads the actual video from the provided resource URL. | | Upload Video to Google Drive | Uploads the downloaded video file to the user’s connected Google Drive. | | Google Drive Set Permission | Sets sharing permissions to make the uploaded video publicly accessible. | | Success Notification Email with Drive Link | Sends the Google Drive link to the user via email upon successful upload. | | Processing Delay | Adds a delay before executing error handling if something fails. | | Failure Notification Email | Sends an error notification to the user if download/upload fails. |

🧩 How to Configure Google Drive in n8n

  1. In n8n, open Credentials → New → Google Drive.
  2. Choose OAuth2 authentication.
  3. Follow the on-screen instructions to connect your Google account.
  4. Use the newly created credential in both Upload Video and Set Permission nodes.
  5. Test the connection to ensure access to your Drive.

🔑 How to Obtain Your RapidAPI Key

To use the Bilibili Video Downloader API (RapidAPI):

  1. Visit bilibili videodownloade.
  2. Click Subscribe to Test (you can choose free or paid plans).
  3. Copy your x-rapidapi-key from the “Endpoints” section.
  4. Paste the key into your n8n Fetch Bilibili Video Info from API node header.

Example header:

{
  "x-rapidapi-host": "bilibili-video-downloader.p.rapidapi.com",
  "x-rapidapi-key": "your-rapidapi-key-here"
}

💡 Use Case

This automation is ideal for:

  • Content creators archiving Bilibili videos.
  • Researchers collecting media resources.
  • Teams that need centralized video storage in Google Drive.
  • Automated content management workflows.

🚀 Benefits

✅ No manual downloads – fully automated. ✅ Secure cloud storage via Google Drive. ✅ Instant user notification on success or failure. ✅ Scalable for multiple users or URLs. ✅ Powered by the reliable Bilibili Video Downloader API (RapidAPI).

👥 Who Is This For

  • n8n developers wanting to explore advanced workflow automations.
  • Content managers handling large volumes of Bilibili content.
  • Digital archivists storing video data in Google Drive.
  • Educators sharing Bilibili educational videos securely.

🏁 Summary

With this n8n workflow, you can seamlessly integrate the Bilibili Video Downloader API (RapidAPI) into your automation stack — enabling effortless video downloading, Google Drive uploading, and user notifications in one unified system.

n8n Bilibili Video Downloader with Google Drive Upload & Email Notification

This n8n workflow automates the process of downloading Bilibili videos, uploading them to Google Drive, and sending an email notification upon completion or failure. It is triggered by a form submission, making it easy to request video downloads.

What it does

  1. Triggers on Form Submission: The workflow starts when a user submits a form, likely containing the Bilibili video URL.
  2. Initiates Video Download: It sends an HTTP request to an external service (presumably a Bilibili downloader API) to start the video download process.
  3. Waits for Completion: The workflow then pauses for a specified duration to allow the download to complete.
  4. Checks Download Status: After the wait, it makes another HTTP request to check the status of the video download.
  5. Conditional Logic: It uses an "If" node to check if the download was successful.
    • On Success: If the download is successful, it proceeds to upload the video to Google Drive.
    • On Failure: If the download fails, it sends an email notification about the failure.
  6. Uploads to Google Drive: If the download was successful, the workflow uploads the downloaded video file to a specified folder in Google Drive.
  7. Sends Email Notification:
    • Success: After successfully uploading to Google Drive, it sends an email notification confirming the download and upload, potentially including a link to the Google Drive file.
    • Failure: If any step fails (e.g., download failure, Google Drive upload failure), it sends an email notification detailing the error.

Prerequisites/Requirements

  • n8n Instance: A running instance of n8n.
  • External Bilibili Downloader API: An accessible API endpoint for downloading Bilibili videos. This is represented by the "HTTP Request" nodes. You will need to configure the URLs and any necessary authentication for this service.
  • Google Drive Account: A Google account with Google Drive enabled and appropriate permissions for n8n to upload files.
  • Google Drive Credentials: OAuth2 credentials configured in n8n for Google Drive.
  • SMTP Server/Email Service: An SMTP server or email service configured in n8n to send email notifications.
  • Email Credentials: Credentials for your email service configured in n8n.

Setup/Usage

  1. Import the Workflow:
    • Download the provided JSON file.
    • In your n8n instance, go to "Workflows" and click "New".
    • Click the "Import from JSON" button and paste the workflow JSON or upload the file.
  2. Configure Credentials:
    • Google Drive: Create or select an existing Google Drive OAuth2 credential. Ensure it has access to create and upload files.
    • Send Email: Create or select an existing "Send Email" (SMTP) credential.
  3. Configure Nodes:
    • On form submission (Trigger): This node will generate a webhook URL. Share this URL or embed the form to trigger the workflow.
    • HTTP Request (Download Video): Update the URL, method, headers, and body to interact with your Bilibili downloader API. You'll likely need to extract the video URL from the incoming form data.
    • Wait: Adjust the "Wait Time" as needed based on how long your video downloads typically take.
    • HTTP Request (Check Status): Update the URL and parameters to query the status of the download from your Bilibili downloader API.
    • If: Review the conditions in the "If" node to correctly evaluate the success or failure of the download based on the response from your status check API.
    • Google Drive (Upload File):
      • Specify the "Folder ID" where you want the videos to be uploaded.
      • Ensure the "File Content" and "File Name" expressions correctly reference the output of your download process.
    • Send Email:
      • Configure the "To" email address for notifications.
      • Customize the "Subject" and "Body" of the success and failure emails to include relevant information (e.g., video title, download status, Google Drive link, error messages).
  4. Activate the Workflow: Once all configurations are complete, activate the workflow by toggling the "Active" switch in the top right corner of the n8n editor.

Now, whenever the form is submitted, the workflow will execute, attempting to download the Bilibili video, upload it to Google Drive, and send you an email notification.

Related Templates

Analyze call recordings with OpenAI and update Zoho CRM leads automatically

Zoho CRM - Conversation Intelligence Analyzer This workflow automatically processes customer call recordings, transcribes them using OpenAI Whisper, extracts key topics, identifies commitments, analyzes sentiment, generates follow-up suggestions and updates the corresponding Zoho CRM Lead — all without manual efforts. It eliminates the need for listening to calls or writing summaries and equips your sales team with instant AI-generated insights. ⚡ Quick Start (Fast Setup) Import the workflow JSON into n8n. Add Zoho CRM OAuth2 & OpenAI API credentials. Copy the webhook URL and configure your telephony system to POST call recordings. Map Zoho custom fields. Upload a test recording → Confirm CRM updates → Activate workflow. 📘 What It Does This workflow turns every incoming call recording into structured insights which your sales & customer support team can immediately use. When a recording is received, the call is automatically transcribed using OpenAI’s Whisper model. That transcript is then processed by multiple AI nodes that detect topics, customer sentiment, commitments and possible follow-up actions. All extracted data — such as mood, sentiment score, subjects, action items and commitments is merged into a clean result object and pushed to the matching Lead in Zoho CRM. The sales team gets ready-to-use call intelligence instantly, improving decision-making, accuracy and speed. This automation works 24/7 and replaces hours of manual review work with reliable AI-generated summaries. 👤 Who’s It For Sales & Customer support teams using Zoho CRM. Support teams handling inbound/outbound calls. Businesses wanting call analytics without manual transcription. Zoho CRM admins who want automation with minimal maintenance. Organizations using telephony/VoIP systems that support call exports. 🧾 Requirements To use this workflow, you need: An n8n instance (self-hosted or cloud) Zoho CRM OAuth2 credentials OpenAI API key (Whisper + GPT models) A telephony system capable of POSTing audio files to a webhook Zoho fields to store: Topics Main subject Action items Sentiment Mood Follow-up text Commitments (optional) ⚙️ How It Works & How to Set Up Webhook Trigger Your call system sends an audio file (.mp3, .wav, etc.) to the webhook. The workflow starts instantly—no polling required. Workflow Configuration Static values like: sentimentThreshold = 0.7 minCommitmentConfidence = 0.8 ensure consistent logic across nodes. Audio Transcription (OpenAI Whisper) The audio file is converted to text. This transcript becomes the base for all analysis nodes. Key Topic Extraction AI identifies: Key topics Main subject Important action items Sentiment & Mood Analysis AI analyzes: Customer mood Sales rep tone Overall sentiment Sentiment score Commitment Extraction AI detects commitments using a structured JSON schema. Follow-up Generation GPT generates 3–5 follow-up suggestions based on the transcript & commitments. Combine All Insights A Set node merges transcription, topics, sentiment, commitments and follow-up text. Update Zoho CRM Lead Updates Zoho custom fields so the sales team gets immediate insights. 🛠 How to Customize Nodes Transcription Node Switch to another Whisper/GPT model Add language options Topic Extraction Add more attributes (risks, objections, intent) Sentiment Analysis Tune thresholds Add more emotion labels Commitment Extraction Modify schema Add filtering logic CRM Update Map to different fields Append notes instead of overwriting ➕ Add-Ons (Optional Enhancements) Slack/Teams alerts for negative sentiment Email transcripts to teams Save files to Google Drive / S3 Create Zoho tasks from commitments Multi-language transcription Sales rep performance scoring 💼 Use Case Examples Sales Call Analysis – Auto-summarize calls for follow-up. Support Hotline Monitoring – Detect customer frustration. QA Audits – Auto-generate evaluation notes. Voice-to-CRM Logging – Store conversation data automatically. Compliance Tracking – Capture legally relevant commitments. 🛠 Troubleshooting Guide | Issue | Possible Cause | Solution | |------|----------------|----------| | Workflow not triggered | Telephony not hitting webhook | Recheck webhook URL & logs | | Transcript empty | Unsupported/corrupted audio | Validate file before sending | | CRM not updating | Wrong Zoho field IDs | Verify field IDs in Zoho | | Commitments missing | Transcript unclear | Improve audio quality or edit schema | | Sentiment inaccurate | Model interpretation | Adjust sentimentThreshold | 🤝 Need Help? If you want to customize this workflow, integrate telephony systems or want to build advanced level CRM automation, then our n8n workflow development team at WeblineIndia team is happy to help. We’re here to support setup, scaling, and custom enhancements.

WeblineIndiaBy WeblineIndia
259

Voice AI chatbot with OpenAI, RAG (Qdrant) & Guardrails for WordPress

This workflow implements a complete Voice AI Chatbot system for Wordress that integrates speech recognition, guardrails for safety, retrieval-augmented generation (RAG), Qdrant vector search, and audio responses. It is designed to be connected to a WordPress Voicebot AI plugin through a webhook endpoint. --- Key Advantages ✅ Complete Voice AI Pipeline* The workflow handles: audio input STT intelligent processing TTS output All within a single automated process. ✅ Safe and Policy-Compliant Thanks to the Guardrails module, the system automatically: detects harmful or disallowed requests blocks them responds safely This protects both the user and the business. ✅ Contextual and Memory-Based Conversations The Window Buffer Memory tied to unique session IDs enables: continuous conversation flow natural dialogue better understanding of context ✅ Company-Specific Knowledge via RAG By integrating Qdrant as a vector store, the system can: retrieve business documentation give accurate and up-to-date answers support personalized content This makes the chatbot far more powerful than a standard LLM. ✅ Modular and Extensible Architecture Because everything is modular inside n8n, you can: swap OpenAI with other models add new tools or knowledge sources change prompts or capabilities without redesigning the entire workflow. ✅ *Easy WordPress Integration The workflow connects directly to a WordPress Voicebot plugin, meaning: no custom backend development simple deployment fast integration for websites ✅ Automatic Indexing of Documents The second workflow section: fetches Google Drive files converts them into embeddings indexes them into Qdrant This lets you maintain your knowledge base with almost no manual work. --- How It Works This workflow creates a Wordpress voice-enabled AI chatbot that processes audio inputs and provides contextual responses using RAG (Retrieval-Augmented Generation) from a Qdrant vector database. The system operates as follows: Audio Processing Pipeline: Receives audio input via webhook and converts speech to text using OpenAI's STT (Speech-to-Text) Applies guardrails to detect inappropriate content or jailbreak attempts using a separate GPT-4.1-mini model Routes safe queries to the AI agent and blocks unsafe content with a default response AI Agent with Contextual Memory: Uses OpenAI Chat Model with window buffer memory to maintain conversation context Equips the agent with two tools: Calculator for computations and RAG tool for business knowledge retrieval The RAG system queries Qdrant vector store containing company documents using OpenAI embeddings Response Generation: Generates appropriate text responses based on query type and available knowledge Converts approved responses to audio using OpenAI's TTS (Text-to-Speech) with "onyx" voice Returns binary audio responses to the webhook caller --- Set Up Steps Vector Database Preparation: Create Qdrant collection via HTTP request with specified vector configuration Clear existing collection data before adding new documents Set up Google Drive integration to source documents from specific folders Document Processing Pipeline: Search and retrieve files from Google Drive folder "Test Negozio" Process documents through recursive text splitting (500 chunk size, 50 overlap) Generate embeddings using OpenAI and store in Qdrant vector store Implement batch processing with 5-second delays between operations System Configuration: Configure webhook endpoint for receiving audio inputs Set up multiple OpenAI accounts for different functions (STT, TTS, guardrails, main agent) Establish Qdrant API connections for vector storage and retrieval Implement session-based memory management using session IDs from webhook headers WordPress Integration: Install the provided Voicebot AI Agent WordPress plugin Configure the plugin with the webhook URL to connect to this n8n workflow The system is now ready to receive audio queries and respond with voice answers The workflow handles both real-time voice queries and background document processing, creating a comprehensive voice assistant solution with business-specific knowledge retrieval capabilities. --- Need help customizing? Contact me for consulting and support or add me on Linkedin.

DavideBy Davide
706

Write HTTP query string on image

Receives data from an incoming HTTP Request Reads file from internet Writes data on image Returns the data The URL to call will look like this: http://localhost:5678/webhook-test/webhook/test?name=Jim Once called it will return an image like this:

Jan OberhauserBy Jan Oberhauser
4819