Short answer: Drop the "YouTube → Add Comment to 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. |
Comment Text text | string | Required | — |
{"video_id": "{{trigger.video_id}}","text": "{{trigger.text}}"}
{"id": "comment_abc","snippet": {"topLevelComment": {"snippet": {"textDisplay": "Hi","authorDisplayName": "Jane"}}}}
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.