01
New contacts in your address book
After an enquiry, a configured workflow can find the contact in your connected address book and create it if needed. Later form submissions can update an existing entry deliberately.
Data Sync
Update once. Keep connected work moving.
Move customer and order data between ONE LOOP and your other software. A configured connection keeps supported information up to date without constant copying.
Here’s what you can do.
Three examples show how you can use Data Sync.
02
See orders alongside the customer
A supported shop connection brings new orders and related customer data into ONE LOOP. Your team can review purchase activity without looking up every order in the shop.
03
Keep company details current
A suitable connection can update an existing company record using new information from your other software. We define which company and which fields may be changed.
What this changes for your day-to-day work.
The practical benefits of Data Sync.
Find the right contact
A lookup can check the email address before creating or updating a record. Matching is tested against your data.
Put details in the right field
For a custom connection, we define which information goes where. Prebuilt integrations may have fixed field rules.
Find contacts more easily
A connected address-book workflow can add contacts to a suitable group, for example after a consultation booking. That makes them easier to find again.
You control the access
Each connection needs suitable account permissions. We review the requested access and connect only the systems your process needs.
Keep failed transfers in view
For configured workflows, execution history shows which steps worked. Errors can be investigated instead of leaving missing data unnoticed.
Simplified examples, not live account data.
What you need to get started.
We check the systems, permissions and supported data, then agree the direction, matching and error handling. Custom connections may require additional setup, external plans and ongoing maintenance.
Import and sync remain separate: import brings over existing records, while the configured sync processes later changes. Messages or other follow-up actions require separately defined workflows.
Availability and any add-on or usage costs are confirmed for your ONE LOOP account before implementation.
Build on it.
All Integrations features
Your questions, answered.
Is this the same as importing a CSV?
No. A CSV import transfers a selected snapshot. Syncing then processes supported changes through a configured connection. Both can be useful, but they are different operations.
Do all changes sync in both directions?
No. Direction, data types and editable fields depend on the connection. A shop might send orders to ONE LOOP without accepting changes back. Deletions are not automatically propagated either.
How quickly do new data arrive?
That depends on the trigger and connection. Some changes are sent as events; others are checked at intervals. We test the actual process rather than promising instant updates everywhere.
What happens to existing or conflicting values?
We establish the behaviour of the specific connection before starting. Some integrations only fill empty contact fields; others can replace selected values. Reliable matching and test cases cannot prevent every error, but make the rules verifiable before use.
See it with your own use case.
Let’s explore your use case and what the setup requires.
Book a demo