Website integrations: connecting your site to the tools you run on
A website does far more than sit there looking nice. Here's what it means to wire yours into your CRM, calendar, payments and accounting, and what that actually gets you.
Updated 21 September 2026
On this page
Most small business websites are islands. A lead fills in a form, the message lands in an inbox, and then someone has to read it, copy the details into a spreadsheet or a CRM, send a reply, maybe book a time, maybe chase an invoice. Every one of those steps is manual, and every manual step is somewhere a lead can go cold or a job can slip.
A connected website does that work for you. When your site talks to the tools you already run, an enquiry can land in your CRM, trigger a follow-up email, offer the customer a time in your calendar, take a deposit, and raise an invoice in your accounting software, without you touching any of it. That's the difference between a brochure and a piece of business infrastructure.
We've built integrations into all of the tools below and plenty more. Here's how to think about it.
What an integration actually is
An integration is just two pieces of software talking to each other through an API: a defined way for one system to send or pull data from another. Your website fills in a form; the API hands that data to your CRM. Your booking page checks the API for free slots in your calendar. A payment goes through Stripe; the API tells Xero to raise the invoice.
The practical upshot is that data only gets entered once, by the customer, and then flows wherever it needs to go. Nobody re-types a phone number. Nothing gets missed because the one person who checks the inbox was on leave.
Almost every serious business tool has an API these days. If yours does, we can usually connect it.
The tools worth connecting
You don't need everything wired up on day one. The connections that pay for themselves fastest are the ones that touch a lead or a dollar.
CRM and lead capture
This is the first one we'd do for most businesses. Instead of form submissions sitting in an inbox, every enquiry lands in your CRM tagged with where it came from, ready to follow up. Nothing slips. The section on CRM connections below covers what a good one does.
Bookings and calendars
If you sell appointments, classes or consultations, letting people book themselves a time on your site beats phone tag every time. It syncs to your calendar so you're never double-booked, and it can take a deposit at the same time. The section on booking options below compares the three ways to do it.
Payments and accounting
Take money on your site through Stripe, Square or PayPal, then push the sale straight into Xero, MYOB or QuickBooks so your books stay current without manual entry. The Australian specifics, GST and invoices included, are in connecting payments and accounting, and Xero vs MYOB vs QuickBooks compares the three products.
Email marketing and automation
New leads can flow into Mailchimp and start a welcome sequence, or trigger a chain of actions through Zapier or Make: notify your team in Slack, add a row to a sheet, create a task. Automation tools like these are the glue that connects the apps that don't talk to each other directly.
Reviews and chat
Pull your Google or Trustpilot reviews onto the site as live social proof, and add live chat or a tool like Intercom so visitors can reach you the moment they have a question.
What it looks like in practice
Say you run a clinic. A new patient finds you on Google and books a first appointment on your site. In one go:
- the booking takes a deposit through Stripe
- the time drops into your practice calendar
- the patient gets a confirmation and a reminder the day before
- their details land in your CRM, tagged as a new patient from organic search
- an invoice is raised in Xero
You did none of that. You just turned up to the appointment. That's a website earning its keep.
Which job and clinic tools can a website connect to?
Most of them have either an API or a booking or enquiry form, and which one decides how the connection is built. The table records what each vendor's own pages say, as at November 2026. Check the vendor's pricing page for your region, because prices and plan limits differ by country.
| Tool | Used by | What the vendor says about connecting | Fee page |
|---|---|---|---|
| ServiceM8 | Trades and field service | "Our REST API allows developers to hook into ServiceM8" and API access starts at the Starter plan on its pricing page. Online bookings come with every plan, and Zapier, Xero, QuickBooks Online and Mailchimp integrations are listed on all plans | ServiceM8 pricing |
| Tradify | Trades | A branded enquiry form and email address that sends enquiries into Tradify on the Pro and Plus plans, and Xero and QuickBooks Online sync. We found no public API mentioned on its pricing page, so a website connection would go through the enquiry form or email | Tradify pricing |
| Cliniko | Allied health clinics | A public REST API returning JSON, with each user's API key as Basic authentication, covering patients, appointments, invoices and practitioners, with a limit of 200 requests per minute per user | Cliniko API and Cliniko pricing |
| Nookal | Allied health clinics | Online bookings on all three plans, and API access on the Professional and Enterprise plans but not Essentials | Nookal pricing |
Two plain rules follow from the table. Check which plan includes the API before you promise a client a live connection, because on Nookal and ServiceM8 it depends on the plan. And design the form so that a failed call to the tool never loses the enquiry, which is the "never let a CRM call fail a booking" rule: we cap job-system calls at eight seconds so the form still sends, and keep the plain-email copy described below.
Should a booking button link out, embed the widget or be built into the site?
For most small businesses a link to the booking tool's own page is enough. Count the bookings you take in a month: under about twenty, link out. Between twenty and a couple of hundred, embed the widget if it behaves on a phone and link out if it does not. Above that, or when your scheduling has real rules in it, build it into the site.
| Option | How it works | What it costs you | Suits |
|---|---|---|---|
| Link out | The button opens Calendly, Cliniko, Square Appointments or similar on the tool's own domain | A visible seam: your site and the booking page look different, and some visitors hesitate at the jump | A handful of bookings a week; nothing breaks, and the tool's own flow is usually better tested on mobile than a custom one |
| Embed the widget | A snippet from the tool puts the calendar inside your page | Third-party JavaScript from someone else's server. Google's guidance on third-party JavaScript says any significant amount of JavaScript can slow a page, and third-party code is outside your control. Widgets built for a wide container often scroll badly on phones | A short booking flow with a widget you have checked on an actual phone |
| Build it in | The site reads availability from the tool's API; the form and confirmation are yours | The most work by a distance | Enough bookings that a few points of drop-off is real money, or an unusual flow such as multi-practitioner clinics, prices that depend on booking answers, or site visits with no fixed slot length |
Three things go wrong more often than the widget does. The first is the account: whoever set up the booking tool owns the login, and the tool holds your customer list and history. The business should hold the account under its own email address, with anyone helping invited to it, the same rule as for the domain in who actually owns your website. The second is what happens after the booking. A confirmation that reads like a receipt, no reminder and no way to reschedule without ringing all cost bookings, and reminders are a setting in these tools that someone has to switch on. The third is that the booking tool becomes a second place your customer data lives.
A booking flow worth setting up covers two-way calendar sync, so anything already in your calendar blocks that time; a deposit or full payment through Stripe or Square at booking; reminders by email or SMS; buffers for travel time, a daily cap and a minimum lead time; and a new contact created in your CRM, as an enquiry would be.
What should a website to CRM connection do?
It should push every form into the CRM through its API as well as emailing it, so each enquiry arrives as a record that can be assigned, chased and reported on. A CRM is the system that holds your leads and customers and tracks where each one is up to. A connection worth paying for does five things:
- Sends every form to the CRM, including contact, quote request, audit and newsletter forms.
- Tags each lead with its source, such as organic search, a Google ad or a landing page, so after a few months you can see which channels produce paying customers.
- Notifies the right person by email or Slack when a lead arrives.
- Puts new leads in the right pipeline stage, tagged by service or location.
- Keeps an email notification as a backup, with the CRM as the record.
We work with whatever CRM you already run, including HubSpot, Pipedrive, Zoho and industry systems, provided it has an API. A two-person business that visits the CRM only when it remembers to is better off with the enquiry landing in a shared inbox than in a CRM nobody opens.
How do you stop an integration failing without anyone noticing?
Keep an unconditional plain-email copy of every submission, and send yourself a test enquiry once a month. When a form only emails you, a failure is loud, and two weeks of silence prompts a check. When a form pushes into six systems, five can keep working while the one holding the record you would have used to notice has stopped. There is no alert, only a thinner month.
- Keep the plain copy. The form should send a plain email to an address more than one person reads, every time. A fallback that triggers when the clever route fails does not work, because it needs the system to know it failed. Use a shared address, since a departed employee's mailbox can swallow a fortnight of enquiries.
- Test monthly. From your phone on mobile data, send an enquiry with a real phone number, then check every place it should appear: CRM, calendar, shared inbox and notification. Most automation tools keep a log of what ran. Zapier's Zap history shows whether a workflow fired, errored or never started.
- Know where the copies are. Each connection is another system holding customers' names, phone numbers and addresses. Under the OAIC's Notifiable Data Breaches scheme, if the Privacy Act covers your business and personal information you hold is breached in a way likely to result in serious harm, you must notify the people affected and the OAIC. Remove form fields nobody uses.
- Check whose account each tool is in. An automation platform under an ex-contractor's login puts the ownership problem between your website and your enquiries.
We run this check as part of a free website audit. It has turned up automations that stopped firing after someone changed a field name, and forms notifying an address that no longer existed.
We integrate with these, and more
Across our projects we've connected sites to Stripe, PayPal, Square, Xero, MYOB, QuickBooks, HubSpot, Mailchimp, Intercom, Calendly, Google Calendar, Zapier, Make and others. We can also connect a store you already run on Shopify to a fast front end through our e-commerce plan, where you pay Shopify directly. The list isn't the point, though. The point is that if a tool runs part of your business and it has an API, your website can work with it instead of around it.
If you're planning a new site or a rebuild and want it doing real work rather than just looking the part, here's how we approach web design, or get a free website audit and we'll tell you what's worth connecting first.
Common questions
- What is a website integration?
- An integration is your website and another piece of software talking to each other through an API, so data entered once on the site flows straight into the tool that needs it. A form submission becomes a CRM record, a booking becomes a calendar entry, a payment becomes an invoice, and nobody re-types a phone number.
- What does website synchronisation mean?
- It is the same idea described from the data side: two systems holding the same information and keeping it in step, rather than one copy quietly going stale. In practice the website pushes changes as they happen, so your CRM, your calendar and your accounting software all show the same customer record.
- How does a CRM integration with a website work?
- Your contact or quote form posts to the CRM's API as well as sending an email, so every enquiry arrives as a record carrying the source, the page it came from and the customer's details. Assignment and follow-up then happen in the CRM, where the rest of your pipeline already lives.
- Which integration should you connect first?
- The one that touches a lead or a dollar. For most businesses that is lead capture into the CRM, because an enquiry sitting unread in a shared inbox is the most expensive failure on the list. Bookings and payments come next, and reporting tools last.
- Should I embed a booking widget or link to the booking tool?
- For most small businesses a link to the booking tool's own page is enough. Embed the widget only if it behaves well on an actual phone, and build the booking into the site only when you take enough bookings that a few points of drop-off is real money or your scheduling has unusual rules.
- What happens when an integration breaks?
- Quietly, which is the real risk. A form that emails you fails loudly; a form pushing into six systems can fail in one of them for weeks without anyone noticing. Keep an unconditional plain-email copy of every submission going to a shared address, and send a test enquiry through every destination once a month.
Want a website that turns readers into customers?
A custom site, hosting and upkeep for one monthly fee, with your leads and Google results in a dashboard you can check any time.