Get 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
Hashed ID hashed_id	string	Required	Wistia media hashed ID (the short string used in embed URLs)

Sample request

{
  "hashed_id": "{{trigger.hashed_id}}"
}

Returns

{
  "id": 12345678,
  "name": "Product demo",
  "type": "Video",
  "created": "2026-04-15T10:00:00Z",
  "project": {
    "id": 1,
    "hashed_id": "proj_abc"
  },
  "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.

FAQ

Questions about Get Media.

What does the Get Media action do in Wistia?

Retrieves a Wistia media by hashed ID with name, duration, thumbnail, project, and embed code. Used to enrich trigger payloads or to render catalog UI.

What inputs does Get Media require?

Required: Hashed ID. 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 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 Get Media support batch operations?

Yes. Run Get 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