Short answer: Drop the "Vimeo → Get 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 | Numeric Vimeo video ID. From the URL: vimeo.com/<video_id>. |
{"video_id": "123456789"}
{"uri": "/videos/123456789","link": "https://vimeo.com/123456789","name": "My Product Demo","embed": {"html": "<iframe src='...'></iframe>"},"duration": 184,"description": "A 3-minute walkthrough."}
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.