How to get video in YouTube

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Video ID videoId	string	Required	Video ID. Example: dQw4w9WgXcQ
Details part	options	Optional	Details. Options: Basic Info, Basic + Statistics, All Details

Sample request

{
  "videoId": "e.g. dQw4w9WgXcQ",
  "part": "{{trigger.part}}"
}

Returns

{
  "items": [
    {
      "id": "dQw4w9WgXcQ",
      "snippet": {
        "title": "Video Title",
        "thumbnails": {
          "default": {
            "url": "https://i.ytimg.com/..."
          }
        },
        "description": "...",
        "publishedAt": "2026-01-01T00:00:00Z",
        "channelTitle": "Channel"
      },
      "statistics": {
        "likeCount": "50000",
        "viewCount": "1000000"
      }
    }
  ]
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Get Video.

What does the Get Video action do in YouTube?

Returns details of a YouTube video by ID: title, description, thumbnails, duration, privacy status, and statistics. The standard read after a trigger fires with a video ID.

What inputs does Get Video require?

Required: Video ID. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if YouTube returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Get Video support batch operations?

Yes. Run Get Video inside a Loop node to process arrays. TinyCommand handles YouTube's rate limits automatically so you don't have to throttle manually.

More actions