Integrations/Payments & finance

Revenue lands next to the customer who paid it.

Every charge, invoice, order, and bank transaction becomes an entry on the record of the person or company behind it — so what a customer is worth, and what's moving through your accounts, is a glance, not an export.

Charges, invoices & orders → transactions + AR · Subscriptions → MRR & churn · Bank + bills → cash & spend

5 connectors, one canonical shape

Each maps into the same schema. Connect one, or all of them.

Stripe logo

Stripe

SyncAPI key

Sync Stripe customers, payments, invoices, and subscriptions to see revenue, MRR, and LTV per customer.

Customers → people/orgs, Charges & Invoices → revenue transactions + AR, Subscriptions → MRR/churn metrics.

Xero logo

Xero

SyncOAuth

Pull Xero contacts and invoices into Excellent to tie accounting to the customers behind it.

Contacts → people/orgs, Invoices → revenue transactions + the AR lifecycle table.

QuickBooks logo

QuickBooks

SyncOAuth

Sync QuickBooks customers, invoices, and bills so receivables and spend live next to your customers.

Customers → people/orgs, Invoices → transactions + AR, Bills → the AP/spend table.

Plaid logo

Plaid

SyncAPI key

Connect your bank through Plaid and see actual cash movement — transactions land in money accounts beside the revenue behind them.

Bank transactions → money-account entries, tracking real cash movement in and out.

Shopify logo

Shopify

SyncOAuth

Sync Shopify customers and orders so storefront revenue lands on the customer record — the same people your CRM already knows.

Customers → people/orgs, Orders → revenue transactions. Store revenue lands on the customer who spent it.

Connected, not surrendered.

Your data from these tools syncs in and stays on your machine — connecting a tool never hands it to a middleman.

No third-party broker

Records sync straight between your machine and the provider — nothing sits in the middle.

Sealed at rest

Tokens are AES-256-GCM-encrypted locally, with the master key kept off the database.

One source of truth

Synced records become rows in the one schema you own — never a parallel copy.

Revenue lands next to the customer who paid it.