Integrations
Connect the platforms your business runs on, reliable, monitored integrations instead of rekeying and fragile automation chains.
Superstack provides API integration services NZ businesses rely on to connect software systems that were never built to talk: Your accounting software to the job system, the CRM to accounting, the online store to the warehouse. If your team rekeys data, or a Zapier chain broke again, you get integrations that keep working and tell you when they need attention.
connected once, broken quietly
API integration services that keep working
Connecting two systems once is easy. Keeping them connected through password changes, API updates and a bad record at midnight is the real job. We build each integration as documented software you own, with retries, monitoring and a log of every record that moved.
01 of 8
Before any code, we sit with the people who do the rekeying and map every field that moves: which system owns the customer record, and what a job is called in each one. A distributor usually finds the same product coded differently in each system. The map becomes the spec.
02 of 8
Each connector handles one platform's login, rate limits and quirks, so nothing else has to. Your accounting software connector refreshes its tokens and backs off when your accounting software says slow down. When a job is marked complete, it creates the invoice in your accounting software with the right contact and account codes, then writes the number back.
03 of 8
Some updates cannot wait overnight. When a customer pays through Stripe, the webhook fires within seconds and the job is marked paid before the technician has left the driveway. Where a platform has no webhooks, we poll instead, and tell you which pattern each integration uses: one-way, two-way or event-driven.
04 of 8
Every record passes through a middle layer we control, instead of one system talking straight to another. It translates fields, queues records when a platform is down, and replays them once it is back. When a Shopify sale creates hundreds of orders, the queue feeds the warehouse at a pace it can take.
05 of 8
Integrations fail in boring ways: a token expires, a record has no email, a platform times out. A failed record retries, and one bad record never stops the batch. If a HubSpot contact has no matching accounting customer, the integration follows your rule: create one, or park it for a person to check.
06 of 8
Every integration reports in. A dashboard shows each connection, records moved and records waiting. If a sync fails and retries do not clear it, the right person gets an email or Slack message saying what failed, which record, and what to do. You hear it from the system, not the accountant.
07 of 8
Each integration comes with a plain-language document: what it connects, which fields map to which, how often it runs, what each error means and who to call. When your office manager asks why a accounting contact changed, the answer is in the document, not in a former developer's head.
08 of 8
Platforms change their APIs. Your accounting software retires an endpoint, Shopify changes a webhook format, a token policy tightens. We watch for these announcements, update the connectors before the change lands, and test afterwards. Support is an ongoing arrangement, so when something changes on a Tuesday, someone who knows your integration is already on it.
Take a paid invoice. Your accounting software fires a webhook when the payment is applied. The middleware receives it, finds the matching job, translates your accounting software's fields into the job system's, and marks the job paid. The log records the result. If the job system is offline, the record waits and retries. If it still fails, the office manager gets an alert naming the record. A person only steps in when the system asks.
your accounting software and MYOB exchange invoices, contacts and payment status. Stripe and GoCardless mark invoices paid. Twilio and SendGrid send SMS and email. Google Workspace and Microsoft 365 sync calendars. Shopify and WooCommerce pass orders to fulfilment. HubSpot and Salesforce share contacts and deals, Slack and Microsoft Teams receive alerts, and legacy APIs get their own connector.
Any system with an API connects. Click a logo to visit them.
Xero
MYOB
Stripe
Google Workspace
Microsoft 365
Twilio
Shopify
HubSpotAI is optional, and most integrations run without it. We add it only where a rule cannot do the job. See how we use AI and business process automation.
AI drafts the first field mapping from each platform's data, and a person confirms it.
An incoming order or enquiry gets tagged by type and urgency in the middleware, so it lands in the right queue.
A weekly note in plain words: what ran, what failed, what was fixed and what needs a decision.
Your office manager uses the web app as the integration console: every connection, its last run, records waiting, records that failed and why. They fix a bad record and hit retry, without calling a developer.
Alerts reach the responsible person's phone, so a failed sync on a Saturday is a quick fix, not a Monday surprise. Staff apps we build use the same connectors, so a technician sees accounting invoice status on the job card.
Often the portal is why the integration exists. Customers log in and see accounting invoices, Stripe payments and Shopify order status in one place. All three share one database, so a customer sees the record your team sees.
A services company with a CRM, a job system and your accounting software is the classic case.
TradesJob management to your accounting software, supplier invoices and timesheets included.
Retail and e-commerceShopify or WooCommerce orders into stock, fulfilment and your accounting software without rekeying.
DistributionOrders, stock and pricing kept in step across the store, warehouse and your accounting software.
Professional servicesCRM, timesheets and invoicing linked, so a won deal becomes a project.
SaaSCustomer-requested integrations, built and supported so your developers stay on the product.
Quickest start
We customise an existing Superstack connector, such as your accounting software to a job system, with your field mapping, rules and alerts. It suits a single, well-understood connection.
Most common
We combine several connectors with middleware, queues and a monitoring console into one integration layer, the usual shape of the system integration services NZ businesses with three or more platforms need.
Fully bespoke
A fully bespoke integration platform for legacy software, unusual data or a SaaS product that needs integrations its own customers will use.
Any platform with an API, and most without one. The common request is to integrate your accounting software with other software: a job system, a CRM, an online store or a booking tool. We have connectors for your accounting software, Stripe, GoCardless, HubSpot, Salesforce, Shopify, WooCommerce, Twilio, SendGrid, Google Workspace, Microsoft 365, Slack and Teams, and we write new ones for industry software.
Yes. A two-way sync keeps a record matching in both systems. A customer's address updated in the CRM flows to your accounting software, and a change in your accounting software flows back. We set a rule for conflicts, such as the CRM wins for contact details and your accounting software wins for payment status, so the two never fight. If one direction is enough, we say so.
We find another way in. Most software without an API still has scheduled exports, a database we can read or a web interface we can drive. A custom API integration for an older system usually reads a nightly export and writes back through whatever the vendor supports. It is slower than a webhook, but it still removes the rekeying.
Reliable enough that you stop thinking about them. Every record passes through middleware that retries failures and never lets one bad record block the rest. A dashboard shows each connection's last run. If a failure survives the retries, the person you nominate gets an email or Slack alert naming the record. You hear it from the system, not from a customer.
As a fixed price per integration, agreed after discovery. The cost depends on how many systems are involved, whether the sync is one-way or two-way, how messy the data is, and whether the platform has a decent API. Unlike Zapier, there is no per-task fee that grows as your volume does. Ongoing support and monitoring are a separate arrangement.
Yes. Support is the part most people skip, and it is where integrations die. Platforms change their APIs and tokens expire, so we monitor every integration we build, apply platform updates, and fix issues the alerts raise. We are an API integration company that stays around after go-live, with documentation written so another developer can take over if you ever want them to.
Built around the way you work.
Your business shouldn't have to fit someone else's software. Tell us how your business works. We'll show you what Superstack can build around it.
List the systems that should talk to each other. We'll map the integrations and tell you which to do first.
We use cookies to see which pages help people. Nothing runs until you say yes. Read the privacy policy.