Skip to main content
Back to overview

Integrations

Connect what you already use.

Contracts arrive from your CRM, your e-signature tool, your biller, or a PDF. Entries go back to your general ledger. Everything below is read from the same registry the product runs on, so this page cannot promise a connector that is not wired.

Read this before you connect anything

Who books the receivable?

The expensive mistake in this category is two systems booking the same invoice. Your ledger has one AR balance; if your biller syncs invoices into it and something else posts them too, the balance is wrong and the difference is tedious to unpick months later.

So every connector below carries an answer to that question, written by whoever built the adapter. Possibly is the honest answer for most billers and ledgers: it depends on whether you already run their own GL sync, and only you know that.

Available now

6 connectors

Wired, shipped, and connectable from your settings today.

Available now: Wired, shipped, and connectable from your settings today.
ConnectorBooks your AR?
HubSpotRead closed-won deals + attached signed contracts. OAuth read-only.No
DocuSignRead completed envelopes + attached signed PDFs. Same downstream extraction pipeline as CRM-sourced contracts.No
StripeSync subscriptions, invoices, payments. Drives the collections workflow. Connect via Stripe Connect (OAuth) or a read-only restricted API key — no Connect platform required.Stripe itself doesn't post to your GL — but the QuickBooks Stripe app or a sync tool may already book its invoices there.Possibly
QuickBooksPost journal entries idempotently. Read chart of accounts.If you create customer invoices directly in QuickBooks, QuickBooks already books the AR.Possibly
XeroAlternative GL — chart of accounts read + ManualJournal post with idempotency dedup. Alpha: single-tenant per connection (multi-tenant pick is a future enhancement).If you create customer invoices directly in Xero, Xero already books the AR.Possibly
BigQueryRead contracts directly from BigQuery via SQL. Single-step connect: paste your GCP service account JSON + SQL → we live-probe + save. Self-signed JWT auth (no OAuth round-trip per request). For shops with curated contract tables in BigQuery.No

In development

8 connectors

The adapter exists and has a connect path; it is not switched on for customers yet.

In development: The adapter exists and has a connect path; it is not switched on for customers yet.
ConnectorBooks your AR?
AttioRead deals + linked signed contracts from the fastest-growing CRM in Series A → C SaaS. Alpha — full sync each run (Attio's filter API doesn't expose last-modified yet).No
SalesforceRead Accounts + closed-won Opportunities + attached signed contracts (ContentDocument). OAuth read-only. Sandbox-vs-production toggle on connect — sandbox auth codes hit test.salesforce.com (the most common Salesforce setup bug).No
PandaDocRead completed documents + signed PDFs. OAuth read-only with built-in completed_from incremental sync. Real-time webhook on document completion.No
CommonPaperContract platform built around standardized open-source agreements (CSA / NDA / DPA / pilot / software license). API-key auth (paste key; we validate before saving). Real-time webhook on agreement.executed. Ideal for sales-led SaaS teams using CommonPaper's CSA template.No
ChargebeeSync customers + subscriptions + invoices + payments. API-key auth (paste site name + key; we validate before saving). Real-time webhook on subscription / invoice / payment events.Chargebee's optional QuickBooks/Xero sync may already book its invoices in your GL.Possibly
RecurlySync accounts + subscriptions + invoices + transactions. API-key auth (paste private key; we validate before saving). Cleaner API surface than Chargebee — single base URL, ISO dates, Link-header pagination.Recurly's optional GL integration may already book its invoices in your GL.Possibly
MetronomeUsage-based billing (metering + rating; Stripe-owned). Sync customers + finalized invoices for usage-based revenue recognition — commit/credit-funded invoices route to the contract track. API-key auth (paste token; we validate before saving).Metronome invoices settle in your downstream payment provider (Stripe, NetSuite) — its GL sync may already book those invoices in your GL.Possibly
SnowflakeRead contracts directly from your Snowflake warehouse via SQL. Multi-step connect: paste config + SQL → we generate an RSA keypair → register our public key in Snowflake → verify. For data-engineering-mature shops with curated contract tables.No

On the map

8 connectors

Designed against the same port. Each is one adapter away, built when a customer needs it.

On the map: Designed against the same port. Each is one adapter away, built when a customer needs it.
ConnectorBooks your AR?
ClayNot applicable as a CrmAdapter — Clay's API is inbound-only (you POST data → enrich → push to your webhook). Belongs in a future EnrichmentSourceAdapter port if ICP demand surfaces.No
Apollo.ioRead closed-won opportunities + linked contracts from the sales-engagement platform.No
Adobe SignRead completed agreements + signed PDFs. Adobe's e-signature platform.No
Bill.comSync invoices + payments. Alternative billing for enterprise. Coming next.Bill.com's two-way GL sync posts AR invoices into your GL — that's the product.Yes
MaxioSync subscriptions + invoices. Coming next.Maxio's optional GL sync may already book its invoices in your GL.Possibly
NetSuiteEnterprise GL. Coming Tier-2.If you create customer invoices directly in NetSuite, NetSuite already books the AR.Possibly
RedshiftRead contracts from Redshift via SQL. Coming next — port shape proven via Snowflake.No
DatabricksRead contracts from Databricks via SQL. Coming next — port shape proven via Snowflake.No

Nothing to connect on day one.

Upload a signed contract and read the determination before you wire a single system — the primary path needs no connector at all.