How we connect your tools
A control hub is most useful when it works with the systems you already run. Here's how those connections are set up, what they can and can't do, and how you stay in control of them.
You approve every connection
We never ask for your passwords. For tools like Microsoft 365, Google Workspace and QuickBooks, someone on your team signs in to that tool directly and approves the connection on the tool's own screen. Your hub receives a secure access token, never your password. For tools that use API keys, you add the key in your hub, or give it to us through a secure channel; never by email or chat.
Only the access a feature needs
- We ask for the narrowest permission each feature needs, and read-only access wherever that's enough.
- Write access (for example, sending an email you've approved, or creating a draft invoice) is only requested where a feature needs it, and we explain it before you connect.
- Nothing is sent to a customer, paid or changed in another system without a person on your team approving it.
How tokens and keys are kept
- Access tokens and API keys are encrypted before they're stored, in your hub's own database, separate from every other client.
- They're used only by your hub's server, never shown in the browser, and never shared with other clients or third parties.
- Connection events (connected, refreshed, disconnected) are recorded in your hub's activity log.
When a system has no API
Some systems don't offer an open way to connect. In those cases we can have the system email its standard reports to your hub on a schedule, and the hub reads them in automatically. You get up-to-date numbers without anyone exporting or retyping anything, and the original system stays exactly as it is.
What we connect most often
- Email and calendars: Microsoft 365 and Google Workspace.
- Accounting: QuickBooks Online. See how the QuickBooks connection works.
- Websites and analytics: your website's forms, Google Analytics and Google Search Console.
- Industry and point-of-sale systems: through their API where one exists, or scheduled reports where it doesn't.
AI and your data
Where a feature uses AI, only the information that feature needs is sent to the AI provider, under business terms where your data isn't used to train their models. Sensitive records can be kept out of AI features entirely.
Disconnecting
You can disconnect any tool at any time, from your hub or from the tool's own settings. When a connection is removed, its stored token or key is deleted. When you stop using your hub, we delete your data after giving you an export on request. See our data retention policy and data deletion page.
Questions about a connection? Email build@buddyworkflow.com.