Short answer: Drop the "YouTube → List Playlists" 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 |
|---|---|---|---|
Max Results max_results | string | Optional | — |
{"max_results": "{{trigger.max_results}}"}
{"items": [{"id": "PLabc","snippet": {"title": "Tutorials"},"contentDetails": {"itemCount": 10}}]}
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.