Description
Overview
This video notification automation workflow enables periodic detection and alerting of newly uploaded videos from a specific YouTube channel. Using an event-driven analysis pipeline, it reliably identifies fresh content and delivers timely notifications to a Telegram chat every 30 minutes.
Designed for content managers and community moderators, it streamlines the task of monitoring YouTube feeds by leveraging a scheduled interval trigger and OAuth2 authenticated API calls to fetch video metadata.
Key Benefits
- Automates video discovery every 30 minutes using a precise scheduling interval workflow.
- Filters out previously notified content to ensure only new videos trigger alerts.
- Extracts essential video data (ID, title, URL) for focused message content in notifications.
- Integrates YouTube API and Telegram bot for seamless cross-platform communication.
Product Overview
This automation workflow initiates via a time-based interval node that triggers every 30 minutes. Upon activation, it calls the YouTube API to fetch the latest four videos from a predefined channel using OAuth2 authentication. The workflow processes the API response by extracting key metadata fields—video ID, title, and a constructed short URL—then filters out videos already processed in prior runs by maintaining static workflow data of known IDs.
New videos identified are formatted into HTML messages and dispatched to a specified Telegram chat using bot credentials. The workflow operates synchronously on each trigger, with no explicit error handling nodes configured, thereby relying on platform-level defaults for retries or failures. No persistent data storage outside the workflow’s static scope is involved, ensuring transient data handling specific to each execution cycle.
Features and Outcomes
Core Automation
This event-driven analysis pipeline takes input from a scheduled interval trigger, applying deterministic filtering logic within a function node to isolate only new video entries. The decision criteria involve comparing incoming video IDs with stored ones to avoid duplicates.
- Single-pass evaluation of incoming video lists for efficient uniqueness checks.
- Modular node structure enabling clear separation of data extraction and filtering logic.
- Deterministic branching halts processing upon detecting previously seen content.
Integrations and Intake
The workflow connects to YouTube via an OAuth2-authenticated API node, fetching video resource data filtered by channel ID and ordered by upload date. The intake expects a structured JSON payload containing video metadata fields including videoId and snippet title.
- YouTube API node for retrieving recent video uploads from a specific channel.
- Telegram bot node with API key credentials for dispatching formatted notifications.
- Interval trigger node ensures periodic polling without manual intervention.
Outputs and Consumption
Outputs consist of HTML-formatted messages sent synchronously to a Telegram chat. Each message includes a static prefix, the video title in bold, and a direct shortened URL to the video. The delivery is immediate per new video detected within each execution cycle.
- HTML messages with embedded video title and URL for Telegram consumption.
- Message dispatch occurs per new video detected, ensuring prompt notification.
- Output fields include video ID, title, and constructed YouTube short link.
Workflow — End-to-End Execution
Step 1: Trigger
The workflow initiates on a fixed interval schedule set to 30-minute increments. This interval node acts as a timer, triggering the entire pipeline at consistent, predictable times without external input.
Step 2: Processing
Following trigger, the YouTube node queries recent videos from the specified channel using OAuth2 credentials. The subsequent set node extracts and isolates the video ID, title, and short URL into a simplified data structure. Basic presence checks ensure required fields are present before forwarding.
Step 3: Analysis
The function node performs a filtering routine that compares each video ID against a static list of previously processed IDs stored within the workflow context. If a video ID is already present, processing halts for subsequent items. This ensures only new, unnotified videos proceed downstream.
Step 4: Delivery
For each new video identified, a Telegram node composes and sends a notification message to a designated chat. The message format uses HTML to bold the video title and includes the direct YouTube short URL. Delivery is synchronous per message, with no batch queuing configured.
Use Cases
Scenario 1
Content moderators need automated alerts for new videos on a specific YouTube channel. This no-code integration pipeline polls the channel every 30 minutes and sends formatted notifications to Telegram, eliminating manual monitoring and ensuring timely updates.
Scenario 2
Community managers require consistent announcements of fresh video content in their group chats. This workflow’s filtering logic prevents duplicate notifications, delivering only unshared videos with precise metadata for clear communication.
Scenario 3
Teams tracking influencer content want streamlined ingestion of new uploads into their messaging platform. The automation workflow integrates YouTube API data with Telegram notifications, providing a deterministic and repeatable process for real-time content awareness.
How to use
To deploy this video notification automation workflow, import it into the n8n environment and configure OAuth2 credentials for YouTube API access along with Telegram bot credentials. Set the targeted YouTube channel ID within the YouTube node parameters. Activate the workflow to run in live mode; it will then poll for new videos every 30 minutes and send notifications automatically. Expect output messages containing video titles and direct links formatted in HTML for Telegram consumption.
Comparison — Manual Process vs. Automation Workflow
| Attribute | Manual/Alternative | This Workflow |
|---|---|---|
| Steps required | Multiple manual checks, note-taking, and message posting | Single automated cycle every 30 minutes with no manual input |
| Consistency | Prone to missed updates or duplicate postings | Deterministic filtering ensures no duplicate notifications |
| Scalability | Limited by human monitoring capacity | Scales automatically with channel activity without added effort |
| Maintenance | Frequent oversight and manual adjustments required | Low maintenance; relies on stable API credentials and interval node |
Technical Specifications
| Environment | n8n automation platform |
|---|---|
| Tools / APIs | YouTube Data API (OAuth2), Telegram Bot API |
| Execution Model | Scheduled interval-triggered synchronous processing |
| Input Formats | JSON video metadata from YouTube API |
| Output Formats | HTML-formatted text messages to Telegram |
| Data Handling | Transient in-memory storage for ID tracking within workflow static data |
| Known Constraints | Relies on external API availability and credential validity |
| Credentials | OAuth2 for YouTube, API key for Telegram bot |
Implementation Requirements
- Valid OAuth2 credentials configured for YouTube API access.
- Telegram bot API key with permissions to send messages to the target chat.
- Network access allowing outbound connections to YouTube and Telegram APIs.
Configuration & Validation
- Verify OAuth2 authentication with YouTube API by testing video retrieval node.
- Confirm Telegram bot credentials by sending a test message to the designated chat.
- Run the workflow manually and monitor logs to ensure new videos trigger notifications correctly.
Data Provenance
- Trigger node: Interval node set at 30-minute intervals initiates execution.
- Data source: YouTube node retrieves video metadata filtered by channel ID “UCTe5YtigJdZZ3i-za6IkbGQ”.
- Output: Telegram node sends messages containing video title and URL using stored Telegram bot credentials.
FAQ
How is the video notification automation workflow triggered?
The workflow is triggered every 30 minutes by an interval node configured to initiate the process on a fixed schedule.
Which tools or models does the orchestration pipeline use?
The orchestration pipeline uses the YouTube Data API authenticated via OAuth2 to fetch video metadata and the Telegram Bot API to send notifications.
What does the response look like for client consumption?
Each new video generates an HTML-formatted message sent synchronously to a Telegram chat, including a bolded title and a direct short URL link.
Is any data persisted by the workflow?
The workflow maintains transient static data within the workflow context to track notified video IDs but does not persist data externally.
How are errors handled in this integration flow?
No explicit error handling nodes are configured; the workflow relies on n8n platform defaults for retries and failure management.
Conclusion
This video notification automation workflow provides a structured and deterministic method for detecting new YouTube uploads and delivering timely alerts to Telegram chats. By leveraging scheduled triggers, OAuth2 authentication, and in-workflow data filtering, it ensures consistent and duplicate-free notifications. A key constraint is its dependence on external YouTube and Telegram API availability and credential validity to maintain uninterrupted operation. The workflow offers a reliable, low-maintenance solution for real-time content update delivery without manual intervention.
Reviews
There are no reviews yet.