WActionWistiaUpdated May 2026

How do I get engagement stats for a Wistia video?

Short answer: Drop the "Wistia → Get Media Stats" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 5 Wistia actions

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 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 Stats support batch operations?

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