ChatBuildConnecting your website to the tools you already use
The useful question is not what can connect. It is what you keep retyping.
Most small businesses run on four or five tools that do not know about each other: the website, a mailbox, an invoicing package, a booking calendar, maybe a spreadsheet nobody admits to.
Connecting them sounds like a technical project. Usually it is one decision about where information should live, followed by something much smaller.
Start with the question, not the integration
The useful question is never "can these connect?" It is "what am I currently retyping?"
Write down the last five things you copied from one place to another: an enquiry into a quote, an address into an invoice, a booking into a calendar. That list is your integration backlog, in priority order, and it is usually shorter than people expect.
The three levels, cheapest first
Level one: a link. Your site's contact button opens WhatsApp, your booking page links to the calendar tool you already pay for. Nothing to build, nothing to break, and it solves more than people expect.
Level two: a forward. Form submissions arrive as email, and your existing rules file them. Still no integration, still no maintenance.
Level three: an actual connection. The site writes into another system through its API, or through an automation tool sitting between them. This is the only level with ongoing cost, and the only one that breaks when the other side changes.
Most businesses need level one for nearly everything and level three for exactly one thing.
What makes a connection worth building
Three conditions, and it needs all three:
- It happens often. Once a month is not a workflow, it is a task.
- The data is the same every time. Structured, predictable fields — not "whatever the customer wrote".
- Getting it wrong is visible. A wrong address on an invoice costs more than the minute it saves.
If a connection fails two of those, a link and a habit will serve you better and cost nothing to maintain.
The part nobody mentions
Every integration is a small ongoing liability. The other side updates its API, a key expires, a field is renamed, and the failure is silent — nothing errors, things just stop arriving.
So for anything that matters, know how you would notice. Usually that is as simple as "the weekly summary email stopped", but it has to exist, because the alternative is finding out from a customer.
Ask before you build. With ChatBuild you describe what should happen — enquiries into your inbox, for example — and the connection is set up for you, or you are told plainly that a link would do the job better. What your site can connect to.
A sensible order
Do the retyping list. Solve the top item with a link if you can. Only reach for a real connection when a link genuinely cannot do it, and when all three conditions above hold.
That order is boring and it is why some businesses have five tools that work together and others have a monthly bill for automations nobody uses.
Related: if your site is old enough that nothing connects to it cleanly, the question may be repair or rebuild. And whatever you connect, someone has to keep it working.
Frequently asked
- Do I need an automation tool like Zapier or Make?
- Only once a link or an email forward genuinely cannot do the job. Those tools are worth their subscription when something happens weekly with predictable data; below that, they add a bill and a dependency to a task you do twice a month.
- How do I know an integration has stopped working?
- Decide that before you build it. The common failure is silent — nothing errors, records simply stop arriving — so you need a signal you would actually notice, such as a weekly summary that goes quiet.
Sjors Hooijen Builds ChatBuild and writes about getting a business online without turning it into a project. Questions about this article? Email hi@chatbuild.com.