Integrations
Open Settings → Integrations in Thermal →
What it's for
Integrations is where you connect outside services to Thermal — accounting, card payments, texting, and email — and see what's connected, what needs attention, and what's still available. It's the hub for every third-party connection; a link on this page takes you to API & webhooks for anything you'd build yourself instead of connecting an off-the-shelf service.
Reach it from Settings → Data and connections → Integrations in the
sidebar, at /settings/integrations.
Tabs
This screen has no tabs. It's two sections: Connected, shown only when at least one service is connected or needs attention, and Available below it, always shown.
Panels and controls
Connected
One card per connected service, showing its status line — Connected, or Reauthorize needed if the connection errored out or QuickBooks stopped accepting Thermal's sign-in (an expired or revoked token, for example). The QuickBooks card shows its measured sync times on a separate line. A connected card shows the account identifier under its blurb (e.g. the QuickBooks Realm ID) — never a secret or token, only the non-secret reference. Reconnect restarts the QuickBooks connection when it needs reauthorizing; Disconnect clears the QuickBooks connection after a confirmation, warning that existing tokens will be cleared. The Card payments card has neither: it links to Payments, where the Stripe account is managed.
Available
One card per service not yet connected. The QuickBooks Online card authorizes your company file (see Connect integrations for what syncs); its Connect button starts an OAuth flow. The card payments card is set up on its own screen: Set up payments (or Manage payments once connected) opens Payments. The text messaging card links to Settings → Integrations → Text messaging, where you set up your company's sending number; Thermal runs text messaging, so there is no key to enter, and texting US numbers waits on carrier registration, which is in progress. The email card is informational: Thermal runs email and receipts, so there is nothing to connect.
The Zapier card's Set up Zapier button opens API & webhooks, where you connect a Zap. API & webhooks is also live and links through to that screen. Two more tiles (Google Business, Dropbox) are shown for reference only — they're not connected, and their Connect button does nothing.
Setup rolling out
If a service's connection isn't configured on this deployment yet (missing OAuth credentials, or encryption not set up), its card shows "Setup rolling out — this connection is not configured yet" instead of a connect control.
What it accepts
| Field | Format | Required | Rule |
|---|---|---|---|
| Provider | One of the four listed services | Yes | "Unknown integration provider." |
A connection can't be saved at all if the platform's encryption for stored credentials isn't configured — "Integration encryption is not configured." A callback that arrives after the OAuth handshake has expired shows "Connection state expired. Start the connection again from this page." instead of completing silently.
How to configure it
- Every connection here is what other screens depend on: Invoicing's tax engine can use Stripe Tax once Stripe is connected; customer notifications (configured on the main Settings page) only actually send when the channel is ready. Text is ready once your company has a verified sending number, set up at Settings → Integrations → Text messaging. Email depends on Thermal's own email setup. A notification toggle left on for a channel that isn't ready simply never fires.
- API & webhooks, reached from the API & webhooks tile, is the build-your-own alternative — API keys and outbound webhook endpoints rather than a first-party connected service.
Who can see it
This screen sits behind its own Integrations area gate, not the general Settings gate — and unlike almost every other Settings screen, that gate is owner-only. Office managers, who otherwise have full Settings access, are specifically excluded from Integrations; they cannot open this page or manage a connection. Dispatchers and technicians cannot reach it either. The gate is checked on the server, not just hidden in the sidebar, so a direct link does not get around it.
The full role matrix is on Roles & permissions.