Skip to content
Softgenix

API Integration · Workflow Proof £350

API integrations that keep your systems in step.

When systems don't share data, people do it for them: retyping orders into the accounts, exporting CSVs, fixing records that disagree. We build integrations that move that data automatically and reliably, and that tell you when something needs attention instead of failing quietly.
Tell us your workflowHow the £350 proof works
Example: an online order, from Shopify to Xero and the warehouse
  1. Ordinary code: Order paidShopify webhook received and stored
  2. Ordinary code: Duplicate checkThe same order is never processed twice
  3. Ordinary code: Invoice in XeroCustomer matched or created
  4. Ordinary code: Pick list sentTo the warehouse system or SFTP folder
  5. Ordinary code: Stock updatedBack in Shopify and the stock sheet
  6. A person: Something failed?Alert in Slack with a retry button
  • Ordinary code
  • A person
  • Only when needed

Why it matters

Worth doing properly

Simple automations break in quiet ways. A webhook fires twice and an order is created twice. An API is down for ten minutes and a payment never reaches the accounts. Nobody notices until a customer does. Integrations that matter need to record every event, retry safely, ignore duplicates and alert a person when they cannot finish.

“Our CRM, accounts, shop and spreadsheets don't talk to each other, so we copy data between them by hand.”

The kind of message that starts these projects

What we build

Typical jobs

Two-way sync between systems

Customers, orders, products, stock and invoices kept consistent across your CRM, accounting, ecommerce and operations software, with a clear source of truth for each field.

Webhooks and events

Incoming events verified, stored before they are processed and handled exactly once, even when a provider sends the same event twice.

APIs for your own data

A documented API over your database or internal system, so partners, apps and other tools can use it with proper keys, limits and logs.

Older systems and files

CSV exports, SFTP folders, shared spreadsheets and software without an API connected through scheduled imports and exports.

Moving off Zapier and Make

Automations that have grown too tangled or too costly rebuilt as code you own, with tests, logs and no per-task pricing.

Monitoring and alerts

A searchable log of every message, what happened to it and why, with alerts to email or Slack when something needs a person.

Process

How it runs

  1. Map the data

    Which systems, which records, which system owns each field, and what should happen when two of them disagree.

  2. Plan for failure

    Rate limits, outages, duplicates, missing fields and changed formats, decided before any code is written.

  3. Build and test

    Connectors tested against sandbox accounts and a copy of your real records, so the first live run holds no surprises.

  4. Switch on and watch

    Run alongside the manual process at first, then take over, with monitoring and alerts in place from day one.

Deliverables

What you end up with

Code, accounts and infrastructure are in your name from the start.

  • Integration services running on infrastructure in your name
  • A searchable log of every event and what happened to it
  • Safe retries and duplicate protection
  • Alerts when an item needs a person
  • Documentation of each connection, field mapping and where credentials live

FAQ

Common questions

Why not just use Zapier or Make?

Often you should. For simple, low-volume connections they are quicker and cheaper. Custom integrations make sense when a failure costs money, volume makes per-task pricing expensive, or the logic no longer fits a chain of steps. Many businesses keep both.

What if one of our systems has no API?

There is usually another way in: scheduled exports, an SFTP folder, an email inbox, read access to the database, or as a last resort controlled browser automation. We will tell you which one is reliable enough for the job.

Where does the integration run?

In a cloud account in your name, so the code, credentials and data stay yours. If you would rather we keep an eye on it after launch, that can be agreed separately.

Worth reading first

Also from Softgenix

  • AI Workflows

    AI that handles the reading, sorting and drafting your team does by hand.

  • Custom Software Development

    Business software and SaaS products built around how the work is actually done.

  • MVP Development

    The first working version of a product, built to learn from real users.

Test it on your own examples first.

Tell us what comes in, where it ends up and who touches it on the way. We will reply with the scope and sample we'd propose for a £350 Workflow Proof.

Tell us your workflowWhat's included