Does your team enter the same information into several systems? DustinLabs investigates how your website, CRM, scheduling or administration can be connected. Alongside an API, import and export or another permitted method may be suitable. We record which information is exchanged and how you identify errors.
Custom softwareAn overview that suits your way of working
Possible applications
What can you connect through an API integration?
An API lets software exchange data. If there is no suitable API, we explore whether import and export or another permitted route is possible. The options depend on the systems, rights and subscriptions. These are examples of integrations we can investigate, not a list of guaranteed integrations.
01
Website to customer overview
Now
After a website enquiry, the company is entered again in a CRM or customer list.
Solution
The integration can transfer the agreed fields and create a follow-up task.
Review
We agree how duplicate enquiries, missing data and existing customers are handled.
02
Scheduling and work orders
Now
A scheduling change has to be passed on manually to another overview.
Solution
The integration can send agreed statuses and work order information to the system your team uses.
Review
We specify which system is authoritative and what happens when two users make changes at the same time.
03
Order and payment status
Now
Employees search in different systems to find out whether an order has been received and paid.
Solution
A process can link the order to a payment notification and make the status available in the customer environment.
Review
Duplicate notifications must not cause duplicate processing. We check the source and test delayed or failed notifications.
From enquiry to use
From your question to a tested solution
Map systems and data
We review the available API documentation, licences and fields you want to exchange.
Agree on the data flow
We determine the direction, authoritative source, access permissions and what happens when data is missing or duplicated.
Build and test the integration
We test normal processing, timeouts, duplicate messages and recovery after an error.
Arrange management and changes
We specify who follows up error messages, manages access and checks supplier changes.
Questions before you start
Can every application be connected?
That depends on the available access and capabilities. We check the API, import and export options, access rights and the supplier's terms. Sometimes suitable data exchange can be arranged without an API. We cannot promise an integration without suitable access or permitted data exchange.
What happens if one system does not respond?
We agree when processing is retried, which data is retained and who receives an error message. Preventing duplicate processing is also part of the design and testing.
Are changes processed in both directions?
Only when it is necessary and technically feasible. We decide which system is the authoritative source for each item of data and how conflicts are handled. An integration does not automatically have to work in both directions.
Who manages access to the systems?
We agree ownership, access and management in advance. The integration receives only the permissions it needs. Secrets are not shared on public pages or in the initial enquiry.
What if a supplier changes its API?
Such a change may require maintenance. The proposal records which checks fall within management and when a change to the integration requires a separate estimate.
