Short answer: Drop the "Wistia → Upload Media" 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 |
|---|---|---|---|
Project ID project_id | string | Required | Project to upload the media into. Use List Projects to find it. |
Media URL url | string | Required | Public URL of the video file Wistia should fetch |
Name name | string | Optional | Title to display in Wistia |
Description description | string | Optional | Media description |
{"project_id": "{{trigger.project_id}}","url": "https://example.com/video.mp4","name": "{{trigger.name}}","description": "{{trigger.description}}"}
{"id": 12345678,"name": "Product demo","type": "Video","status": "queued","created": "2026-04-15T10:00:00Z","duration": 142.5,"hashed_id": "abc123def4","thumbnail": {"url": "https://embed-fastly.wistia.com/.../thumb.jpg"}}
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.