Short answer: Drop the "YouTube → Update Video" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Video ID video_id | string | Required | The Video ID assigned by Youtube. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label. |
Title title | string | Required | — |
Description description | string | Optional | — |
Tags tags | array | Optional | — |
Category ID category_id | string | Optional | — |
Privacy privacy_status | options | Optional | — |
{"video_id": "{{trigger.video_id}}","title": "{{trigger.title}}","description": "{{trigger.description}}","tags": "{{trigger.tags}}","category_id": "{{trigger.category_id}}"}
{"id": "abc","status": {"privacyStatus": "public"},"snippet": {"title": "Updated title"}}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.