Media integration

Bynder + Sequel

Send finished event media into your Bynder DAM automatically, carrying the metadata of the event it came from.

Every recording, clip and audio file in your DAM, with no manual downloads or re-uploads.

Bynder is where your brand's approved assets live. Event media usually is not. Recordings get downloaded out of one system and re-uploaded into another, arriving with system-generated filenames and none of the context that makes them findable six months later.

Connect Sequel to Bynder once and that step disappears. When Sequel finishes producing a session recording, an AI clip or AI audio, it pushes a copy into your DAM automatically, named and tagged the way your taxonomy already expects.

What you can do

Bynder and Sequel, connected

Recordings, clips and audio, delivered on production
Named to your convention, not ours
Tagged with the event it came from
Playback never moves

What lands in your DAM

Media types: session recordings, AI clips and AI audio. Take all three or any subset.

Timing: delivery is automatic and near real-time, triggered as each asset finishes processing. There is no queue to run and no export to remember.

Organisation: Bynder's asset bank is not a folder hierarchy. It organises by brand, metaproperties, tags and collections, and Sequel can set all four at upload, mapped onto the metaproperty scheme you already use. Where a required field has no natural Sequel equivalent, it can be set to a fixed default instead.

Filenames are permanent, so you define them

Bynder keeps the original upload filename for the life of the asset. The title can be edited afterwards, but the original persists and is what downloads resolve to, which makes the name sent at upload effectively irreversible.

Sequel's internal filenames are system identifiers. They are fine for storage and wrong for a governed DAM, so the connector never sends them. You define a template and Sequel renders it at upload time. A template of {{event-date}}_{{event-name}}_{{asset-type}}_{{sequence}} produces 2026-09-14_q3-provider-summit_recording_01.mp4, with the extension appended from the asset's real format.

Separator, casing, maximum length and character policy are all yours to set, recordings, clips and audio can each use a different pattern, and a name that would collide with an existing asset gets a numeric suffix rather than overwriting it.

Hosting and security

Sequel keeps hosting and streaming every event from its own CDN. The Bynder copy is additive, so removing or reorganising an asset in Bynder does not affect playback, and vice versa. Attendees see no difference: this is back-office content delivery, not a change to the player.

Bynder credentials are stored encrypted in Sequel and used only to upload to the destination you configure. We recommend a least-privilege token scoped to asset creation in the target brand. All transfers run over HTTPS, and credentials can be rotated at any time.

Two-way, when you want it

Sequel can also watch designated Bynder collections and pull supported media back into Sequel's Media Hub, so assets curated in Bynder can be attached to events without re-uploading them. Supported inbound formats are MP4, MP3, JPEG, PDF and PPT/PPTX. This is scoped separately from the outbound push.

Also connects with