ActionWistiaUpdated September 2026

How do I upload a video to Wistia?

Short answer: You can upload media in Wistia by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Wistia Upload Media action to a workflow, map its 4 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Upload Media in Wistia — start free
Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

FieldTypeRequiredDescription
Project ID
project_id
stringRequiredProject to upload the media into. Use List Projects to find it.
Media URL
url
stringRequiredPublic URL of the video file Wistia should fetch
Name
name
stringOptionalTitle to display in Wistia
Description
description
stringOptionalMedia description
Sample request
{
"project_id": "{{trigger.project_id}}",
"url": "https://example.com/video.mp4",
"name": "{{trigger.name}}",
"description": "{{trigger.description}}"
}
Returns
{
"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.

Triggered by

Apps that pair well as the trigger for Upload Media.

Any of these apps can fire this action as part of a workflow.

FAQ

Questions about Upload Media.

What does the Upload Media action do in Wistia?
Uploads a new media (video) to Wistia from a URL or file into the specified project. Processing is async, so the returned media is initially unready; poll Get Media for status.
What inputs does Upload Media require?
Required: Project ID, Media URL. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Wistia returns an error?
The run history shows the failed step with its input and the error message Wistia returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does Upload Media support batch operations?
Run Upload Media inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Wistia's rate limits.
More actions

Other Wistia actions.

Upload Media in Wistia — start free