Short answer: Drop the "Vimeo → Create Video Upload" 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 |
|---|---|---|---|
Title name | string | Required | My Product Demo |
File Size (bytes) size | number | Required | Total file size in bytes. Vimeo needs this upfront for the tus session. |
Description description | string | Optional | — |
Privacy privacy_view | options | Optional | — |
{"name": "My Product Demo","size": "{{trigger.size}}","description": "{{trigger.description}}","privacy_view": "{{trigger.privacy_view}}"}
{"uri": "/videos/123456789","link": "https://vimeo.com/123456789","upload": {"size": "10485760","approach": "tus","upload_link": "https://files.tus.vimeo.com/files/abc..."}}
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.