Pipedream YouTube steps in n8n

YouTube workflows on Pipedream are content pipelines: a new video from a channel is summarised and posted to Slack or Telegram, a rendered file is uploaded with a title and description, a video is added to a playlist. n8n has a native YouTube node; new-video triggers become RSS or polling.

The n8n side

YouTube node (n8n-nodes-base.youTube):

Resource	Operations
Channel	Get, Get Many, Update, Upload Banner
Playlist	Create, Delete, Get, Get Many, Update
Playlist Item	Add, Delete, Get, Get Many
Video	Delete, Get, Get Many, Rate, Update, Upload
Video Category	Get Many

There is no YouTube trigger node.

What maps where

Pipedream (app youtube_data_api)	In n8n	Status
Upload Video	Video → Upload	manual
Update Video Details	Video → Update	manual
Upload Thumbnail	HTTP Request → thumbnails.set	manual
Search Videos, List Videos	Video → Get Many (search filters)	manual
Add Playlist Items	Playlist Item → Add	manual
Create Playlist	Playlist → Create	manual
Channel Statistics	Channel → Get (statistics part)	manual
New Videos, New Videos by Handle (polling)	RSS Feed Trigger on youtube.com/feeds/videos.xml?channel_id=…	manual
New Videos in Playlist (polling)	RSS Feed Trigger on ?playlist_id=…, or Schedule + Playlist Item → Get Many	manual
New Comment Posted, New Subscriber, New Videos by Search (polling)	Schedule Trigger + HTTP Request / Get Many + Remove Duplicates	manual

YouTube is not in the converter's mapped list. Each step arrives as a placeholder with its props in a comment. If the Pipedream workflow used the generic RSS source on a YouTube feed, that trigger converts automatically to the RSS Feed Trigger.

YouTube credentials in n8n

Google OAuth2 (single service) for YouTube. On self-hosted n8n: Google Cloud console → enable YouTube Data API v3 → OAuth client (web) with n8n's redirect URL → paste Client ID and Secret. Uploads need the account that owns the channel; brand accounts must be picked during consent.

Typical migration: new video to Telegram

Pipedream: YouTube New Videos by Handle → OpenAI Chat (summary) → Telegram Send a Text Message. n8n: RSS Feed Trigger (channel feed URL) → OpenAI → Telegram → Message → Send. The RSS feed costs no API quota, unlike polling the Data API.

YouTube migration pitfalls

• Quota. The Data API has a default quota of 10,000 units per day per project. Search requests and uploads are far more expensive than reads; check Google's quota calculator before polling with search.
• Unverified apps. Videos uploaded through an unverified Google Cloud project may be locked as private until the project passes an audit.
• Binary data. Upload expects the video as binary on the item (from HTTP Request, Google Drive or Read/Write Files).
• Handles vs channel IDs. RSS feeds need the channel ID (UC…), not the @handle.

How to move your YouTube workflows

1. Export from Pipedream.
2. Upload on /convert; the free report lists every YouTube step and its props.
3. Get the n8n JSON: 1 workflow is free; full export: $3 per workflow, $19 minimum — coming soon.

See the Pipedream to n8n guide. Related: Google Drive, OpenAI, Telegram.