🎥 Gemini AI Video Analysis
Configured with HTTP Request, Wait. Review the connections and setup before adapting this template.
Node categories in this workflow
- Wait
- Web / API
- Trigger
- Transform
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| Wait | Wait | Wait | See node parameters |
| Download video | Web / API | HTTP Request | See node parameters |
| Upload video Gemini | Web / API | HTTP Request | POST |
| Analyze video Gemini | Web / API | HTTP Request | POST |
| When clicking ‘Test workflow’ | Trigger | Manual Trigger | See node parameters |
| Set Input | Transform | Edit Fields | See node parameters |
| Get Result | Transform | Edit Fields | See node parameters |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
None declared. HTTP requests and Code nodes may still need configuration.
Workflow notes
Video Analysis with Gemini AI
Video Analysis with Gemini AI
This workflow demonstrates how to analyze video content using Google's Gemini 2.0 Flash API:
- Download a video from a URL
- Upload it to Gemini's servers
- Process the video with AI to generate a detailed description
- Extract the analysis results
Use cases: Content moderation, video cataloging, accessibility features, etc.
OUTPUT: The workflow produces a detailed text description of the video content in the "MediaDescription" variable. You can use this data for content tagging, searchable descriptions, accessibility, moderation, or cataloging.
⚙️ Before using this workflow, make sure to set the GeminiKey environment variable with your Gemini API key.
This ensures your API key is securely managed and not hardcoded in the workflow.
SECURITY NOTE: This workflow contains an API key in the workflow data.
For production use, store your API keys in Credentials or use environment variables (like GeminiKey) instead of hardcoding them.
Configuration
Configuration
Define the video URL you want to analyze.
Video Processing Pipeline
Video Processing Pipeline
This section handles the complete video processing workflow:
-
DOWNLOAD: First, we fetch the video from the provided URL, converting it to binary data that Gemini can process
-
UPLOAD: Next, we send the binary video data to Gemini's servers where it's stored temporarily for AI processing
-
ANALYZE: Finally, we request Gemini's AI to analyze the video content. You can customize the prompt in the "Analyze video Gemini" node to focus on specific aspects of the video content you're interested in
The Wait node ensures the video is fully processed before analysis begins.
🎥 Gemini AI Video Analysis
🎥 Gemini AI Video Analysis
Purpose and structure
This folder contains the 🎥 Gemini AI Video Analysis workflow. Its executable nodes use httpRequest, manualTrigger, set, wait. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
When clicking ‘Test workflow’
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Http/1876_HTTP_Manual_Automation_Webhook.json MIT; preserve source notices.