Connecting S3-compatible storage
- Contact us through our support page with the endpoint and region you want to use, and we'll enable S3-compatible storage on your account.
- Create a bucket, and an access key limited to it. RecordFlow needs to put objects, read back what it wrote, and list the prefix it owns — nothing else, and nothing outside the bucket you name.
- Send us the endpoint, region, bucket and key. There is no folder picker: the bucket you name is the destination.
Where your recordings land
The bucket you name, under one prefix per year and one per meeting — for example 2026/2026-05-30-1430-Weekly sync/. Object keys mirror the folder layout the file destinations use, so a bucket stays browsable in your provider's console.
What gets archived
- The video recording
- Audio-only recording
- Transcripts — the raw .vtt and a readable .docx
- Chat log
- AI Companion transcript and meeting summary, where your Zoom plan produces them
Deleting the Zoom original after archiving
Supported. Turn on auto-delete in your RecordFlow settings and the Zoom copy is removed once the archive is confirmed. S3 returns an ETag for every object it stores, which RecordFlow checks against what it uploaded before anything is deleted from Zoom. For objects large enough to need a multipart upload the ETag is not a whole-object MD5, so those are verified by size instead — the same check OneDrive uses.
If something isn’t working
- My recordings aren't syncing — Usually a cloud-vs-local recording mix-up — check this first.
- Where are my recordings? — Google Drive, OneDrive, Dropbox or YouTube — pick yours and see exactly where files land.
- Your storage is full, so recordings stopped arriving — Recordings wait safely in Zoom and sync automatically once you free up space.
Other destinations
One destination per account, and you can switch at any time — recordings already archived stay where they are, only new ones move.