Home / Product / Storage synchronization

Keep content available

Bring stored content into the product—and keep published surfaces current.

List, upload, move, remove, import, and synchronize content through backend operations that understand the connected store.

See what it changes Technical guide ↗

Storage synchronization in a product

Content changes somewhereA file arrives, moves, or is replaced

Run a storage operationImport, synchronize, rename, or remove

Refresh the product viewRecords and hosted content see the intended state

Storage changes become managed product work

01Manage content through one backendRun named copy, move, and synchronization actions with stored credentials and record ownership.

02Import files into application contextTurn stored objects into records people can use.

03Refresh sites and caches deliberatelySynchronize content where published surfaces depend on it.

Why it matters

Files drift when storage is treated as a folder nobody owns.

A teammate uploads a new asset, an object moves, or a published site needs the latest build. Run named synchronization actions that update storage content and its related records together.

Daptin provides storage actions for listing, uploading, moving, deleting, creating folders, importing files into records, and synchronizing connected site or asset storage.

Each synchronization job uses a stored credential, a named action, an optional schedule, and a recorded result.

Give storage work a clear operation

Make import, move, delete, and synchronize explicit actions.

Connect objects to records

Bring provider content into the application model when it needs ownership and metadata.

Automate recurring refreshes

Schedule synchronization through the same action system.

How it fits

Part of one connected backend.

Storage synchronization does more when it can reuse the records, people, access rules, and workflows already in your application.

Step 1Connect

Choose the cloud store and protected credential.

Step 2Operate

List, upload, move, remove, or import content.

Step 3Synchronize

Refresh the local or published representation.

Step 4Observe

Monitor synchronization completion, provider quotas, cache age, and content freshness.

What it enables

Use it in products people recognize.

Start from the experience you want to create; the backend capability supports the work behind it.

Publish a site build

Synchronize a new frontend bundle into the configured site root.

Import an asset library

Create application records from provider-held files.

Organize customer content

Move and rename objects through a permissioned backend operation.

Connected by design

Connect credentials, actions, schedules, sites, and record ownership around each synchronization job.

These capabilities share the same application context, so each one makes storage synchronization more useful.

Know the boundary

What Daptin leaves in your hands.

Define source ownership, completion checks, conflict policy, cache invalidation, monitoring, and recovery for each synchronization job. Declare source ownership, deletion and conflict rules, cache invalidation, and completion checks for each refresh.

Understand the operating responsibility →

Build from one foundation

Run named copy, move, and sync jobs with stored credentials, schedules, and completion records.

Run Daptin locally, explore the live administration surface, and follow one complete application path.

Get Daptin Explore all capabilities