List Media: Wistia action

Inputs

The fields this action accepts.

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	Optional	Filter media to a specific project
Name Contains name	string	Optional	Filter by media name (substring)
Per Page per_page	number	Optional	Max media per page

Sample request

{
  "project_id": "{{trigger.project_id}}",
  "name": "{{trigger.name}}",
  "per_page": "{{trigger.per_page}}"
}

Returns

[
  {
    "id": 12345678,
    "name": "Product demo",
    "type": "Video",
    "created": "2026-04-15T10:00:00Z",
    "duration": 142.5,
    "hashed_id": "abc123def4"
  }
]

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about List Media.

What does the List Media action do in Wistia?

Lists media (videos) in your Wistia account with their hashed IDs, name, project, and duration. Useful for catalog exports or batch operations.

What inputs does List Media require?

List Media has no required inputs. Sensible defaults are applied if you leave fields blank.

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 workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does List Media support batch operations?

Yes. Run List Media inside a Loop node to process arrays. Tiny Command handles Wistia's rate limits automatically so you don't have to throttle manually.

More actions