YouTube Channel Advanced RSS Feed Generator - n8n Workflow

Content Curators and Researchers needing reliable, automated RSS feeds for tracking YouTube channels.
Automators seeking advanced n8n templates that solve complex external dependency issues (like bypassing mandatory APIs).
Users who require multiple RSS formats (JSON, ATOM, XML, HTML) for integration with feed readers or custom applications.
Anyone utilizing n8n to centralize content discovery and monitoring.

Managing YouTube subscriptions and tracking community posts often requires complicated setups involving the official Google API, which can be costly or restrictive. This innovative n8n workflow template completely bypasses those requirements by leveraging smart third-party API requests and services to determine the underlying YouTube Channel ID from any input—be it a username, channel URL, or video link.

Once the Channel ID is resolved, the n8n automation constructs a comprehensive list of 13 separate RSS feed URLs, covering both new video releases and community tab posts, in various standardized formats (XML, JSON, ATOM, etc.). This makes the n8n workflow extremely versatile, providing a robust solution for developers and content managers who need reliable, multi-format feeds without the overhead of API management.

This highly specialized n8n workflow begins with an n8n trigger: the n8n Form Trigger. The user submits a YouTube identifier (URL, username, or ID) via a dedicated form.

1. Input Validation: The Validation Code n8n node determines the exact type of input provided (Channel ID, username, or video ID) using custom JavaScript logic.


2. Routing: The Switch n8n node directs the flow into one of three distinct paths based on the validated input type.


3. Temporary Token Retrieval: Regardless of the path, the workflow first uses an HTTP Request n8n node to fetch a temporary access token from a third-party service, which is essential for the subsequent API lookups (a crucial part of this non-API n8n template).


4. ID Resolution: The flow uses the token and additional HTTP Request nodes to resolve the Channel ID. For instance, if a username is provided, the workflow calls the resolution service to find the corresponding Channel ID. If a video ID is provided, the process resolves the Channel ID associated with that video.


5. RSS URL Construction: Once the Channel ID is confirmed, dedicated Set n8n nodes construct the base YouTube XML feed URL.


6. Aggregation and Advanced Formatting: The Aggregate n8n node combines the results. Subsequent Set nodes (Youtube Channel Videos RSS Formats and Youtube Channel Community RSS Formats) leverage an RSS bridge service (rss-bridge.org) and regex extraction to generate 12 additional, advanced RSS feed formats (HTML, ATOM, JSON, etc.) for both videos and community posts.


7. Final Presentation: The merged data is passed to a Format response as HTML Table n8n node, which renders the 13 resulting URLs into a clean, clickable HTML table. Finally, the Respond to Webhook n8n node returns this table directly to the user who initiated the form request.

To deploy this powerful n8n workflow, follow these steps:

1. Import: Copy the provided JSON code. In your n8n instance, navigate to 'Workflows' and use the 'Import from JSON' option.


2. Activation: Ensure the workflow is set to 'Active'.


3. Trigger Setup: The initial n8n trigger is an n8n Form Trigger listening on the path /Youtube.


4. Access: You can test the n8n workflow by navigating to the corresponding form URL provided by the Form Trigger node (e.g., YOURN8NURL/webhook/Youtube).


5. No Credentials Needed: A significant advantage of this n8n template is that it requires no external credential setup for Google Cloud or YouTube API services, as it utilizes the integrated workarounds defined within the n8n node configuration.

n8n Form Trigger: This acts as the initial n8n trigger, providing a user-friendly form interface to capture the YouTube Channel or Video identifier input. It is configured to accept a single, required field.
Validation Code (Code): A crucial n8n node containing custom JavaScript logic. It uses regular expressions to analyze the user's input (URL, username, ID) and standardize the data, identifying the type (e.g., 'channel username', 'video ID') for proper routing.
Get Temporary Token / GTT (HTTP Request): These n8n nodes execute a third-party API request to commentpicker.com/actions/token.php to securely retrieve a temporary token needed for subsequent channel ID resolution steps, effectively bypassing the need for a Google API key.
Switch: This core logic n8n node routes the workflow based on the output of the validation step, ensuring the correct data resolution path is followed (for Username, Direct Channel ID, or Video ID).
Get Channel ID / Get Video ID Channel ID (HTTP Request): These n8n nodes use the temporary token to query the third-party service's wrappers around YouTube API endpoints, resolving the final Channel ID from either a username or a video ID.
Set XML URL / Set XML Feed URL / Set XML Feed (Set): These n8n nodes are responsible for constructing the fundamental YouTube XML RSS feed URL using the resolved Channel ID.
Aggregate: A merging n8n node used to unify the output from the different channel resolution paths into a single data item.
Youtube Channel Videos/Community RSS Formats (Set): These nodes use expressions to construct 12 additional multi-format RSS links (ATOM, JSON, HTML, etc.) by feeding the Channel ID into the rss-bridge.org service.
Merga Data of Youtube & Community RSS (Merge): Combines the video and community RSS links into one object for final processing.
Format response as HTML Table (Code): This final processing n8n node transforms the complex list of 13 URLs into a clean, readable, styled HTML table for the user.

• Respond to Webhook: Sends the generated HTML table containing all the RSS feeds back to the browser or client that initiated the n8n trigger.