Wistia

Put AI agents in charge of your Wistia video library. Agents upload media from URLs, update and organize videos into projects, and pull play and engagement stats to see how content performs.

9 actions API key available

Wistia website ↗ Platform Documentation ↗ Capability data verified 2026-07-28

A finished video render lands at a public URL from the production flow

List Projects resolves the right destination project for this content type

Upload Media From URL imports the file server-side into the project

Update Media sets the clean title and description from the content brief

Get Media confirms processing has progressed past the queued state

The video owner reviews the title, description, and project placement before the embed goes anywhere public

The team channel gets the new media's hashed ID and thumbnail, ready to embed

What This Integration Enables

Wistia is where B2B teams put video they intend to measure, and the library is only as useful as its housekeeping. FlowRunner agents do the housekeeping. They import videos server-side from public URLs, file media into the right projects, keep titles and descriptions synced with the external system that actually owns them, and pull per-video play and engagement stats so performance is a report that arrives, not a question someone has to remember to ask. - Import renders from [Dropbox](/integrations/dropbox) links or any public URL straight into the right project - Sync video titles and descriptions from a [Google Sheets](/integrations/google-sheets) catalog or your CMS - Publish landing pages in [WordPress](/integrations/wordpress) embedding new videos the moment they finish processing - Log play counts, hours watched, and engagement into a performance dashboard on a schedule - Alert sales through [Slack](/integrations/slack) when a prospect-relevant video crosses a play threshold - Audit projects and flag stale media for a reviewed cleanup pass The stats side deserves emphasis. Wistia's per-media engagement data is the reason teams pay for it over a generic host, and an agent that reads Get Media Stats weekly turns that data from a dashboard nobody opens into a signal that reaches the people who act on it.

Without FlowRunner

Uploads are a browser chore Someone downloads the render, opens Wistia, uploads, retypes the title from the brief

Metadata drifts from the catalog The CMS says one title, Wistia says another, and the landing page says a third

Performance is checked on demand Engagement stats get looked up when someone asks, which means rarely

With FlowRunner

Renders file themselves Videos import from a URL into the right project with clean metadata, as a pipeline step

One source of truth for titles Names and descriptions sync from the CMS or catalog on a schedule

Performance reports on a schedule Play counts, play rate, and engagement land in the dashboard weekly, per video

Use Case Scenarios

The batch import that files itself

A [Google Sheets](/integrations/google-sheets) tab holds thirty video URLs from a webinar series migration. The agent reads the rows, calls Upload Media From URL for each with the target project's hashed ID, then Update Media to set the title and description from the sheet's columns. Wistia fetches every file server-side, so nothing is downloaded or re-uploaded locally. What was a week of drag-and-drop becomes a monitored flow with a completion report.

Video ships, page ships, team knows

When a new product video imports, the flow waits for processing, pulls the embed details with Get Media, and creates a draft landing page in [WordPress](/integrations/wordpress) with the video embedded and copy from the brief. A [Slack](/integrations/slack) message gives the marketing lead the draft link and the thumbnail. Publishing stays a human call; everything before it stops being human work.

The engagement report sales actually reads

Weekly, List Medias enumerates the demo and case study project, and Get Media Stats pulls each video's plays, play rate, and engagement. Rows append to the performance sheet, and any video that crossed its play-count threshold since last week posts to the sales channel with the movement called out. When a prospect's team watches the integration demo eleven times in three days, sales hears about it while the deal is still warm.

Human-in-Loop Highlight

Delete Media does not just remove a file from a library. It removes the media from its project and from every embed, permanently, with no undo, which means the landing page that converted last quarter now renders a hole where the product demo used to be. So cleanup flows in FlowRunner never let the agent swing that axe unattended. The agent builds the case instead: List Medias sweeps the archive project, Get Media Stats pulls each candidate's trailing engagement, and the owner receives a docket, "6 medias, zero plays in 12 months, not referenced in the CMS catalog, combined 2.1 GB." The owner strikes two off the list because one is embedded in a customer's onboarding portal and one is legal's, and approves the rest. Four deletes run. The two that would have broken something never happened, and that is the entire argument for the gate.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

9 actions

Medias

List Medias Lists medias in the account, optionally filtered by project, returning each one's hashed ID, name, type, duration, thumbnail, and status, with pagination. The sweep behind audits, reports, and cleanup dockets.
Get Media Retrieves a single media in full by hashed ID: name, description, duration, thumbnail, embed assets, and project association. The inspection step before embedding, editing, or deciding anything.
Update Media Updates a media's name and/or description, changing only the fields you provide. The sync tool that keeps Wistia aligned with the CMS or catalog that owns the metadata.
Delete Media Permanently deletes a media by hashed ID, removing it from its project and all embeds. Cannot be undone, which is why FlowRunner routes it through a reviewed cleanup docket.
Upload Media From URL Imports a media from a publicly accessible file URL. Wistia fetches the bytes server-side and returns the new media in a queued state, optionally filed into a project with name and description set. The workhorse of migrations and render pipelines.

Projects

List Projects Lists the account's projects with hashed ID, name, media count, and creation date. The lookup that resolves where new media should land.
Get Project Retrieves a project in full: name, description, sharing settings, and the list of medias inside. The audit read for library organization.
Create Project Creates a new project to organize medias, with optional anonymous upload, download, and public sharing settings. Used when a new series or campaign needs its own container.

Analytics

Get Media Stats Retrieves aggregate engagement for one media: load count, play count, play rate, hours watched, engagement, and visitor count. The number source behind every performance report and sales alert this page describes.

Frequently Asked Questions

What can FlowRunner do with Wistia?

FlowRunner agents can run List Medias, Get Media, and Update Media in Wistia, plus 6 more actions.

Does connecting Wistia to FlowRunner require OAuth?

No. Wistia connects to FlowRunner with an API key, no OAuth flow required.

Can Wistia trigger a FlowRunner workflow automatically?

Wistia doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Wistia

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us