Vizard Agent

How to make an event promo when the footage arrives as a share link

Last updated 2026-08-18 · 6 min read

Send Vizard Agent the link where your footage lives, even when it is a review platform rather than files. Vizard Agent works out how to reach the actual assets behind the share page, downloads them, and builds the promo to your campaign brief once it has the material in hand.

What is the short version?

In most real productions the footage does not arrive as files. It arrives as a link to a review platform, and getting from that page to something you can actually edit is a job in itself that happens before any editing begins.

  1. Go to Vizard Agent and paste the link the footage lives behind.
  2. Paste the campaign brief: the event, the date, the names, the rules.
  3. Say the length, the feed and what has to appear on screen.

What do you need before you start?

The link and the brief. Vizard Agent will work at the link until it either reaches the assets or can tell you it cannot, and the brief is what turns a pile of retrieved footage into a promo with a date and a call to action on it.

What do you type into Vizard Agent?

Paste the brief as written and give the link. Vizard Agent reads a campaign document as a document rather than needing it rewritten, and the retrieval problem is something it works on rather than something you have to solve first.

Prompt

[link] Make a [60] second vertical promo for [event] on [date]. [Paste the campaign brief.]

Variants worth knowing:

What does Vizard Agent actually do?

Here is the order Vizard Agent worked in on a real event promo. The whole first stretch of the run is retrieval, and it is included here because it is the honest picture: fifteen steps failed before the footage was in hand.

  1. Inspects the provided footage link and tries the download tool on it.
  2. Downloads the share page itself and looks for video links in it.
  3. Queries the platform's API for the shared assets.
  4. Follows the short link's redirect to find where it actually points.
  5. Fetches the presentation data behind the share page.
  6. Inspects the page markup and searches it for endpoints.
  7. Finds the script bundles and scans them for the API the page itself uses.
  8. Works out the query the page sends and the headers it sends with it.
  9. Uses that route to reach the assets, then downloads them and starts the edit.

Steps 2 to 8 are what "the footage is behind a link" actually costs. Vizard Agent did not report that the link was not a file and stop; it worked out how the page gets its own video and used the same route.

What does the result look like?

From the run this page is written from, probed on the delivered file: 1080x1920, H.264, 30fps, 73.52 seconds, AAC audio. Vertical, just over a minute, cut from the retrieved footage with the campaign's dates and details on screen.

A minute is long for a promo and right for this one. An event promo has to carry a date, a channel, two names and a reason to watch, which is more information than a thirty-second cut can hold at readable speed.

Vizard Agent keeps everything it retrieved, which is why the expensive half of this job happens exactly once no matter how many cuts you ask for afterwards.

The retrieval happens once. Every later cut, every corrected card and every alternate length comes out of the same downloaded assets rather than another pass at the share page.

When does this not work well?

Retrieval is the part of this job that either works or does not, and it depends entirely on how the footage was shared with you in the first place. Vizard Agent works at it persistently rather than giving up on the first failure, and there are share setups that nothing short of an export will get past.

How do you fix a result that came back wrong?

Say what to change. Vizard Agent keeps everything it retrieved from the share link, so revisions never repeat the retrieval work, and a new cut or a corrected date card is built from material that is already sitting on disk.

How does Vizard Agent compare to doing it yourself?

By hand this is emailing the person who sent the link to ask them to export the files, waiting a day, getting a transfer that expires in seven days, downloading forty gigabytes, and only then starting the edit.

By hand Vizard Agent
Getting the footage Ask someone to export it Works through the share page itself
A failed attempt Give up and email again Reads the failure and tries another route
Revisions Re-download Footage already in hand
A second cut Re-import everything Re-paced from the same assets

Common questions

What if the link needs a password? Give it in the brief. Without it Vizard Agent has no way to reach the assets behind the page.

Does it work with any sharing platform? Vizard Agent works through whatever the page itself uses to load its video. Some setups are genuinely closed, and then an export is the answer.

Is exporting the files better? Yes, when you can. It removes the whole retrieval problem and gets to the edit faster.

Can it handle a large amount of footage? Yes. Vizard Agent reviews everything it retrieves before cutting rather than working from whichever file arrived first.

Will the campaign dates be on screen? If you ask. Say so explicitly, since a date in the caption disappears when the video is reposted.

How long should an event promo be? Around a minute when it carries several facts, and shorter when it only has to set a mood. Vizard Agent paces the detail cards to be readable either way.

Can it add commentary? Yes. Vizard Agent can cast a voice and write the read, or leave it to music and text.