Tools and integrations

API integration services for ERP, CRM, accounting and shop systems

API integration services connect the business systems a company runs separately, such as the CRM, the ERP, the accounting package and the online shop, through their programming interfaces, so data moves between them without anyone retyping it. In most B2B firms the ERP sits at the centre: it holds customers, products, prices and invoices, and the other systems read from it or write to it. Systems with a ready connector we wire up through an integration platform. The rest, an ERP on a server in your office, a warehouse system nobody has documented, an internal API that appears on no connector list, we connect with an integration written for your case, and we keep it running when the vendor changes the API.

Diagram: a single AI agent wired at once into the systems a company already runs - CRM, Finance and ERP, Commerce, Team tools, Data, Integration layer. The agent reads them as one whole instead of moving data between them by hand. AI agent CRM Finance and ERP Commerce Team tools Data Integrationlayer
  • 8 connectionsthe integrations UK firms ask us about most, each with its source of truth and a plain yes or no on whether we build it
  • 6 partswhat every integration needs so it never wakes anyone at night: authentication, rate limits, pagination, retries, error queue, monitoring
  • EUR 3,500 netone week of workshop, after which you know what to connect, in which direction, and whether it is worth connecting at all

The problem

Why does an integration without a ready connector take longer than the demo promises?

A salesperson closes a deal in the CRM. Now someone creates the customer in the ERP, types the same details into the accounting package, makes a contract folder on the drive, adds a project in the task tool and posts about it on Slack. Five systems, five manual steps, the same company number retyped five times, and every one of them a chance to misspell a name or put the wrong amount on an invoice.

A connector catalogue in an off-the-shelf platform solves this quickly, as long as both systems are on the list. The trouble starts with the systems that are not: an ERP installed on a server in your office and reachable only from your own network, a warehouse system that came bundled with the building, an internal API written by a developer who has since left. Nobody built paged reads for you there, nobody counted the rate limit, and nobody worked out what happens when the token expires on a Sunday night.

Rate limits are not a matter of imagination, they sit in the documentation. Google publishes its own caps on request counts and batch sizes in the BigQuery quotas documentation, and every larger vendor has an equivalent page. Authentication works the same way: accounting and tax platforms issue their own tokens, run their own test environments and set their own access rules, and none of that fits a login and password field in a configuration wizard.

  • The same customer lives in three systems and nobody knows which record is current
  • The sync stopped on Friday and the company heard about it on Monday, from a client
  • The integration was written by someone who no longer works here and nobody knows where it runs
  • The vendor changed the API, the export died, and finance went back to pasting from a spreadsheet

Types of integration

What types of API integration are there, and how does an API integration work?

The first split is architecture. A point-to-point integration joins each pair of systems with its own connection: with two or three systems it is the simplest route, but five systems can need up to ten pairs, each with its own rules. The alternative is a middle layer: every system connects to one place where the field mappings, the queue and the logs live. In a mid-sized company that layer is often n8n or Make, in a large enterprise an enterprise service bus. An ERP with three or four systems around it usually needs a middle layer plus a few custom integrations written underneath it.

The second split is the type of API, and lists of the most common types usually mix two different things. By style, most business systems expose REST, which exchanges JSON over HTTP, older ones SOAP with XML, some GraphQL, where you ask for exactly the fields you need, and a few RPC interfaces such as gRPC. Webhooks reverse the direction: the system sends you a message the moment something changes. By who may use them, APIs are open to anyone, offered to partners only, or internal to one company. Which combination your systems have decides the route, the effort and whether real time is possible at all.

In practice an API integration works like this: one system sends the other a request with an access token, for example create a customer with this company number, or list the orders changed since 8 am, and gets a reply in an agreed format, usually JSON. Where there is no API, a scheduled CSV or XML file over SFTP or read-only views in an SQL database still do the job. Cloud systems such as HubSpot or Salesforce are reachable from the internet; an ERP on your own server is not, so we place a small service inside your network that exposes only the agreed fields.

What changes

What do you get beyond the connection itself?

  • We connect the system that is not on any connector list

    If the system speaks REST or SOAP, we go in through the API. If it does not, there is still a file export over SFTP, a read-only view in the database, or a webhook the vendor can add on their side. Which order we try them in is decided in the workshop.

    REST, SOAP, SFTP file, SQL database, webhook, ERP export: six ways in instead of one

  • Rate limits and pagination handled on our side

    The integration reads data page by page and watches its own time window so it stays under the vendor cap. After an interruption it resumes from the last confirmed record, not from the top of the catalogue.

    Paged reads, a last-modified marker, resume from the point of failure

  • The token refreshes itself

    Access sits in one place, with least privilege as the rule. An OAuth token refreshes automatically, a static key has its expiry date recorded and an alert before it stops working.

    An alert 7 days before a key expires, instead of a phone call from finance on Monday

  • A failure does not vanish and does not stop the rest

    A failed call is retried 3 times with a growing gap. If it still does not go through, the record lands in the failed operations queue with the error text attached, not in the gap between two systems.

    3 retries, then a review queue and a notification to a named person

  • Field mapping written down, not held in a developer's head

    A customer in the CRM and a customer account in the ERP are two different data models. We produce a mapping sheet: source field, target field, conversion rule, behaviour when data is missing. That sheet stays with you.

    Units, VAT rates, currencies and date formats settled in writing, before the first line of code

  • An API change at the vendor does not stop your company

    We record the API version and check response shape in monitoring. When the vendor changes a format or retires a field, you see it straight away, not after a week without invoices.

    Response monitoring and a recorded API version, so a change shows on the day it happens

Proof

Do you connect your own systems this way?

Yes. The AI agent inside our founders' agency runs on more than a dozen systems joined through APIs, including ones that had no ready connector. Below is the scale of that work, together with what the number does NOT prove.

Built for ourselves. These are not client deployments but implementations inside the founders' own companies. We say so plainly, because proof you cannot verify is not proof.

  • JustBotJustBottheir agent

    JustIdea Agency, a performance marketing agency of around 30 people

    23
    people from the company work with the agent
    38
    systems wired in permanently
    112
    processes run without a human
    475
    thousand lines of the agent’s code

    API integrations with the CRM, the task system, Google Ads, Meta, the SEO tool, Analytics, Search Console and the data warehouse. First commit 1 March 2026, today 23 people use it.

    8 of 38 systems it works in

    • Google Ads
    • Meta Ads
    • HubSpot
    • ActiveCollab
    • Ahrefs
    • GA4
    • Search Console
    • BigQuery
    Before
    Client data sat in several systems separately. Pulling it into one place meant opening one panel after another and pasting into a spreadsheet, so the report was produced once a month, because more often than that nobody could face it.
    After
    The integrations feed the warehouse and trigger operations in the connected systems on their own, on a schedule and on events. People step in where something has to be decided, not where something has to be copied across.

    64,903 operations in 30 days across systems joined by API, of which 29,854 ran without a human

And in your company

What if our system is old, or simply odd?

Four sentences come up most often when the integration has to be written from scratch, and this is how we answer them.

  • Our system has no API.

    It usually has something we can use: a file export, a batch import, database access, or a web interface behind a token. We check that in the workshop, in the documentation and with the vendor. If there really is no way in, we say so plainly and look for a different place to automate, rather than promising an integration nobody could keep alive.

  • We already run an off-the-shelf platform and it works.

    Good, and there is no reason to touch it. We write a custom integration only for the connections a ready connector does not cover, or covers without rate limits, pagination and error handling. Everything else stays where it is.

  • The vendor will not give us database access.

    And they are right, because writing straight to the database bypasses the rules the application enforces. We work through the official API, or through an account with read-only rights to named views. The scope of those rights is written down, so it can be revoked later in one place.

  • We will not agree to testing on real data.

    We test in three stages: first read-only, then writes into the vendor test environment if one exists, then writes in production on a narrow sample of tagged records. Every stage has a written rollback, and the processing terms under UK GDPR are signed before any personal data moves.

CRM
HubSpot, Pipedrive, Salesforce, Zoho
Finance and ERP
Xero, sevDesk, Fakturownia, Comarch Optima, on-premise ERP systems
Commerce
Shopify, WooCommerce, BaseLinker, PrestaShop, marketplaces
Team tools
Google Workspace, Microsoft 365, Slack, Notion, ClickUp, Jira, Asana
Data
BigQuery, Google Sheets, GA4, SQL databases
Integration layer
custom API integrations, webhooks, n8n, Make, Zapier

Which integrations we build, which system is right in a conflict, and what we leave to others

Eight connections B2B firms ask us about. The source of truth column is a decision we take in the workshop: when a record changes in both systems at once, the one named here wins.

ConnectionWhat moves, and in which directionSource of truthDo we build it?
CRM and ERPcustomer accounts with payment terms from the ERP to the CRM; a won deal as a quote or sales order from the CRM to the ERP; overdue invoices visible on the customer record in the CRMERP for billing data, CRM for the sales stage and conversation historyyes
Online shop and ERPproducts, prices and stock from the ERP to the shop; orders and invoice details from the shop to the ERPERP for price and stock, shop for basket and paymentyes: Shopify, WooCommerce, PrestaShop
ERP or shop and Xerosales invoices and customer contacts into Xero, payment status back to the CRM or the shopXero for the ledger, the source system for the saleyes
Accounting software and HMRCVAT returns under Making Tax Digitalyour MTD-compatible accounting softwareno: the return goes from your accounting software; we feed it clean data
ERP and marketplacesorders from marketplaces into the ERP, stock levels from the ERP back to every channelERP for stockyes, including through BaseLinker
ERP and a data warehousesales, margin and receivables from the ERP to BigQuery, read-onlyERPyes
A public API for your own productan API you sell or open to your customers, with a developer portal and API managementyour productno, that is product development
Machines, PLCs, MES, or replacing the ERP itselfdata from the production line, or configuring a new ERPthe MES or the ERP vendor and its partnerno: we connect to the ERP you already run

Without a source of truth two versions of the same customer overwrite each other in a loop, and the price in the shop drifts away from the price in the ERP. That is why we settle it before the first line of code, together with field mapping, rate limits and error handling. VAT rules for digital records and returns are set out in HMRC's <a href="https://www.gov.uk/government/publications/vat-notice-70022-making-tax-digital-for-vat" rel="noopener">VAT Notice 700/22: Making Tax Digital for VAT</a>.

How we work

The five stages of an API integration, from two separate systems to production

Every step ends with something you can judge before you decide on the next one.

  1. Workshop and interface audit

    We break the process into steps and check what we have to work with: API documentation, limits, versions, the authentication method, access to a test environment. With on-premise systems we also check whether they can be reached from outside at all, and on what terms.

  2. Data contract

    We produce the field mapping sheet and the decisions on sync direction, source of truth in a conflict, and frequency. This is also where the route is chosen: a custom API integration, a ready platform as the runtime layer, or both.

  3. Pilot on real data

    First read-only, then writes on a narrow, tagged sample. We look for the edge cases the documentation never mentions: duplicates, records with no VAT number, orders with items deleted from the catalogue, characters outside the Latin alphabet.

  4. Production with monitoring

    We switch on full volume together with monitoring, a failed operations queue and a notification to a named person. The old way of working stays available until the numbers from both routes agree.

  5. Maintenance and vendor changes

    After 30 and after 90 days we check what actually passed through the integration and what landed in the error queue. When a vendor changes the API or retires a field, we fix it on our side before the process stops.

Before and after

How the week changes for the person who watches the data

Before

  • The same customer created by hand in three systems, from scratch every time
  • The question whether it reached the ERP is settled by opening two panels
  • A broken sync is reported by a client, not by the system
  • How the integration works is knowledge held by one person

After

  • A record is created once and appears in the other systems on its own
  • Sync state is visible in one place, and an AI agent answers questions about it in a sentence
  • A failed operation waits in the queue with the error text and clears on retry
  • Field mapping and access rights are written down, so anyone on the team can make a change

The first records pass during the pilot. Whether the integration is stable is clear after 30 days, whether it still fits the process after 90.

For the person signing this off

What an operations director gets out of it

You stop answering the question where the current data is, because there is one place a record is created and one rule by which it reaches the other systems. A broken integration stops being a discovery a week later and becomes a notification the same day.

The second thing matters in the board meeting and on the day a developer resigns. A custom integration usually ends up as knowledge held by one person. Ours ends up as a document: field mapping, scope of access, API versions, rollback procedure. That is what stays with you, including on the day we stop working together.

  • Field mapping and conflict rules written down, independent of any one person
  • Scope of access to each system described and revocable in one place
  • A pilot on real data before full volume, with a written rollback
  • Measurement at 30 and 90 days, so the decision to extend is made on numbers

What it costs

How much does API integration cost? The workshop has a published price, the integration is quoted after it

The process workshop costs EUR 3,500 net per week, and runs from one to seven weeks. For a single integration one week is usually enough: the process is narrow and the work is writing down fields and rules. We quote the integration after the workshop, because only then is it clear how many systems are involved, whether they are documented, and whether the vendor provides a test environment.

The cost of an API integration depends on five things: the number of systems, whether the ERP runs in the cloud or on your own server, the state of the API documentation, the direction (a one-way read is simpler than a two-way sync with conflict rules) and the number of fields that need converting. We check each of them in the workshop, which is why the rollout quote comes after it, not before.

Tool costs you pay directly to the provider: the automation platform (pricing: n8n, Make), hosting, and the language model provider if an AI agent is part of the scope. No margin from us on any of it. When the integration runs on your own infrastructure, you pay nobody for it.

  • Process workshop

    EUR 3,500 net

    per week, one week is usually enough for a single integration

    A self-contained piece of work. It ends with a document that stands up without us and that your own developer could build from.

    • Interface audit of both systems: API, limits, versions, authentication
    • Field mapping sheet together with conversion rules
    • Decision on sync direction and source of truth in a conflict
    • A recommended route: custom integration, ready platform, or both
    Start with the workshop
  • Most popular

    Workshop and integration rollout

    Quoted after the workshop

    scope follows from the number of systems and the state of their documentation

    The option most companies choose. A working integration tested on your real data, with the rollout date given after the workshop, once the interfaces have been checked.

    • Everything in the workshop
    • Integration over API, webhook, SFTP or database, depending on what the system offers
    • Rate limits, pagination, token refresh, retries, error queue
    • Pilot on a tagged sample, then production with monitoring
    • Documentation and handover to your team, rollback procedure included
    Talk about a rollout
  • Integrations and an AI agent

    Quoted after the workshop

    for companies that ask about data state several times a day

    Everything in the rollout plus BOND, which answers questions about data from the connected systems in a plain sentence.

    • Everything in the integration rollout
    • An AI agent wired into the systems over the same APIs
    • Alerts on a stopped sync and on records waiting in the error queue
    • The agent goes in once the integrations run, never before
    Ask about the agent

The workshop ends with a document that stands up without us: field mapping, conflict rules and a rollout plan. If the workshop shows that a ready connector is enough, or that there is nothing worth integrating in this process, we say so plainly and the engagement ends there.

Frequently asked questions

What are API integration services?

It is the work of connecting two or more systems through their programming interfaces, so data moves between them without a person in the middle. Typical examples: a customer won in the CRM appears in the ERP, a shop order reaches the accounting package, a stock level goes back to the shop. The service covers more than the connection itself: direction, frequency, field conversion rules and defined behaviour on failure. It differs from a ready connector in being built for your specific case, including when one of the systems appears on nobody's integration list.

What are the main types of API?

By style: REST, which most business systems use today and which exchanges JSON over HTTP; SOAP, older and XML-based, still common in ERP and finance systems; GraphQL, where the caller asks for exactly the fields it needs; RPC interfaces such as gRPC; and webhooks, which push a message when something changes. By access: open APIs anyone can use, partner APIs offered to selected companies, and internal APIs used inside one organisation. An integration often combines several, for example REST for writes and a webhook for changes.

What are the five stages of an API integration?

In our work: a workshop and audit of both interfaces, a data contract with field mapping and the source of truth, a pilot on a tagged sample of real data, production with monitoring and an error queue, and maintenance with checks after 30 and 90 days. Each stage ends with something you can judge before you approve the next one.

How long does an API integration take?

The workshop for a single integration usually takes one week. We give the rollout date after it, because it depends on things that only the workshop shows: missing documentation on the on-premise side, waiting for access from the vendor, and whether the vendor offers a test environment. A date given before anyone has looked at the interfaces would be a guess.

What if our system has no API documentation?

We check what it actually exposes: batch export, file import, database views, browser traffic after login. That is usually enough to build a data exchange, though more often on a schedule than in real time. If there is no way in at all, we say so and we do not take on an integration nobody could keep alive.

How much do API integration services cost?

The only fixed price is the process workshop: EUR 3,500 net per week, and for a single integration one week is usually enough. The integration itself is quoted after the workshop, because the cost depends on things nobody knows before it: how many systems are involved, whether their APIs are documented, whether the vendor offers a test environment, and whether data moves in one direction or both. Platform, hosting and language model fees you pay directly to the provider, with no margin from us.

Who owns the integration code?

You do. The code, the configuration, the field mapping sheet and the access description stay with you, along with repository access. The integration can run on your infrastructure or in your own automation platform account. Dependence on us ends on handover day, and that is deliberate.

How does a custom integration differ from a ready connector?

A ready connector is faster and cheaper everywhere it exists and covers your case, and we will tell you so. A custom integration is for the places where no connector exists, where it ignores rate limits or pagination, where fields have to be converted between different data models, or where two sources of truth have to be reconciled.

Let us find out whether your systems can be connected

The free consultation takes 30 minutes. Name the systems that should talk to each other and say what someone retypes by hand today. We will tell you whether a ready connector exists, whether an integration has to be written, and where we would start. You do not have to share systems or documentation at this stage.

Book a free consultation

PS. If the same company number gets typed into three systems in your company today, that is exactly this problem. An integration takes those three entries and leaves one, and the workshop document stays with you even if someone else does the rollout.

Tell us your challenge

You write directly to Paweł. No spam.