Short answer: Drop the "YouTube → Search Videos" 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 |
|---|---|---|---|
Search Query query | string | Required | Search Query. Example: javascript tutorial |
Max Results maxResults | number | Optional | Max Results |
Sort By order | options | Optional | Sort By. Options: Relevance, Date, View Count, Rating |
{"query": "e.g. javascript tutorial","maxResults": "{{trigger.maxResults}}","order": "{{trigger.order}}"}
{"items": [{"id": {"videoId": "abc123"},"snippet": {"title": "JavaScript Tutorial","publishedAt": "2026-01-01T00:00:00Z","channelTitle": "Code Academy"}}],"pageInfo": {"totalResults": 1000}}
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.