Home / Product / Data exchange

Keep systems in step

Move application data where it needs to go.

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. Run each transfer as a named action that records its initiating user, affected records, mapping, and outcome.

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.

Attach each exchange to the affected record lifecycle and show its owner, action, and recorded outcome.

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.

Follow every update to completion

Turn a saved business change into a reliable next step.

When an order, customer, shipment, or ticket changes, Daptin can update the product, send the details to another service, or add a spreadsheet row and retain the result.

Diagram showing a business item change creating a follow-up sent to product automation, another service, or a spreadsheet with completed, retry, or needs-attention results. — **Follow each business change to completion**Keep the assigned account, attempt count, completion time, and concise problem details with every follow-up.Open diagram for full-size view

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

Run imports, exports, and provider transfers through named actions with explicit ownership and mapping.

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

Know the boundary

What Daptin leaves in your hands.

Define ownership, idempotency keys, conflict policy, retry behavior, and replay handling for every data exchange. Declare transfer ownership, field mappings, idempotency, retry policy, provider quotas, and recovery steps.

Understand the operating responsibility →

Build from one foundation

Move records between systems with the initiating user, field mapping, and retry policy attached.

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

Get Daptin Explore all capabilities