Integrations & Channels

Fyndow runs a whole service business end to end — quoting, scheduling, invoicing, collecting payment, and keeping clients warm — but it doesn't pretend to be the only software you use. A provider already has a calendar they live in, an accountant who wants the numbers in a familiar shape, and customers who'd rather get a text than open an app. Integrations are how Fyndow meets those tools where they are: your bookings flow into the calendar you already check, your paid invoices land in the books your accountant already trusts, money moves through a real payment processor, and alerts reach people on the channel they actually read.

This chapter is a capability-level tour of what Fyndow connects to and the value each connection delivers. It is not a setup manual or a developer reference — the point here is what becomes possible once a connection is in place. Builders and partners who want to integrate with Fyndow at the protocol level — a public API, webhooks, channel bridges — have their own deeper material, pointed to from the API Reference.

What Fyndow Connects To

Four kinds of connection cover the ground a working business needs:

Connection	What it does	Who it's for
Calendar sync	Mirrors confirmed bookings onto your external calendar and keeps them in step	Any provider who books appointments
Accounting export	Sends paid invoices to your bookkeeping software as receipts	Providers who keep formal books
Payments	Processes customer payments and pays providers out	Everyone who transacts on Fyndow
Messaging channels	Delivers notifications over email, SMS, and chat apps	Anyone who wants to be reached off-app

Each is opt-in and independently switchable. Connecting one doesn't require the others, and disconnecting is always a single action — you own the connection, and you can revoke it whenever you like.

Calendar Sync

A booking on Fyndow is only useful if it shows up where you already look for your day. Calendar sync connects your Google Calendar once, then keeps it in lockstep with your Fyndow schedule so you never double-book or miss an appointment because it lived in the wrong place.

The sync follows your bookings through their lifecycle automatically:

• When a booking is confirmed, Fyndow places a matching event on your calendar — with the customer, the service, and the time already filled in.
• When a booking is rescheduled, the calendar event moves with it.
• When a booking is cancelled, the calendar event is removed, so a dead slot doesn't sit there blocking your day.

You connect the calendar from your settings, see its connection status at a glance, and disconnect in one click. The flow of bookings into appointments is part of the Scheduling tool — calendar sync simply extends it onto the calendar you already keep.

Accounting Export

When an invoice gets paid on Fyndow, the money is only half the job — your books need to know about it too. Accounting export connects your bookkeeping software (QuickBooks) so that paid invoices flow straight into your accounting as sales receipts, with no re-keying and no end-of-month reconciliation marathon.

It works the way good automation should — quietly, in the background:

• Connect your accounting software once and turn on auto-export.
• Every time an invoice is marked paid — whether the customer paid online or you recorded a manual payment — Fyndow posts a matching receipt to your books.
• Each export is tracked, so the same invoice is never double-counted.

If you'd rather keep manual control, you can leave auto-export off and the connection simply stays available without acting on its own. Either way, your accountant sees the numbers in the format they already work in. The invoicing side of this is covered in Invoicing.

Payments

Every transaction on Fyndow — a booking deposit, a paid invoice, a marketplace order — moves through a real, regulated payment processor (Stripe), not a balance that only exists inside Fyndow. That choice is what makes the money trustworthy on both sides.

What it means in practice:

• Providers are paid into their own connected payment account. Your earnings are yours, held in an account you control and can withdraw from — Fyndow never sits between you and your money as a permanent holding pen.
• The platform fee is transparent. Fyndow takes a clear, disclosed cut of each transaction for running the marketplace; the rest is the provider's.
• Payout timing protects both parties. For certain jobs, funds are held briefly after a customer pays and released once the work is done — so a customer isn't paying into the void and a provider isn't chasing a payment that never clears.
• Refunds, cancellations, and disputes have clear rules. When something goes wrong, there's a defined path back, not an argument.

This chapter keeps payments at the level of what you can rely on. The full money story — how providers get paid, fees, payout timing, refunds, and disputes — lives in its own section: start with How Providers Get Paid, then Refunds & Cancellations and Disputes & Chargebacks. Paying to give a Happening public reach is its own small transaction, explained in Paying for Reach.

Messaging Channels

People don't all live in the same inbox. A notification that matters — a booking confirmed, an invoice paid, a new message, a review received — should reach someone wherever they actually pay attention. Fyndow can deliver alerts over several channels beyond the app itself:

in-app · email · SMS · WhatsApp · Telegram · push (mobile)

Two principles keep this useful rather than noisy:

• You choose the channels per event type. Each person sets which channels fire for which kinds of event, so the things that matter reach you the way you want and the rest stay quiet. The push channel covers the mobile app.
• External channels are notification-only. An SMS or a WhatsApp message tells you something happened and links you back into Fyndow to act on it — no booking is accepted, no invoice is paid, and no money moves through a text message. The channel is a doorbell, not a control panel, which keeps every consequential action inside the app where it's authenticated and auditable.

The full picture of what triggers a notification and how delivery is decided is in Notifications & Digests.

Building With Fyndow

Everything above is about connecting Fyndow to tools a business already uses. The reverse direction — building software on top of Fyndow — exists too. Fyndow's back office is a large, capability-rich toolkit (dozens of self-contained domains, from services and scheduling to payments, forums, and events), and that breadth is exposed through programmatic surfaces for partners and integrators: a public API, event webhooks, and bridges into outside channels.

Those surfaces are documented separately, in their own depth, for the people who need them. If you're integrating at that level rather than just connecting an account, the API Reference is the front door.

Where Connections Live

Connections are managed from your settings — connect, check status, toggle behaviour like accounting auto-export, and disconnect, all in one place. Nothing is connected by default; each integration is something you deliberately turn on, and each is something you can deliberately turn off. The goal is steady, boring reliability: once a connection is in place, your calendar stays current, your books stay reconciled, your payouts arrive, and the right people hear about the right things — without you thinking about it again.