Connect systems via API: software that talks to each other
You connect systems with a workflow that reacts to events such as a new customer or order, fetches the data from the source system via API, maps fields and formats and reliably transfers it to the target system, with retries on errors and a log of every transfer. Your team resolves contradictory data. In the worked example with eight connected endpoints it saves about 23 h a month.
- Time saved in the worked example
- approx. 23 h per month
- Delivery
- 7 to 12 working days
- Typical systems
- Shopify, WooCommerce, HubSpot
- Fixed price
- from €990
, Rouven Jahnke
Flow: Connect systems via API
5 steps-
Event occurs
New customer, order, status change
-
Fetch data
From the source system via API
-
Translate
Map fields, formats, ID schemes
-
Transfer
To the target system, with retries
-
Resolve conflicts
When data contradicts itself
Green runs automatically. Orange is decided by a person.
Where time gets lost today
- Data is copied between programs
- Systems contradict each other
- Old integrations fail silently
Most small companies use five to fifteen programs today, and each does its job well. They just don’t talk to each other. So customer data is copied from shop to CRM, orders from CRM to accounting, stock from inventory to shop.
Where connections exist, they are often one-off solutions from the past: a script, a plugin, an export meant to run nightly. When it fails, nobody notices until the data is wrong.
How the automation works
First we clarify which data should flow from where to where and which system is the source of truth for which information. It sounds trivial but it’s the most important step, otherwise two systems keep overwriting each other.
Then the workflow handles the transfer: it reacts to events like a new order or polls for changes at set intervals, maps fields, formats and ID schemes and writes the data to the target system. Failed transfers are retried; if they keep failing, someone is notified.
Every transfer is logged. You can always see what was sent where and when, and the integration is documented visibly in n8n instead of hidden in a script.
What your team still decides
When data contradicts itself, for example a customer address changed differently in two systems, your team decides. You define upfront which system leads for which data.
Calculate your savings
Adjust the values to your company. The calculation runs only in your browser; nothing you enter is transmitted.
- Working time saved per month
- – h
- Savings per month
- –
- Savings per year
- –
Excludes running costs for hosting and AI usage. You receive the implementation cost as a fixed price after the intro call.
Formula
Hours saved/month = (Endpoints x Syncs/day x 22 x 1 min + Endpoints x Error handling) x Automation rate / 60
Worked example
The calculator above starts with these assumptions. They are example values, not averages from studies.
- Managed API endpoints
- 8
- Data syncs per day
- 8
- Error handling time per endpoint/month
- 30 min
- Share of work automated
- 85 %
- Labour cost per hour (fully loaded)
- 55 €
Result: about 23 h less manual work per month, roughly €1,280 a month or €15,400 a year.
Before and after
| Aspect | Today, by hand | With the workflow |
|---|---|---|
| Data flow | Copying between programs | Automatic on every event |
| Consistency | Systems contradict each other | One source of truth per item |
| Errors | Fail silently | Retries and alerts |
| Documentation | In someone’s head or a script | Visible in the workflow, logged |
Frequently asked questions
What if a program has no API?
There are often alternatives: file exports and imports, email notifications, database access or webhooks via middleware. As a last resort a user interface can be automated, but that is more fragile.
Why n8n rather than custom code?
n8n makes integrations visible and understandable to others, brings error handling and logging, and can be self-hosted. Where n8n reaches its limits, I add custom code selectively.
What happens when an API changes?
Vendors change their APIs occasionally. Monitoring notices failing transfers immediately. Adjustments are covered by post-launch support or a maintenance agreement, depending on what we agree.
How many systems can be connected?
Technically almost any number. It makes sense to start with the connection that causes the most manual work today and expand step by step. Each fixed price covers a clearly defined data flow.
What does this workflow cost and how quickly is it live?
Implementation is a fixed price from €990; the exact price is set after the free intro call and depends on the number of connected systems and exceptions. Typical delivery time for this workflow: 7 to 12 working days. Running costs for hosting and, where used, AI usage are quantified in the proposal.
Connect systems via API: free intro call
Describe a process that eats time today. I’ll tell you honestly whether automating it pays off, what it would look like and what it costs.
- We walk through your process together, ideally on screen.
- You learn which step has the biggest leverage and what it takes.
- You receive a fixed-price proposal within 48 hours. No obligation.
Pick a time in the calendar
Loading calendar…
Thanks, your message arrived.
You’ll get a confirmation email. I’ll reply within 24 hours.
Your reference number: