Skip to content
Aldridge Dagos Get in touch

CASE 17

Meeting Recording Archiver

Cloud recordings used to pile up and hit storage limits. Now they move themselves into dated folders every half hour, logged, and cleared from the source only once the copy is safe.

Role
Design, build, automate
Year
2026
Stack
Automation · Cloud storage
Status
Live in production

01 The problem

Cloud recordings build up fast and storage runs out. Moving them by hand is the kind of chore that gets skipped until the day a recording is lost or the account is full. By then a meeting you needed is gone and there is no getting it back. The work itself is dull and easy to forget, so it slips for weeks at a time. It needs to happen on its own, on a schedule nobody has to think about, and it needs to never delete a recording it has not safely copied first.

02 The system

An automation that archives recordings on a schedule so you never touch it. Every half hour it checks the call platform for new recordings, copies each one into a dated folder in storage, logs it, and only then clears it from the source to reclaim space. The dated folders keep everything easy to find later. A running log means it never copies the same file twice, even if it runs over an old set, and an alert goes out on each pass so you always know it ran.

03 How it holds up

The order is deliberate. It deletes from the source only after the copy is verified, gated by a confirmation step, so a failed upload never costs a recording. If the copy does not check out, the source stays put and the next pass tries again. The log is the memory that keeps it safe to run over and over without duplicating or losing anything. I hardened it with an adversarial review pass that hunted down the ways it could fail and fixed each one before it could bite. The result is something I trust to run on its own without anyone watching it.

04 The result

Recordings archive themselves into tidy, dated folders, storage stays clear, and nothing is deleted until a safe copy exists. No recording gets lost, the account never fills up, and nobody spends time on it anymore. The chore that used to get skipped now just takes care of itself.

· How it works

  1. 01

    Check for new recordings

    Every half hour it lists new cloud recordings from the call platform.

  2. 02

    Skip what is done

    A log of what is already backed up means nothing is ever copied twice.

  3. 03

    Copy and verify

    Each file lands in a dated folder in storage, and the copy is confirmed before anything else.

  4. 04

    Reclaim and log

    Only after a verified copy does it clear the source, then log the result and send an alert.

· Results

Cadence
Every 30 min
Safety
Verified before delete
Status
Live in production

1. The platform connection uses server-to-server authorization, and the log acts as the memory, so a recording is never downloaded or deleted twice.

2. The source recording is deleted only after the copy in storage is verified, with a confirmation step gating the delete and alerts on two channels.