Platform
Integrations (foundation + roadmap)
Stripe, Gmail, Google Calendar, Twilio, OpenPhone — foundation ready, integrations ship per quarter.
The problem
Service businesses run on a chain of SaaS tools. Each one is a credential to manage, a webhook to monitor, an outage to chase.
How it works
- Step 01
Connect once
Per-org integration credentials, stored encrypted server-side.
- Step 02
Choose modules
Enable per-org which integrations are active.
- Step 03
Watch the feed
Activity log captures every external API call.
What's included
Per-org credentials
Each organization manages its own integrations independently.
Encrypted credential storage
Service-role access only; never exposed to the client bundle.
Module toggles
Enable / disable integrations per org without code changes.
Webhook foundation
Inbound webhook routing in place for Stripe, Twilio, OpenPhone.
Activity log
Every external API call is logged.
Roadmap visibility
Per-integration roadmap status surfaced in Settings.
Why teams choose this
- Connect the tools you already use.
- Per-org isolation — one client's integration outage doesn't affect another.
- Credentials never leak to the browser bundle.
- Roadmap visibility means no surprises.
What it looks like
Screenshot
Integrations settings
Screenshot
Credential card
Screenshot
Activity log
Use cases
Payments + accounting
Stripe + QuickBooks for collect-and-reconcile flows.
Comms
Twilio for SMS reminders; Gmail for outbound proposals.
Calendar sync
Two-way Google Calendar sync for dispatch teams.
Works well with
Frequently asked
Which integrations are live today?
The foundation tables + credential storage are live. Individual integrations roll out per quarter — check the in-app Integrations settings for current status.
Where are credentials stored?
Encrypted in the database, accessed only via the service-role client server-side. Never in the browser bundle.
Can I write my own integration?
Public API + webhook docs ship with the developer platform release.
Do you charge extra for integrations?
Most integrations are included in the base plan. Heavy-volume integrations (e.g. SMS at scale) carry usage-based pricing.
What about an open API?
Internal API stabilizes first; public OpenAPI spec ships with the developer release.
How is data flow secured?
Every external call is logged + the audit feed captures it. Webhook signatures are validated before processing.
Try Integrations (foundation + roadmap)
Free for small teams. Activate it on your account in one click.