Home / Product / Data exchange

Keep systems in step

Move application data where it needs to go without losing who the work belongs to.

Run controlled synchronization around record changes, using an explicit account and optional outside-service connection.

See what it changes Technical guide ↗

Data exchange in a product

A record is about to changeCreate, update, or synchronize

Exchange with the other systemSend or receive the relevant data

Continue with shared contextKeep the acting user and product record visible

Synchronization stays part of the application path

01Connect change to synchronizationRun exchange work before or after selected record operations.

02Keep identity in the flowChoose the account that represents the synchronization.

03Reuse delegated accessUse an OAuth connection when the outside system requires it.

Why it matters

Synchronization becomes fragile when nobody can say which product event caused it.

A customer record changes and another system needs the update. Or an outside source should enrich a record before it is saved. Standalone scripts can move data, but they often lose the original user, product context, and failure boundary.

Daptin data exchange attaches synchronization work to selected resource operations. It can run before or after the change, under an explicit account, and carry a delegated provider token when needed.

That keeps the exchange connected to the record lifecycle and makes its responsibility easier to understand than an unrelated background script.

Put synchronization near the change

Connect outside movement to the resource operation that gives it meaning.

Keep responsibility explicit

Know which account context the exchange uses.

Choose the right moment

Run before a change when outside data is required, or after it when the product should publish a result.

How it fits

Part of one connected backend.

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

Step 1Observe

A selected create, update, or other operation reaches the exchange point.

Step 2Identify

Load the chosen user and any delegated token.

Step 3Exchange

Send or receive the configured data.

Step 4Continue

Proceed with the product operation and its normal response or events.

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.

Customer enrichment

Bring approved provider data into a customer record during onboarding.

System-of-record update

Publish a completed product change to an external business system.

Two-way catalogue sync

Receive outside updates and send local changes through deliberate boundaries.

Connected by design

Build the next part without starting over.

These capabilities share the same application context, so each one makes data exchange more useful.

Know the boundary

What Daptin leaves in your hands.

Data exchange is not automatically conflict-free or exactly once. Define ownership, mapping, retries, replay safety, provider limits, and what happens when the outside system is unavailable.

Understand the operating responsibility →

Build from one foundation

Make data exchange part of the product—not another disconnected service.

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

Get Daptin Explore all capabilities