- Most app connections follow one pattern: when something happens in one app, do something in another.
- Map how information moves through your business before connecting anything.
- Decide which app is the source of truth for each type of information, and only edit it there.
- Every connection needs a named person who is alerted when it fails.
- A well-kept spreadsheet is fine for small volumes. Connect apps when the retyping becomes a weekly cost.
Why the same job gets typed into three systems
Picture a Monday morning at a small homewares shop. An online order came in overnight. Someone copies it into the packing spreadsheet, then creates the customer in Xero, then types the sale in again so the books match.
Nobody planned it that way. Most small businesses didn't choose their software all at once. The accounting software came first, then an online store, then a booking app, then a spreadsheet someone set up to track jobs.
Each tool does its own job well. The trouble is that none of them knows what the others are doing.
So people fill the gaps. A job is booked by email and someone creates the customer in Xero. A supplier invoice lands in Outlook and someone keys it into the accounting software.
Each step only takes a little while, but they happen all day. And every retype is a chance for a typo, a missed order or an invoice that never goes out.
You're not alone. On our home page we describe this as "no more retyping the same job into three systems." Copying details between two systems turns up in almost every industry.
How app connections work: when this, do that
Almost every connection between two apps follows the same simple pattern: when this happens here, do that over there. There are three parts to it.
Triggers
A trigger is the event that starts things off. A new order in your online store, a form submitted on your website, or an email arriving with an attachment.
It could also be a quote marked as accepted, or a new row added to a spreadsheet.
Actions
An action is what happens as a result. Create an invoice, add a customer, send a message, update a row or save a file to a folder.
One trigger can lead to several actions in a row.
Matching records
This is the part that takes the most care. When an order arrives, the connection has to decide whether this customer already exists in your accounting software or needs to be created.
It usually matches on something unique, like an email address or customer number. Get matching wrong and you end up with three versions of the same customer, which is worse than retyping.
Apps talk through doors called APIs. An API is a way for one app to let another app read or write information, with your permission. You'll hear the word a lot. All you really need to know is that most modern business software has one, and that's what makes connections possible.
Map your data flow before you connect anything
Before connecting anything, draw how information moves through your business today. A whiteboard or a sheet of paper is fine.
- List your apps. Everything that holds business information, including spreadsheets, shared inboxes and paper forms.
- Follow one job from start to finish. Where does the first enquiry arrive? Where is it booked, quoted, delivered, invoiced and paid?
- Mark every retype. Each time a person copies information from one place to another, draw an arrow. These arrows are your candidates for connection.
- Note who does each step. The person doing the retyping usually knows exactly where it goes wrong.
- Pick the busiest arrow. Start with the copy that happens most often or causes the most mistakes.
Your map is also handy for deciding what to automate first, because it shows where the effort really goes.
Useful app connections for NZ small businesses
Here are common connections between tools many New Zealand businesses already use. Each one swaps a manual copy for an automatic one.
The tools we connect are Microsoft 365, Google Workspace and Xero. Where another system is involved, such as an online store or point-of-sale, we work from the emails or Excel and Google Sheets exports it already produces, rather than connecting to it directly.
| When this happens | This happens automatically |
|---|---|
| An order confirmation email arrives from your online store | A packing row is added to Google Sheets, and the sale is recorded in Xero |
| A supplier invoice arrives in Gmail or Outlook | The details go into Xero as a draft bill for checking |
| A customer accepts a quote | A draft invoice is created in Xero with the approved line items |
| A website enquiry form is submitted | The contact is added to your customer list in Excel or Google Sheets and the right person is alerted by email or in Teams |
| Your point-of-sale system emails its end-of-day sales report | A summary is added to an Excel or Google Sheets file and sent to the owner's phone |
Notice the word "draft" in a couple of those rows. A person still checks the bill or invoice before it's final.
Want to see one of these end to end? Our guide to automating quotes and invoices walks through it. And the weekly business numbers guide shows how connected apps can feed a single summary.
Keep one source of truth for your data
When apps are connected, the same information can appear in several places. That's fine, as long as everyone knows which app is in charge of it. This is called the source of truth.
For example, you might decide that:
- Customer contact details live in your customer list, such as an Excel or Google Sheets file.
- Invoices and payments live in your accounting software.
- Stock levels live in your point-of-sale or online store.
- Bookings live in your booking app.
The rule is simple: change information only in its source of truth, and let the connections carry the change everywhere else.
Say someone updates a customer's phone number in the accounting software instead. The next sync may overwrite it, or you end up with two numbers and no idea which is right.
Write it down. A one-page list of "this information lives here" saves a lot of confusion, especially for new staff.
When a connection fails: errors and alerts
Every connection will fail sometimes. An app goes down for maintenance, a password changes, someone renames a column in a spreadsheet, or an order arrives with a missing email address.
What matters is what happens next. A good alert tells the right person what's stuck and why:
Heads-up: last night's order #2187 couldn't be added to Xero because it has no email address. It's been saved and is waiting. Add the email and it'll go through on the next retry.
Behind that message sit four habits every connection needs:
- Catch the failure. The connection should notice it didn't work, rather than carry on as if it did.
- Keep the information. Whatever failed should be held so it can be retried, not lost.
- Alert a named person. Decide who gets told, how (email, text or a message) and how quickly. "Someone will notice" isn't a plan.
- Retry and confirm. Once fixed, the stuck items should go through, and someone should check they arrived.
Whoever builds your connections, ask how failures will be reported, who will be told and who will fix them. Then get the answer written into the scope.
Be careful with connections that delete or overwrite. A mistake that creates a duplicate is easy to tidy up. A mistake that deletes records or overwrites good data is much harder to undo. Test these on sample data first.
Access, security and personal information
Connecting apps means giving one app permission to read or write information in another. Keep that permission as narrow as you can.
- Only pass across the fields the other app needs.
- Use a business account rather than someone's personal login.
- Review access when staff leave.
- Own every login involved, so you're never locked out of your own systems.
If the information includes customer or staff details, the Privacy Act 2020 applies. Our guide to the Privacy Act 2020 and automation covers what to check.
When a spreadsheet is fine, and when to connect your apps
Not every gap needs a connection. A shared Google Sheets or Excel file is often the right tool when volumes are small, one or two people use it, and the information doesn't need to reach anywhere else.
Spreadsheets are cheap, flexible and everyone understands them. It's time to connect when you notice:
- The same details are typed into the spreadsheet and another app every week.
- Mistakes in copying are costing you money or customers.
- Several people edit the sheet at once and things get overwritten.
- You spend more than a few hours a week keeping it up to date.
Even then, the spreadsheet can stay. Often the best first step is simply to fill it automatically, so it keeps doing its job without anyone typing into it.
That's a small, low-risk change, and a good way to see what connected apps can do for your business.
Try it with your own numbers
Work out your hours back
Pick one repetitive task. Move the sliders to match a normal week.
An estimate from your own numbers, not a promise. In a free session we work out a proper estimate together. Book a free session →
Common questions
Do I need to replace my software to connect my apps?
Usually not. We connect Microsoft 365 (Outlook, Excel, Teams, OneDrive and SharePoint), Google Workspace (Gmail, Google Calendar, Google Sheets and Google Drive) and Xero. If you also use a point-of-sale, booking or other system, we do not connect to it directly, but where it can export to Excel or Google Sheets, or sends you emails, we work from what it already produces. The work is in connecting things sensibly, not replacing them.
What happens if a connection stops working?
A well-built connection notices the failure, keeps the information that did not go through and alerts a named person, so it can be fixed and retried. The worst outcome is a connection that fails quietly, so error alerts should be part of the setup from day one.
Is it safe to connect apps that hold customer information?
It can be, as long as you know what information is being shared, where it is stored and who can access each app. Only pass across the details the other app actually needs, and review access when staff leave.
Can I connect apps myself?
Simple connections between two popular apps are often manageable for a confident owner. The difficulty usually comes with matching records, handling errors and keeping things running as your apps update, which is where help can save time.
