Vidalytics
Media & VideoVidalytics is video hosting and analytics built for conversion, with a customizable player, timed calls to action, and per-second retention stats. Agents upload and publish videos, manage thumbnails, pause screens, and CTAs, organize folders, and pull drop-off and timeline statistics.
What This Integration Enables
Vidalytics is not really a video host. It is a conversion instrument that happens to stream, which is why its surface is dominated by things a video host does not have: timed calls to action with display modes, pause screens keyed to stretches of the timeline, saved player settings templates for a house style, and a retention curve that reports how many viewers are still watching at each second. The interesting question here is never whether the video plays. It is whether the person watching it does the thing at the end.
FlowRunner agents upload and publish videos, fetch the embed snippet a page needs, read and write player configuration, manage desktop and mobile thumbnails separately because Vidalytics keeps them apart, place and time the prompts and pause screens, organize folders, and pull the statistics behind a drop-off analysis. The platform separates editing from publishing on purpose, and it charges API quota for the reporting endpoints while leaving the rest free. Both facts shape how an agent should behave, and the second one is why Get API Usage belongs at the top of a reporting run rather than in the error handler.
Without FlowRunner
With FlowRunner
Use Case Scenarios
The offer link changes across a campaign, once
A promotion ends and every sales video pointing at the old offer needs a new destination. The agent works back from each landing page in Webflow or WordPress by filtering List Videos on the embed GUID that appears in the page's embed code, which is the only reliable link between a page and the video it shows. It reads List Calls To Action on each, writes the new link with Update Call To Action, and stops short of publishing. The whole change set goes to the campaign owner as a single diff.
A retention curve that produces an edit list
Weekly, the agent calls Get API Usage first, since the statistics endpoints are what consume the monthly allowance and exceeding it drops the account to a reduced rate rather than failing outright. Within the remaining budget it pulls Get Drop Off Stats for the videos carrying paid traffic and finds the second where the curve falls hardest. It writes each video's title, its drop-off second, and the on-screen content at that moment into Google Sheets, and posts the three sharpest cliffs to the growth channel in Slack as a list of edits worth making rather than a dashboard nobody opens.
A variant spun up without touching the control
The team wants to test a different pause screen offer. The agent calls Duplicate Video, which copies the settings, thumbnails, calls to action, triggers, play gates, conversions, and captions into a new video in the same folder, published immediately and therefore usable straight away. It changes only the pause screen on the copy, pulls the new snippet with Get Embed Code, and hands it to the page variant in the testing tool. The control video is never edited, so a losing test costs nothing but the copy, and conversions in HubSpot can be attributed to whichever embed the visitor saw.
Human-in-Loop Highlight
Publish Video is not scoped to your change. Vidalytics separates editing from publishing, which means every unpublished edit on that video, whoever made it and whenever, sits in the same pending state and ships the moment anything publishes. There is no partial publish, no per-change approval, and no error to tell you that the settings edit a colleague made on Tuesday just went live alongside your call to action fix. Until publish runs, the page keeps serving the previous version with no indication anywhere that it is stale. So an agent changing a link on a video that is currently taking paid traffic does the work and then stops: "New offer link written to the call to action on Sales Video 3. Publishing would also ship two pending changes I did not make: autoplay switched from on to off, and the mobile thumbnail replaced. This video is running on a live ad set. Publish all three, or should I revert the two I did not make first?" The campaign owner answers. What made this safe was not caution about the edit, which was correct and small. It was that the agent read the pending state, saw what would travel with it, and put the bundle in front of the person whose ad spend was pointed at that page.
Agent Capabilities
34 actionsVideos
8- List Videos Lists the account's videos, optionally narrowed to the one carrying a given embed GUID. That filter is how a flow works back from a page to the video it is showing.
- Get Video Reads one video's details: its title, folder, duration, and publishing state.
- Upload Video Uploads a video to the account. It arrives unpublished, so a flow that stops here has a video whose embed shows nothing.
- Update Video Renames a video or moves it to another folder. Its settings, thumbnails, and calls to action are untouched.
- Delete Video Deletes a video along with its settings, thumbnails, calls to action, and statistics. Any page carrying its embed code stops showing anything.
- Publish Video Publishes a video, which is what pushes its current configuration out to the live embed. Every pending change ships together, and until this runs the page keeps showing the previous version with no error anywhere. The operation this page's human gate exists for.
- Duplicate Video Copies a video with everything attached to it: settings, thumbnails, calls to action, triggers, play gates, conversions, and closed captions. The copy lands in the same folder and is published immediately, which makes this the practical way to spin a variant for a test.
- Get Embed Code Returns the HTML embed snippet for a video, ready to paste into a page or push into a CMS. The step that makes a publishing flow end to end.
Settings
4- Get Video Settings Reads a video's full player configuration: autoplay behavior, controls, branding, sharing, and the rest. It is the shape an update expects back, so reading before writing is the safe way to change one field.
- Update Video Settings Updates a video's player configuration. The change does not reach the live embed until the video is published, and Vidalytics names these settings itself, so the read is what tells you the exact keys.
- List Settings Templates Lists the account's saved player settings templates, which is how a house style stays consistent across a library rather than being set video by video.
- Apply Settings Template Applies a saved settings template to a video. The republish field is the one that matters: with it off the template is applied but the live embed keeps the old configuration, which is the usual reason a template change appears to have done nothing.
Thumbnails
4- Get Thumbnails Reads a video's thumbnail configuration: which image or frame is used on desktop and on mobile, and how each was chosen.
- Upload Thumbnail Sets a video's thumbnail from an image URL, for desktop or for mobile. Vidalytics keeps the two separately, so setting the desktop one leaves mobile viewers on whatever was there before.
- Update Thumbnail Config Changes how a thumbnail is chosen: a still image, a clip of the video itself, or a time range from it, separately for desktop and mobile.
- Delete Thumbnail Removes a video's custom thumbnail, for desktop or for mobile, so it falls back to Vidalytics' own choice.
Pause Screens
4- List Pause Screens Lists a video's pause screens with the time range during which each is shown. A pause screen is what a viewer sees when they stop the video, which is where an offer usually goes.
- Upload Pause Screen Adds a pause screen image to a video. Several can coexist, each covering a different stretch of the timeline, which is how the offer changes with how far the viewer got.
- Update Pause Screen Timing Changes the seconds between which one pause screen is shown, without replacing the image.
- Delete Pause Screen Removes a video's pause screens: one by its GUID, or every one of them when no GUID is given. Omitting the GUID is the delete them all call rather than a no op, so flows always name the one they mean.
Calls To Action
4- List Calls To Action Lists a video's calls to action with their text, link, and the seconds between which each is shown.
- Create Call To Action Adds a call to action over a video between two timestamps. The display mode decides whether it stays visible or appears at a moment, which matters more for conversion than the timing does.
- Update Call To Action Updates a call to action's text, link, timing, or appearance.
- Delete Call To Action Removes a call to action from a video.
Folders
5- List Folders Lists the account's folders.
- Get Folder Reads one folder by id.
- Create Folder Creates a folder to organize videos in.
- Update Folder Renames a folder. The videos in it are untouched.
- Delete Folder Deletes a folder.
Statistics
5- Get API Usage Returns the account's API quota: the monthly limit, what has been used, and what is left. The operation to call before a reporting run, because the statistics endpoints are the ones that consume the allowance and exceeding it drops the account to a reduced rate rather than failing.
- Get Video Stats Returns total statistics for one video over a date range. It counts against the monthly quota, so frequent polling spends the allowance.
- Get Drop Off Stats Returns how many viewers are still watching at each second, which is the retention curve behind a where do people leave analysis. It counts against the monthly quota.
- Get Live Metrics Returns near real time metrics for a video, such as how many people are watching right now. This one is available on Enterprise accounts only.
- Get Timeline Stats Returns metrics over time for one or more videos, optionally segmented and filtered. Its limits are strict and several are plan gated: the date range cannot exceed one month, and only an Enterprise account may send more than one video, metric, or filter at all.
Frequently Asked Questions
What can FlowRunner do with Vidalytics?
FlowRunner agents can run List Videos, Get Video, and Upload Video in Vidalytics, plus 31 more actions.
Does connecting Vidalytics to FlowRunner require OAuth?
No. Vidalytics connects to FlowRunner with an API key, no OAuth flow required.
Can Vidalytics trigger a FlowRunner workflow automatically?
Vidalytics doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Other Media & Video integrations
Start building with Vidalytics
$100 in credits. No card required. Connect in minutes.