ActionWistiaUpdated September 2026

How do I get engagement stats for a Wistia video?

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

Get Media Stats in Wistia — start free All 5 Wistia actions

Get Media Stats 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.

Field	Type	Required	Description
Hashed ID hashed_id	string	Required	Wistia media hashed ID

Sample request

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

Returns

{
  "id": 12345678,
  "stats": {
    "plays": 2500,
    "visitors": 4012,
    "pageLoads": 5230,
    "engagement": 0.71,
    "averagePercentWatched": 71.4,
    "percentOfVisitorsClickingPlay": 62.3
  },
  "hashed_id": "abc123def4"
}

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

Triggered by

Apps that pair well as the trigger for Get Media Stats.

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

Google Sheets → Wistia

2 Google Sheets triggers

HubSpot → Wistia

18 HubSpot triggers

FAQ

Questions about Get Media Stats.

What does the Get Media Stats action do in Wistia?

Returns engagement statistics for a Wistia media (load count, play count, play rate, hours watched). Use for content reports or for in-app analytics widgets.

What inputs does Get Media Stats 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 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 Get Media Stats support batch operations?

Run Get Media Stats 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