Menu

Mattering Automations Wistia integration

Connect Wistia to Mattering Automations: media and folders, captions, tags, the deleted media trash, channels and webinars, player customizations, and both the stats and analytics reporting surfaces as workflow steps, authenticated with one account API token.

The Mattering Automations Wistia integration puts Wistia's modern API on your automation canvas: list, update, copy, move, archive and delete media, import from a URL, manage folders, subfolders and the deleted media trash, add and remove captions, create and apply tags in bulk, read channels, episodes, webinars and registrations, change player customizations, and pull both reporting surfaces, the older stats counters and the newer analytics family.

The credential is a Wistia API token, created in your Wistia account settings under API access and shown once at creation. It belongs to the account rather than to a folder, so one credential reaches the whole library. What decides which nodes actually work is not a scope list but the permission level chosen when the token is created, and that catches people out often enough to be worth saying first: every stats and analytics node needs Read detailed stats, a separate permission that ordinary read access to media and folders does not include.

Two of Wistia's own conventions cause wrong answers rather than errors, so they are worth reading before you build a report. The analytics endpoints treat the end date as exclusive while the older stats by-date endpoints are inclusive, so an analytics range ending on the last day of a month silently omits that day. And the leaderboard style reads, Wistia: Get Account Top Content, Wistia: Get Media Embed Locations and Wistia: Get Media Traffic Breakdown, are ranked and truncated rather than merely paged, which means their rows cannot be summed across chunks. Setup takes a few minutes, and this guide walks through each step and ends with the full node reference.

Before you start

  • A Wistia account you can create an API token in, from account settings under API access. The token is shown once at creation.
  • A decision about the token's permission level, because it is the thing that gates this integration rather than per node scopes. Basic account reads work with any valid token, the library reads need read access to folder and media data, Wistia: Search and the tag and webinar reads need read access to all data, every stats and analytics node needs Read detailed stats, and every write node needs read, update and delete access.
  • A sense of which Wistia features your plan includes. Wistia documents archiving as requiring access to the Archiving feature, and returns a permission error without it. Webinars, channels and detailed stats are worth confirming on your plan rather than assuming, and Wistia's own pricing and support pages are where to check.
  • A Mattering workspace with access to the Automations app.
  • Not required and not stored here: an upload path. Wistia's file upload host is not part of this integration, so ingest happens through Wistia: Import Media From URL rather than by posting a file from the canvas.

Create a Wistia API token

Mattering authenticates to Wistia with a bearer token created in your account settings. Tokens are account wide rather than per folder, and their access is set by a permission level chosen at creation rather than by a list of scopes, so the level you pick is effectively the list of nodes that will work.

Sign in to Wistia and open your account settings, then the API Access section.
Create a new API token and choose its permission level. Pick the level that covers the whole workflow, not just its first step.
The token is shown once at creation and cannot be read again afterwards. Copy it before leaving the page, and if it is lost, create a new one rather than hunting for the old value.
If any part of the workflow reads performance data, the token needs Read detailed stats specifically. Read access to media and folders does not imply it, which is why a token that lists the whole library can still fail on every analytics node.

Connect Wistia to Mattering

In Mattering Automations, open Connectors and click Add Connector.
Choose Wistia from the list.
Click Create new credential, paste the API token, and save.
The credential is stored encrypted in Google Secret Manager and never appears in workflow logs. Mattering also pins Wistia's API version header on every request, because omitting it serves whatever release is current and a running automation would change shape as Wistia ships new ones.
Click Test Connection. Mattering calls Wistia's account endpoint, which needs no parameters, no ids and, uniquely here, no permission level beyond a valid token. That makes it a clean signal: a failure there is an authentication problem rather than a permission one.
Click Connect. All 51 Wistia nodes appear in your canvas palette.
Four of those nodes are flagged destructive: Wistia: Delete Media, Wistia: Delete Folder, Wistia: Delete Tag and Wistia: Delete Captions. Deleting media stops every embed of that video working immediately, and deleting a tag removes it from every video it was applied to, so any saved filter or rule matching on it stops matching.

Verify it works

After connecting, open any automation canvas and check the palette: a Wistia section should list the read and action nodes. Drop Wistia: Get Account onto the canvas and run a test step. It is the integration's natural probe because it needs no parameters and no permission level beyond a valid token, so a success proves the credential itself and separates an auth problem from a permission one. Then run Wistia: List Media: this response is a bare array, so rows read at data rather than under a wrapper, and each row carries the opaque hashed id the rest of the connector uses.

Now test the half people usually came for, because it is gated separately. Drop Wistia: Get Account Stats or Wistia: Get Media Analytics onto the canvas and run it. If the account read and the media list both worked and this one returns a permission error, the token is missing Read detailed stats rather than the connector being broken. While you are here, open a picker to see the labelling: the media field on any node lists videos by title with their folder name underneath, which is what separates two videos both called Welcome. Everything in this verify path is read-only, so it cannot reach the four destructive nodes and is safe to re-run whenever you rotate the token.

Node reference

51 nodes, generated from the connector itself so this reference always matches what ships.

Read and query nodes 34

Wistia: Get Account

wistia_get_account

Get the account the API token belongs to: its name, its Wistia URL, and how many medias, folders and channels it holds. This is the cheapest call in the connector and the only one that works with any token permission level, which makes it the right way to confirm a credential works before trusting anything else.

Wistia: Get Account Analytics

wistia_get_account_analytics

Account-wide totals for one date range: unique loads, unique plays, plays, play rate, played time, unique visitors, engagement rate and form conversions. One object covering the whole window, not a series - Wistia: Get Account Analytics Timeseries is the series. The end date is EXCLUSIVE on this surface, so ask for the first of next month to include the whole of this one. The range may not exceed two years.

Wistia: Get Account Analytics Timeseries

wistia_get_account_analytics_timeseries

Account-wide performance as a series: one row per day, week or month, each carrying unique loads, unique plays, plays, play rate, played time, unique visitors, engagement rate and form conversions. Any metric may come back null for a bucket with no activity. The end date is EXCLUSIVE and the range may not exceed two years. Bucket width is chosen per request, so the same node returns daily or monthly rows depending on what you ask for.

Wistia: Get Account Stats

wistia_get_account_stats

Lifetime totals for the whole account: loads, plays and hours watched. Three numbers, no window, no parameters - the cheapest possible health check on a video library. For a series over time use Wistia: Get Account Stats By Date, and for rate metrics use the Analytics nodes. Needs a token with Read detailed stats, which is a separate permission from ordinary read access.

Wistia: Get Account Stats By Date

wistia_get_account_stats_by_date

Account-wide loads, plays and hours watched broken out by day, between two dates inclusive. Leaving both dates blank gives yesterday and today, which makes this a cheap daily poll. Each row carries its own date, so a long backfill is ONE request rather than one per day.

Wistia: Get Account Top Content

wistia_get_account_top_content

The account's best-performing content over a date range, ranked: plays, play rate, engagement rate, played time and unique visitors per media, channel or folder, with each media's name, type, duration and thumbnail alongside. This is the leaderboard a weekly digest is built from. Because the rows are RANKED AND TRUNCATED, results from two different date ranges cannot be added together - re-request the range you want. Note the group_by value for folders is still spelled project, which the Stats API kept.

Wistia: Get Account Usage

wistia_get_account_usage

Get the account's plan tier, whether uploads are currently allowed, and its media and storage usage against its limits. Use this as a guard in front of an upload workflow: data.can_upload false with data.upload_blocked_reason explains why before a bulk import fails halfway. Usage and limits are visible only to account owners and managers; every other token gets null for data.limits, which is a permission result rather than an error.

Wistia: Get Background Job Status

wistia_get_background_job_status

Check how a queued bulk operation is going. Every bulk write in this connector - archive, restore, move, bulk tag, import from URL, restore from trash - returns immediately with a job id and does the work afterwards, so this node is what turns an acknowledgement into an answer. Poll until data.background_job_status.status is finished, then read the per-item results array to see which media succeeded and which failed, and why.

Wistia: Get Folder

wistia_get_folder

Get one folder's record: name, description, media count, public-access flags, and whether anonymous visitors may upload or download. Despite the path parameter being named id by the vendor, it wants the HASHED id, not the numeric one that appears in the response body.

Wistia: Get Folder Stats

wistia_get_folder_stats

Lifetime loads, plays and hours watched for every media in one folder. Note the path: when projects were renamed to folders, the Stats API path /stats/projects/{id} was deliberately NOT renamed, so this node sends a folder's hashed id to a projects path. That is the vendor's decision, not a mistake here. The number_of_videos field the endpoint returns is marked deprecated; read data.media_count from Wistia: Get Folder instead.

Wistia: Get Media

wistia_get_media

Get one media's full record: name, description, duration, processing status and progress, thumbnail, tags, the folder and subfolder it sits in, and the assets array with each rendered file's URL, dimensions, size and content type. Poll data.status until it reads ready after an import; anything else means the file is still being processed.

Wistia: Get Media Analytics

wistia_get_media_analytics

One video's totals for a date range: unique loads, unique plays, plays, play rate, played time, unique visitors, engagement rate, call-to-action impressions and conversions, and form conversions. This is the windowed counterpart to Wistia: Get Media Stats, which reports lifetime totals with no range. The end date is EXCLUSIVE and the range may not exceed two years.

Wistia: Get Media Analytics Timeseries

wistia_get_media_analytics_timeseries

One video's performance as a series: a row per day, week or month carrying unique loads, unique plays, plays, play rate, played time, unique visitors, engagement rate, call-to-action impressions, conversions and conversion rate, and form conversions. This is the node a video dashboard is built on. Remember which columns are RATES: play rate, engagement rate and conversion rate are ratios and must never be added across rows, and the three unique counts cannot be added either. The end date is EXCLUSIVE; the range may not exceed two years.

Wistia: Get Media Customizations

wistia_get_media_customizations

Read every player setting saved against a media: colour, autoplay, which controls are shown, end-of-video behaviour, and the plugin block that holds captions, chapters, call-to-action and password settings. Note this payload is camelCase (playerColor, autoPlay) rather than snake_case like the rest of the modern API, because these keys are the player's own embed-option names. Values come back as strings even when they read like booleans.

Wistia: Get Media Embed Locations

wistia_get_media_embed_locations

Which pages a video is embedded on and how it performs on each: the domain, path, page title, loads, plays, play rate, played time, engagement rate and conversion rate per URL. This answers where a video is actually being watched, which is usually not where anyone remembers putting it. Ranked and truncated, defaulting to only 10 rows - raise per_page before concluding a page is not listed.

Wistia: Get Media Engagement

wistia_get_media_engagement

The engagement graph behind a video: the average share of the video watched, plus two arrays describing viewing across the video's length - engagement_data for how many viewers were still watching at each point, and rewatch_data for the parts people went back to. The arrays are positional buckets across the video, not timestamps, so a spike at index 4 means roughly four fifths of the way in for a five-bucket array. This is how a workflow finds the moment viewers drop off.

Wistia: Get Media Form Conversions

wistia_get_media_conversions

The actual people who filled in a video's Turnstile or email-gate form during a date range: first name, last name, email and when they converted. This is the lead list a video-to-CRM automation writes into a pipeline. Rows are at data.data[] inside an envelope and paging is cursor-only, from data.page_info.end_cursor. The end date is EXCLUSIVE; the range may not exceed two years.

Wistia: Get Media Stats

wistia_get_media_stats

Lifetime performance for one video: loads, plays, play rate, hours watched, average engagement, unique visitors, and a breakdown of every call to action and annotation with its impression and click counts. Note play_rate and engagement here are RATES over the whole lifetime of the video, not sums, so they cannot be added to anything.

Wistia: Get Media Stats By Date

wistia_get_media_stats_by_date

One video's loads, plays and hours watched broken out by day, between two dates inclusive. Leaving both blank gives yesterday and today. Each row carries its own date, so a ninety-day backfill is one request rather than ninety.

Wistia: Get Media Traffic Breakdown

wistia_get_media_traffic

Where a video's viewers came from, broken down by whichever dimension you pick: UTM campaign, source or medium, referring domain, or viewer screen size. Each row carries loads, plays and engagement rate. The DIMENSION COLUMN IS NAMED AFTER group_by, so a workflow reading these rows has to know which breakdown it asked for: group_by utm_source produces a utm_source column, not a generic one. Ranked and truncated.

Wistia: Get Webinar Analytics

wistia_get_webinar_analytics

How a webinar performed: registrations (including imported and on-demand ones), attendance, total and average watch time, engagement rate, chat and Q and A volume, and every poll question with its per-option response counts. Turn on include_post_event to add on-demand viewing after the live event ended, which is when the two post-event date fields start mattering; without that flag they are ignored.

Wistia: List Channel Episodes

wistia_list_channel_episodes

List channel episodes across the account or within one channel, with each episode's title, summary, the media it wraps, whether it is published, and its scheduled publish time. Filter on published false to find episodes waiting to go live, which is the usual trigger for a publishing workflow.

Wistia: List Channels

wistia_list_channels

List the account's channels: their names, how many media each holds, whether new episodes publish automatically, and whether the channel is set up as a podcast. A channel is Wistia's published video series; its contents are episodes, which Wistia: List Channel Episodes returns.

Wistia: List Deleted Media

wistia_list_deleted_medias

List media that has been deleted but is still inside the account's restore window, with the folder each came from, when it was deleted, and - the useful one - when it stops being restorable. Wistia keeps deleted media for 30 days on most plans and 14 on free plans. A media missing from this list is gone for good.

Wistia: List Folders

wistia_list_folders

List the account's folders with names, hashed ids, media counts and whether each is a shared folder or someone's personal library. Folders were called projects on the old v1 API and are what the Wistia UI calls folders today. Every folder picker in this connector reads its values from here, and note each folder carries BOTH a numeric id and a hashed id - almost everything wants the hashed one.

Wistia: List Media

wistia_list_medias

List the account's media with names, hashed ids, durations, statuses, thumbnails, tags and the folder each one lives in. This is the node every other Wistia media node leans on: the hashed id it returns is what media pickers store. Filter by folder, media type, tags or archived state. The response is a bare array with no pagination wrapper, and each row carries its own cursor for cursor paging.

Wistia: List Media Captions

wistia_list_media_captions

List every caption track on a media, with each track's language code, its English and native language names, whether it is still a draft, and the full SRT text. The text field is the whole transcript, so this doubles as the way to pull a video's transcript into a workflow that summarises or translates it.

Wistia: List Subfolders

wistia_list_subfolders

List the subfolders inside one folder, in their display order. Subfolders are one level deep and belong to exactly one folder, which is why this node takes a folder and why the subfolder picker on Wistia: Move Media asks for the destination folder first.

Wistia: List Tags

wistia_list_tags

List the account's tags with how many media each one is applied to. Tag names are the identifier here - there is no separate tag id - so the name from this node is what every other tag field wants.

Wistia: List Viewing Events

wistia_list_events

Individual viewing sessions: who watched what, when, from where, how much of it they saw, and any form conversion the session produced. This is the rawest data Wistia exposes and the input to lead-scoring workflows. Only the last two years of events are retained. Rows are one per session at irregular times, not per day, so this is a stream to filter rather than a series to chart.

Wistia: List Visitors

wistia_list_visitors

List the people who have watched something, with their visitor key, when they were last active, how many loads and plays they account for, whatever identity Wistia has captured (name, email, organisation) and their browser and platform. Most visitors are anonymous: filter on has_email to get only the ones a CRM workflow can act on.

Wistia: List Webinar Registrations

wistia_list_webinar_registrations

List who registered for a webinar and what they did: name, email, company, the UTM parameters they arrived with, whether and when they attended, how engaged they were, and their chat, poll and Q and A activity. This is the node a webinar-to-CRM workflow is built on. Filter on attendance to separate attendees from no-shows. Unlike most list endpoints here, the response is an envelope: rows are at data.registrations[] and paging is cursor-only, from data.page_info.end_cursor.

Wistia: List Webinars

wistia_list_webinars

List the account's webinars with titles, scheduled times and time zones, lifecycle and registration status, and the audience, host and panelist links. Webinars were called live stream events on the old v1 API; this is the same thing under the name the product uses. Filter on started to separate upcoming events from ones that have already run.

Wistia: Search

wistia_search

Search across the whole account in one call: media, folders, subfolders, channels, channel episodes and webinars. It searches TRANSCRIPTS as well as titles, so a query matching spoken words finds the video that said them. Results come back grouped by resource type under data.data, not as one flat list, so read data.data.medias[] rather than data[]. Needs a token with Read all data.

Action nodes 17

Wistia: Archive Media

wistia_archive_medias

Archive up to 100 media at once. Archiving takes a video out of the active library without deleting it, and Wistia: Restore Media puts it back, which makes this the reversible alternative to Wistia: Delete Media. Two kinds of media cannot be archived: webinar media, and Soapbox videos imported before 1 September 2023. Needs the Archiving feature on the account. Asynchronous: poll the returned job id.

Wistia: Bulk Tag Media

wistia_bulk_tag_medias

Apply a set of tags to a set of media in one call. Tags are APPENDED to whatever each media already carries, unlike Wistia: Update Media whose tags field replaces the lot, so this is the safe way to add a tag across a library. Tag names that do not exist yet are created. Asynchronous: poll the returned job id for the per-media outcome.

Wistia: Copy Media

wistia_copy_media

Duplicate a media into a folder, optionally handing the copy to a different owner. The copy gets its own hashed id and its own stats starting from zero; the original is untouched. Note this is the ONE endpoint in the connector whose folder_id is the NUMERIC folder id rather than the hashed one, which the picker on that field handles for you.

Wistia: Create Captions

wistia_create_captions

Add a caption track to a media from SRT text. Pass the SRT contents as a string; Wistia detects the language if you do not name one. This is the write half of a translation workflow: pull the existing track with Wistia: List Media Captions, translate the SRT, post it back under a new language code. Needs a token with Read, update and delete anything.

Wistia: Create Folder

wistia_create_folder

Create a folder. Every field is optional, so an empty call makes an unnamed shared folder owned by the account owner. The response carries the new folder's hashed id at data.hashed_id, which is what an import or move node needs next. Note this endpoint's body keys are camelCase on the wire while the response is snake_case; the node handles that translation.

Wistia: Create Tag

wistia_create_tag

Create a tag on the account without applying it to anything. Wistia: Bulk Tag Media creates tags implicitly as it applies them, so reach for this only when a tag needs to exist before any media carries it. A name already in use returns 422.

Wistia: Delete Captions

wistia_delete_captions

DESTRUCTIVE. Remove one language's caption track from a media. The track's timecoded text is gone; a purchased or hand-corrected transcript has to be re-ordered or re-uploaded to get it back, and any translation derived from it goes with it. The media itself and its other caption languages are untouched. Returns 200 with no body.

Wistia: Delete Folder

wistia_delete_folder

DESTRUCTIVE. Delete a folder. Wistia states the folder is permanently deleted and cannot be undone, and does NOT document what becomes of the media and subfolders inside it, so assume they go with it: treat this as deleting the folder's entire contents, along with every embed of every video in it. Move the media out first with Wistia: Move Media if you only want the folder gone. Check data.media_count on Wistia: Get Folder before running this.

Wistia: Delete Media

wistia_delete_media

DESTRUCTIVE. Delete a media and everything attached to it: its captions, its customizations, its stats history and its channel episode if it has one. Every embed of this video on every page stops working immediately. Wistia's own reference for this endpoint states the deletion is permanent and cannot be undone, while the trash surface says deleted media stays restorable for 30 days on most plans and 14 on free plans - check Wistia: List Deleted Media before assuming either. To take a video out of circulation reversibly, use Wistia: Archive Media instead. Needs a token with Read, update and delete anything.

Wistia: Delete Tag

wistia_delete_tag

DESTRUCTIVE. Delete a tag from the account. The tag is removed from EVERY media it was applied to, so any saved filter, automation condition or channel rule that matched on it stops matching. The media themselves are not touched. Wistia states this cannot be undone; re-creating a tag of the same name does not re-apply it to anything.

Wistia: Import Media From URL

wistia_import_media_from_url

Pull a publicly reachable media file into Wistia by URL. This is how an automation gets video INTO Wistia: the connector does not use Wistia's separate multipart upload host, so the file must already be somewhere Wistia can fetch it. Imports from vimeo.com and wistia.com are refused by the vendor. The call returns a queued background job rather than the finished media, so follow it with Wistia: Get Background Job Status and then Wistia: Get Media until status reads ready. Leaving the folder blank makes Wistia create a NEW folder rather than using a default one.

Wistia: Move Media

wistia_move_medias

Move up to 100 media into a folder, and optionally into a subfolder inside it. THIS ENDPOINT HAS ITS OWN RATE LIMIT of 10 requests per 5 minutes, separate from and far tighter than the account's 600 per minute, so move media in batches rather than one node run per video. Asynchronous: poll the returned job id. A partial failure comes back as HTTP 207 with a partial_errors array naming which media failed.

Wistia: Restore Archived Media

wistia_restore_medias

Bring archived media back into the active library, up to 100 at a time, placing them in a folder you name. This undoes Wistia: Archive Media; it does NOT recover deleted media - that is Wistia: Restore Deleted Media, a different surface with its own time limit. Asynchronous: poll the returned job id. Needs the Archiving feature on the account.

Wistia: Restore Deleted Media

wistia_restore_deleted_medias

Recover deleted media from the trash, up to 1000 at a time, either back where each one was or into a folder you name. Only works while the media is still inside its restore window - check Wistia: List Deleted Media and its restore_expires_at first. Asynchronous: poll the returned job id. This is a different surface from Wistia: Restore Archived Media, which un-archives rather than un-deletes.

Wistia: Update Folder

wistia_update_folder

Rename a folder, rewrite its description, or change its sharing posture: whether it is publicly accessible and whether anonymous visitors may upload into it or download from it. Turning public access on exposes every media in the folder to anyone with the link, so treat it as a disclosure change rather than a cosmetic one. Fields left blank are not touched.

Wistia: Update Media

wistia_update_media

Rename a media, rewrite its description, replace its tag set or swap its thumbnail. Note that tags REPLACE the media's existing tags wholesale rather than adding to them - to add tags without losing the current ones, use Wistia: Bulk Tag Media, which appends. Fields left blank are not touched. Needs a token with Read, update and delete anything.

Wistia: Update Media Customizations

wistia_update_media_customizations

Change a media's player settings. The body is an open key-value document rather than a fixed field list: a non-null value creates or replaces that setting, and an explicit null DELETES it, falling the player back to the account default. Keys you do not send are left alone. Keys are camelCase (playerColor, autoPlay, videoFoam) - this surface did not move to snake_case with the rest of the API. Read the current settings first with Wistia: Get Media Customizations if you intend to preserve anything.

Using the integration

On the automation canvas

Wistia nodes chain with every other node in the workspace. A weekly schedule can pull Wistia: Get Account Analytics Timeseries into a Mattering database and open a task when a number moves. A new video can trigger a launch checklist that runs Wistia: Update Media, Wistia: Bulk Tag Media and Wistia: Create Captions in sequence. A quarterly sweep can find stale media with Wistia: List Media and file it with Wistia: Move Media. Identifier fields are pickers sourced from the matching list node, labelled to be legible rather than merely correct: Wistia ids are opaque strings and titles repeat across folders, so the media picker shows the folder name underneath the title, and the tag picker shows how many videos a tag is applied to, which is exactly the blast radius of deleting it.

From AI assistants over MCP

Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and Matter, the assistant built into the platform, can drive the same surface. Reading is 34 of the 51 nodes and is the comfortable surface to hand an assistant: Wistia: Search and Wistia: List Media find things, Wistia: Get Media Analytics and Wistia: Get Media Stats say how they performed, and Wistia: Get Media Embed Locations says where they are used. Wistia publishes an MCP server of its own, and it is worth knowing that before choosing: we have not used it, so nothing here describes what it covers, and Wistia's documentation is the place to look. What this integration is for is unattended operations, scheduled and triggered canvas steps that chain with every other connector, with the credential held once in the workspace rather than in each person's local client config, and the destructive nodes flagged so an approval can sit in front of them.

Two reporting surfaces, and the date convention that differs

Wistia has an older stats family and a newer analytics family, and this integration carries both because they answer different questions. The stats nodes are counters: Wistia: Get Account Stats, Wistia: Get Media Stats and Wistia: Get Media Engagement for lifetime figures, and Wistia: Get Account Stats By Date and Wistia: Get Media Stats By Date for per day rows whose loads, plays and hours watched add up cleanly across periods. The analytics nodes are window first: Wistia: Get Account Analytics, Wistia: Get Media Analytics and their timeseries variants, where the bucket width is chosen per request. The convention that catches everyone is the end date: analytics treats it as exclusive, so a range ending on the last day of a month omits that day, while the stats by-date endpoints are inclusive. Ask for one day past the last day you want on the analytics nodes. Analytics also refuses a range longer than two years, and Wistia documents two years of retention on the viewing events surface.

Ranked reports you must not stitch together

Wistia: Get Account Top Content, Wistia: Get Media Embed Locations and Wistia: Get Media Traffic Breakdown look like ordinary windowed lists and are not. They sort their rows and truncate them, and the embed locations read defaults to only ten rows, so a row limit here does not merely shorten the response, it changes which rows exist. Two practical rules follow. Raise the page size before concluding that a page is not embedding a video or that a traffic source produced nothing. And never assemble a quarter by adding up twelve weekly requests: an entity that fell below the cut in one week is simply absent from it, so the total looks complete while under counting everything in the middle of the pack. Ask for the window you actually want, in one request, and treat these three as leaderboards rather than as datasets. When you need numbers that recombine, use the per day stats nodes instead. One more shape detail: the traffic breakdown names its dimension column after whichever breakdown you chose, so a downstream mapping hard coded to one breakdown will break when the breakdown changes.

Bulk writes are queued, not done

Six nodes hand back a job rather than a result: Wistia: Archive Media, Wistia: Restore Archived Media, Wistia: Move Media, Wistia: Bulk Tag Media, Wistia: Import Media From URL and Wistia: Restore Deleted Media. A success from any of them means the work was accepted, not that it happened, so a workflow that writes and immediately reads gets stale data. Poll Wistia: Get Background Job Status, which reports per item results with the error text for anything that failed, before the next step assumes anything. Two limits belong with this. Bulk endpoints cap the number of items per request, and each node's description carries its own ceiling. And Wistia: Move Media has a rate limit of its own that is far tighter than the account limit, ten requests per five minutes, so move media in batches rather than one per run.

Media, tags and the writes that replace rather than add

Wistia: Update Media and Wistia: Bulk Tag Media both touch tags and they are not the same operation: update replaces the media's whole tag set, while bulk tagging appends. Getting them the wrong way round silently strips tags rather than failing, so read the current tags first if the intent is to add one. Wistia: Import Media From URL has a similar trap in its defaults: an import with no folder named creates a new folder rather than using a default, so a scheduled import loop left unconfigured will litter the account with folders. Wistia also refuses a few sources for import, including its own domain. On Wistia: Copy Media, one field takes Wistia's numeric folder id while the move and import nodes take the hashed one, which is a vendor inconsistency rather than ours: use the picker on each node and the right kind of value is filled for you.

Player customizations and the folder naming to expect

Wistia: Get Media Customizations and Wistia: Update Media Customizations change the player itself, which is the surface a brand consistency workflow wants. This part of the API keeps the player's own naming rather than the rest of the API's, and some values come back as text even when they read like true or false, so copy a current customizations payload with the get node and edit it rather than composing one from scratch. On naming more broadly, this integration follows the product: what the Wistia interface calls a folder is a folder here, in every label and field. One place the vendor did not rename its own path is folder statistics, so Wistia: Get Folder Stats is labelled for the folder it reads even though the underlying route still uses the older word. It takes the folder id the folder pickers provide, so nothing changes in how you use it.

The four destructive nodes, gated

Wistia: Delete Media takes the video with its captions, customizations and stats history, and every embed of it on every page stops working immediately. Its recoverability is genuinely unclear: Wistia's delete reference describes the media as permanently deleted, while its deleted media reference describes deleted media as restorable for a period and ships a restore endpoint, with a shorter window documented on free plans. Do not build on either reading. Check Wistia: List Deleted Media on your own account first, and use Wistia: Restore Deleted Media only as a hope rather than a plan. Wistia: Delete Folder is documented as permanent, and Wistia does not document what happens to the media and subfolders inside, so move the contents out first and treat the delete as taking whatever is left. Wistia: Delete Tag removes the tag from every video it was applied to, so saved filters, channel rules and automation conditions matching on it stop matching, and re-creating the name does not re-apply it: the picker shows the tag's usage count for exactly this reason. Wistia: Delete Captions removes one language track, and a purchased or hand corrected transcript has to be re-ordered or re-uploaded, taking translations derived from it with it. Keep all four behind a condition or an approval task rather than a bare trigger.

Troubleshooting

Test Connection fails with a 401 error
The connection test calls Wistia's account endpoint, which needs no permission level beyond a valid token, so a failure there is about the token itself rather than about what it is allowed to read. Check for whitespace picked up in the copy, and confirm the token still exists in your Wistia account settings under API access. Wistia shows a token only once at creation, so if the value was not saved, create a new token and a new credential rather than trying to recover the old one.
Stats and analytics nodes fail while media and folder nodes work
This is the permission level rather than a bug, and it is the most common problem with this integration. Wistia tokens carry a permission level rather than a scope list, and every stats and analytics node needs Read detailed stats, which read access to media and folders does not imply. Create a token at that level, or raise the level on the existing one, and update the credential. Two neighbouring cases have the same shape: Wistia: Search, Wistia: List Tags and the webinar reads need read access to all data, and Wistia: Archive Media returns a permission error without access to Wistia's Archiving feature, which is a plan matter rather than a token matter.
An analytics report is missing its last day
The analytics end date is exclusive, so a range ending on the last day of a period covers only up to the start of that day. Ask for one day past the last day you want. The reason this is easy to miss is that the two reporting surfaces disagree: the stats by-date endpoints are inclusive, so the same range means one more day there than it does on analytics. If a report and a dashboard disagree by exactly one day's worth of plays, this is why. Note also that the analytics nodes refuse a range longer than two years.
Top content or embed location totals do not match the dashboard
Check how the numbers were gathered. Wistia: Get Account Top Content, Wistia: Get Media Embed Locations and Wistia: Get Media Traffic Breakdown are ranked and truncated, so the row limit decides which rows exist rather than just how many come back, and the embed locations read defaults to only ten rows. Two consequences. A page missing from the embed list may simply be below the cut, so raise the page size before concluding a video is not embedded there. And a total assembled from several narrower requests will under count, because an entity outside the cut in one sub period is absent from it entirely. Request the window you want in one call, and use the per day stats nodes when you need numbers that add up across periods.
A bulk write reported success but nothing changed
Wistia's bulk writes are asynchronous, so the success means queued rather than done. Wistia: Archive Media, Wistia: Restore Archived Media, Wistia: Move Media, Wistia: Bulk Tag Media, Wistia: Import Media From URL and Wistia: Restore Deleted Media all return a job, and Wistia: Get Background Job Status reports per item results including the error text for anything that failed. Add that poll between the write and whatever reads afterwards. If items are failing individually, the job status is where the reason lives, not the original response.
Moving media stops after a few videos
The move endpoint has its own rate limit that is far tighter than the account limit: Wistia documents ten requests per five minutes for it, against 600 requests per minute for the account overall. So a loop that moves one video per iteration hits the ceiling inside a minute, while every other node in the same workflow keeps running. Move media in batches within a single call rather than one per iteration, and space the batches. A rate limited response carries a header saying how long to wait, which is the value to pause for.
Tags disappeared after a media update
Wistia: Update Media replaces the media's whole tag set rather than adding to it, while Wistia: Bulk Tag Media appends. So an update that sent one tag left exactly one tag. If the intent is to add, use the bulk tagging node. If you must use the update node, read the current tags with Wistia: Get Media first and send the complete list you intend to end up with.
A scheduled import created a new folder every run
That is Wistia's documented default rather than a fault: an import with no folder named creates a new folder instead of using an existing one. Set the folder field explicitly on Wistia: Import Media From URL, using the folder picker so the right kind of id is filled. Two related notes: Wistia refuses certain sources for import, including its own domain and some other video hosts, and the import is asynchronous, so poll Wistia: Get Background Job Status to see whether the media actually landed.
A guard reading account usage limits crashes
Wistia: Get Account Usage returns its limits as empty for any token whose user is not an account owner or manager. That is a permission outcome rather than an error, so the node succeeds and the value is simply absent, which is exactly the shape that breaks a downstream expression reading into it. Check that the limits object is present before reading a field from it, or use a token belonging to an owner or manager account if the workflow depends on those numbers.
A media search returns nothing for a title I can see
The name filter on Wistia: List Media is an exact match rather than a search, so a partial title returns an empty array and looks like the video does not exist. Use Wistia: Search for text lookups, which takes a real query, and note its results come back grouped by resource type rather than as one flat list. It is also why the media pickers in this integration do not offer search as you type: a partial string against an exact match filter would show an empty picker while looking entirely correct.

Wistia is a trademark of its respective owner. Mattering uses platform names to identify the services these integrations connect to; no endorsement or affiliation is implied.

Start Free Explore our Products