System integration and process automation
We connect the software you already use, so data flows between systems automatically and invoices, client details and payments no longer need retyping. We use APIs (application programming interfaces), which let programs exchange data, and webhooks, which report changes as they happen.
When to connect your systems
-
The same data is entered several times
Staff copy client and invoice details between the CRM, the invoicing system and spreadsheets. Once these programs are connected through an API, you enter a client's details only once.
-
A change in one program never reaches the other
When a status changes in one system, someone has to update the other by hand. Webhooks pass the change on as soon as it happens.
-
Your application needs to take payments
Customers should be able to pay online or buy a subscription. We connect a payment gateway such as Stripe.
-
Other applications need to check your data
We design REST APIs that other programs use to read and update your data directly.
Integrations in our projects
In the INVENTA Licenses system, we provided a REST API that VR applications use when a user signs in. On the Offer Exchange platform, we connected Stripe payments and subscriptions. After launch, we look after integrations as part of application maintenance and development.
You can order an integration on its own or as part of a new web application for your business. We explain how we quote and bill on our custom software development page.
The APIs that other programs use are built with the technologies described on our .NET and Node.js development page.
Integrations with large language models are covered on our AI integration page.
What we do
- Analysis of where data is retyped by hand in your company and how much time it takes
- Review of both systems' API documentation and a proposed way to connect them
- Integrations built on REST APIs and webhooks
- Design of your application's own API for other programs to use
- Online payments and subscriptions (Stripe)
- Automatic email and SMS notifications
- Single sign-on to the application with one company account
- Monitoring of integrations under a maintenance contract, with changes when the other party updates its API
Who it is for
- Your staff retype the same data between the CRM, the invoicing system and spreadsheets
- When a status changes in one program, the other has to be updated by hand
- You are building an application that needs to take payments or send notifications
- Your application needs to share data with other programs, for example to check accounts and licences
Every integration starts with the API documentation
Before we give you a price, we review the API documentation of both systems, their limits and their authentication method. If a program has no API or data export, or its documentation is incomplete, we tell you at this stage.
- Which data flows, when and in which direction
- API limits and authentication checked up front
- Edge cases and error handling tested in a test environment
REST API for external applications
The INVENTA Licenses system provides a REST API to VR applications running on Windows. When a user signs in to an application, it connects to the API and receives details of their account and licence validity. User data lives in one system, and every application draws on it.
- API available to programs outside the web application
- Account and licence checked at sign-in
- Single source of user data for many applications
Automations we built for ourselves
In our own tools, a new deal in HubSpot triggers client onboarding through a webhook. Data from Fakturownia, a Polish invoicing service, flows into HubSpot, time reports come from Jira, and company details are pulled from the Polish National Court Register (KRS).
- A CRM webhook starts the next steps with no manual work
- Invoicing data reaches the CRM without retyping
- Company details fetched automatically from the KRS register
How we work
-
Process review
We map out which data should flow between your systems, when and in which direction, and point out what can be automated straight away.
-
Feasibility check
We analyse the API documentation, limits and authentication of both systems. If one of them has no API, we tell you at the start.
-
Build and test
The integration is built in a test environment, where we check edge cases and error handling.
-
Go-live and monitoring
We launch the integration in production and check that data flows correctly. Under a maintenance contract, we keep an eye on it from then on.
Pricing
We do not have a price list, because every integration has a different scope. We give you a price once we have reviewed the API documentation of both systems.
- System integration
- Price depends on: the other party's API documentation, volume of data exchanged, error handling, testing.
Experience
- We built the REST API that INVENTA Licenses provides to VR applications.
- The Offer Exchange SaaS platform takes payments and manages subscriptions through Stripe.
- In our own tools, we connect HubSpot, Fakturownia, Jira and Microsoft 365, among others.
Case studies
-
INVENTA Licenses
A system for managing users and licences for VR applications used in staff training, with portals for clients, distributors and administrators.
Frequently asked questions
Do you integrate systems that have no API?
First we check what the program allows. If it has no API or data export, we tell you before any work starts and suggest another solution.
What is an API?
An API is the way a program lets other systems read and write its data without a person in between. It is what allows a CRM, an invoicing system and an online shop to exchange data on their own.
What is a webhook?
A webhook is a notification that one system sends to another as soon as something changes, for example when a new deal appears in the CRM. The second system does not have to keep checking for new data. It simply carries out the next step straight away.
Can I order an integration without building a new application?
Yes. You can order an integration on its own, for software you already use, or as part of a new web application.
What happens when the vendor changes its API?
We monitor integrations covered by maintenance. When the other party changes its API, we adapt the connection under the maintenance contract.
Do you integrate medical systems?
Medical system integrations (HL7, Poland's P1 e-health platform, hospital information systems) are handled by the Conetso Healthcare team. If your integration involves a hospital, clinic or diagnostic centre, we will put you in touch with them.
How much does system integration cost?
It depends on the other party's API documentation, the volume of data exchanged, error handling and the scope of testing.
See also
-
Custom web applications for businesses
We build systems for handling orders, quotes and purchases, with separate portals for clients, staff and managers.
-
SaaS platforms and MVPs for startups
We build first product versions (MVPs) and SaaS platforms with user accounts, subscriptions, payments, licences and APIs.
-
Web application maintenance and development
On a monthly plan, we add new features, install security patches and look after the server. Response times are set out in an SLA.
-
Conetso Healthcare
Healthcare IT systems
The Conetso Healthcare team handles HIS, RIS, PACS and P1 integrations.