Short answer: Drop the "YouTube → Get Channel" 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 |
|---|---|---|---|
Channel ID channelId | string | Required | Channel ID. Example: UCxxxxxx |
{"channelId": "e.g. UCxxxxxx"}
{"items": [{"id": "UCxxxxxx","snippet": {"title": "Channel Name","customUrl": "@channelname","description": "About this channel"},"statistics": {"viewCount": "50000000","videoCount": "500","subscriberCount": "100000"}}]}
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.