Skip to content

Video · reads media

Video montage

AI-assembled clip (Remotion).

Video with its record beside it.

Build an agent that makes thisAll modules
Four clips, thirty seconds. Listing the sources is what makes it re-editable later.
  • Opening, shop exterioroberkampf-window-01
  • Roasting, closeatelier-roast-b
  • Cupping tablecupping-sept
  • Closing cardbrand-outro

What it does

Behaviours, not fields. Choosing between two modules is choosing between these.

One finished piece with its edit visible, rather than a library.

Listing the source clips is what makes it re-editable later.

Narrow on purpose: more than one video is a video library.

How it works

  1. 1

    One finished piece is assembled from named source clips.

  2. 2

    The sources are listed, which is what makes a re-cut an hour rather than a day.

  3. 3

    Narrow on purpose — more than one video is a video library.

  4. 4

    The segment list doubles as a shot list for the next version.

Best for

Recordings, walkthroughs, generated clips.

Not the right choice for

Anything where the video is a link, not the point.

What a row holds

Every field, and what the agent listens for to fill it — which is the difference between a page you type into and one that fills itself.

FieldTypeFilled from
SegmentrequiredtextWhat this part of the cut shows.
FromrequiredtextThe source clip, so the edit is re-editable later.
LengthrequiredtextHow long the segment runs.

What it does not do

A module chosen for something it cannot do costs more than one that was never offered.

  • CANNOT BE BUILT YET. No DataModule type embeds a player.
  • No editing. This records an edit that happened elsewhere.
  • No versioning between cuts.
  • Source clips are named, not linked, unless they are also in the media directory.

Before it works

What you have to provide, if anything.

  • Not currently possible. Use Video library, which is a gallery and renders today.
  • When it lands it needs the same iframe decision as Embeds.

In practice

A roaster making a thirty-second brand film from existing footage.

“Cut the window shot, the roasting close-up, the cupping table and the outro.”
What was said to the agent

What the agent built

A montage with four segments and their sources listed underneath.

What changed

The re-cut for a different campaign took an hour instead of a day, because the sources were named rather than remembered.

Better with

These do a different job on the same data. An agent can have all of them.

Video libraryLive

The business publishes video — tutorials, walkthroughs, recordings — and viewers need to choose between them.

Media directoryLive

A lot of images and video accumulate from many sources and the immediate need is finding one again.

Brand assetsLive

More than one person produces material and the brand keeps drifting because nobody knows which file is current.

This module cannot be built yet

An iframe is a security posture rather than a renderer: it means deciding a sandbox policy, a frame-ancestors rule and what happens when the third party is slow or gone. The CSP here already draws that line deliberately for /embed. Extending it to arbitrary owner-supplied URLs is a decision about what a customer can put on a page we serve, and that has not been made.

Questions

What data does the Video montage page use?

It reads media records the agent has collected. AI-assembled clip (Remotion). Nothing has to be imported first — the page appears once there is something to show.

Do I have to build or configure it?

No. You describe what you need in a sentence and the agent chooses the view and fills it. Custom pages exist for the cases no built-in view covers, and those are reviewed before they go live.

When is a video the wrong choice?

Anything where the video is a link, not the point. It is best for: recordings, walkthroughs, generated clips.

Does it stay up to date?

Yes. The page is a view over the data rather than a copy of it, so anything the agent learns afterwards shows up without a rebuild or a re-import.

More in Dev & automation

A key that expired three days ago and nobody noticed. That is what this page is for.

Stripe

Payments and invoices

Connected

Resend

Outbound email

Connected

Google Places

Address lookup

Key expired

Slack

Internal alerts

Not configured

API connectors

Connected live APIs.

Fourteen failures to one endpoint in a day means leads have been going nowhere.
EndpointEventLast codeFailed (24h)
/api/stripe/webhookpayment_intent.succeeded2000
/api/stripe/webhookinvoice.payment_failed2000
crm.example.com/hookagent.lead.created50214
/api/inbound/emailmail.received2001

Webhooks

Outgoing event hooks.

A price list refreshed a week ago is fine. Postcode zones from March may not be.
DatasetRowsSourceRefreshed
Trade price list412Uploaded CSV2 Sep
Stock levels188Sync, hourly38 min ago
Postcode zones6,204Uploaded CSVMar 2026
Customer list1,940Sync, nightlyToday 03:00

Datasets

Elastic uploaded data.

"Requested by 14" is more honest than a logo with no status, and it prioritises the roadmap.

Stripe

Payments

Take payment in chat, reconcile invoices

Google Calendar

Scheduling

Two-way sync of bookings

Shopify

Commerce

Read products and stock

Xero

Accounting

Push invoices

Integrations

Third-party links.

Ask for it in a sentence

You do not configure this page. You tell your agent what you need and it builds it from what it has already collected.

Build your agent free

Agents

More

👤
Profile
❓
FAQ