Cloud Storage Sync

Dashboard integrations and the public API

VideoNest has dashboard workflows for Dropbox folder ingestion, S3-compatible bucket ingestion, and selecting individual Google Drive files. These workflows have different behavior. The scoped /v1 API does not create storage connections, configure provider credentials, or manage sync jobs.

Amazon S3 and S3-compatible buckets

Bucket credentials support an Ingest Source setting that pulls videos into VideoNest. This is separate from distributing videos to an external bucket.

1. Contact VideoNest support to configure an S3 ingestion source. Bucket ingestion settings currently require the admin credential form.
2. Enter the bucket name, access key ID, secret access key, and region. For an S3-compatible provider, enter its endpoint URL.
3. Set an optional prefix, such as videos/incoming/, to limit which object keys are scanned.
4. Enable Ingest Source and Active Status, choose the destination channel, and save.

Use source credentials that can list the bucket and read the relevant objects. Ingestion scans matching keys and imports video objects that do not already have a completed import for that channel. Existing matching objects are eligible on the first scan; there is no separate “Import existing files” switch documented here.

Recognized S3 ingestion extensions are .mp4, .mov, .mkv, .avi, .webm, .m4v, .mts, and .mxf.

Dropbox folder ingestion

1. Open the channel's upload screen and choose Dropbox from the import sources.
2. Complete Dropbox authorization and return to VideoNest.
3. Add video files directly to the channel's configured Ingest folder. The connection flow creates channel folders; use the path configured for your channel.

Dropbox ingestion lists files directly in that folder, without recursively importing subfolders. It downloads new files into VideoNest and tracks their Dropbox file IDs to avoid importing the same file again during normal sync. A channel may already have another linked sync source; the dashboard will ask you to resolve that conflict.

Recognized Dropbox ingestion extensions are .mp4, .mov, .webm, .mkv, .avi, .m4v, and .ts.

Scheduling and source changes

Provider ingestion runs through VideoNest's sync jobs. Dropbox change notifications can also queue ingestion. Connection does not promise immediate availability; allow time for transfer and processing. This workflow does not expose a user-selected real-time, hourly, or daily frequency.

These ingestion jobs import new files. They do not offer a source-delete propagation setting: deleting a source file is not an instruction to delete its imported VideoNest record. Manage imported videos in VideoNest, and keep source files available until the import completes.

Google Drive and other providers

The upload screen's Google Drive option opens a file picker. Selected files are downloaded into the browser's upload workflow; it does not monitor a Drive folder for future additions. See Importing from Cloud Storage for the steps.

FTP / SFTP import is marked Coming soon in the upload source selector. For other providers, download the files and use direct upload, or build a transfer using the public multipart upload API. Do not send a cloud file URL to POST /v1/videos; that route does not exist.