Short answer: Drop the "Vimeo → List 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 |
|---|---|---|---|
Page Size per_page | number | Optional | Videos per page (1-100). |
Page Number page | number | Optional | — |
Search Query query | string | Optional | Optional text search across title/description. |
{"per_page": "{{trigger.per_page}}","page": "{{trigger.page}}","query": "{{trigger.query}}"}
{"data": [{"uri": "/videos/123456789","link": "https://vimeo.com/123456789","name": "My Product Demo","duration": 184,"created_time": "2026-05-01T10:00:00+00:00"}],"page": 1,"total": 42}
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.