Salesforce
CRM & Sales Engagement
Opportunities and quotes stay in step, with the CRM owning the deal and CPQ owning the price.
Last synced 2 mins ago
Ecosystem
It talks to what you already run
Your sellers are not leaving Salesforce and your controller is not leaving QuickBooks. Neither should have to. Here are 12 native connectors — 7 of them writing in both directions — published with the field mapping, the auth method, the cadence, and the system of record for every entity they touch.
72 mapped fields are listed by name on this page. A logo wall tells you a partnership exists; it does not tell you whether a quote becomes an invoice.
SOC 2 Type II aligned · PIPEDA compliant · AWS ca-central-1 tenant isolation · SAML 2.0 single sign-on
CRM & Sales Engagement
4 connectorsYour sellers keep working the pipeline they already know. The quote is built here and the opportunity value, stage, and close date land back there without anybody re-keying a number.
Call Intelligence & Communication
3 connectorsThe scope of work is agreed on a call, not in a form. These connectors take what was said on the call and turn it into configured line items an estimator can price.
ERP & Financial Operations
5 connectorsYour controller does not change systems because you bought quoting software. Invoices, job cost, and revenue post into the ledger of record with the tax treatment already correct.
6 of 12 connected in Apex Commercial
Salesloft
CRM & Sales Engagement
Cadence activity and reply sentiment land on the quote, so the estimator knows the deal is warm.
Last synced 14 mins ago
Apollo.io
CRM & Sales Engagement
Sequence replies route to the account owner with the site and trade already attached.
Configure sync
LinkedIn Sales Navigator
CRM & Sales Engagement
Buying-committee changes at your key accounts surface against the account, not in a separate tab.
Configure sync
Avoma
Call Intelligence & Communication
Parses the scope agreed on a call into draft CPQ line items, each one linked to the sentence it came from.
Last synced 6 mins ago
RingCentral
Call Intelligence & Communication
Inbound service calls open against the right site, and technician ETA texts go out on your own number.
Last synced 9 mins ago
Microsoft Teams
Call Intelligence & Communication
Approvals and dispatch escalations arrive as adaptive cards that can be actioned without leaving Teams.
Configure sync
QuickBooks Online
ERP & Financial Operations
Completed work becomes an invoice with HST already mapped to the right tax code and account.
Last synced 11 mins ago
QuickBooks Desktop
ERP & Financial Operations
The same invoice posting for Enterprise and Premier Contractor Edition, over the Web Connector.
Configure sync
Sage 300 CRE
ERP & Financial Operations
Job cost actuals, committed cost, and WIP post against the real job and cost code structure.
Configure sync
NetSuite
ERP & Financial Operations
Multi-subsidiary revenue recognition, projects, and inventory across entities and currencies.
Configure sync
Stripe Billing
ERP & Financial Operations
Deposits, progress payments, and PAD settlement, reconciled back to the work order that earned them.
Last synced 4 mins ago
The one that changes the workflow
Avoma: the scope was agreed on the call, so build the quote from the call
On a commercial job the scope is settled verbally — a walkthrough, a site call, fifteen minutes with a facilities manager — and then somebody retypes it from memory two days later. That gap is where margin dies. The Avoma connector runs the transcript through the same catalogue the CPQ engine prices from and proposes draft line items with quantities, dimensions, and product families already resolved.
Every derived line carries a citation: the transcript offset and the sentence that produced it. Nothing auto-prices and nothing auto-sends — a draft line is proposed, never committed. That is the difference between an assistant and a liability.
- Direction
- Inbound
- Mapped fields
- 10
- Cadence
- Webhook on transcript-ready, typically 4–8 minutes after the call ends
How the connections behave
The four things an IT reviewer asks
Integration is where a platform quietly becomes a risk: a token with too much scope, a write with no owner, a partial sync nobody noticed. These are the answers, and they are the same on every connector in the catalogue.
Entity mapping is modelled during implementation by Novel Systems, against your own chart of accounts, cost codes, and price book. It is the part of onboarding that takes the longest and the part that makes every figure above mean something.
Scoped credentials, never a shared admin login
Every connector authenticates with the narrowest grant that works — 4 distinct auth methods across the catalogue, each scoped to the object types listed on its card. A token that can do everything is a token that eventually does.
A declared system of record for every entity
Bidirectional sync without a declared owner is two systems taking turns overwriting each other, and the customer finds out which one won at month end. Each connector names who breaks the tie, per entity, and the drawer shows it before you connect.
Published cadence, including the slow ones
QuickBooks Desktop polls on a 30-minute Web Connector interval and Sage 300 CRE batches hourly. Those are stated here rather than discovered in week three, because a customer who plans around a real interval is not disappointed by it.
Every sync is an audit entry
Writes are idempotent on an external id or event id, so a replayed webhook updates one record instead of creating a second. Failures raise an exception rather than posting a zero — a silent partial sync is the expensive kind.
Bring us the stack you already run
Tell us which CRM, which ledger, and which phone system, and we will walk the field mapping with you against your own objects before anything is signed. If a connector here does not carry a field you depend on, that is a better thing to find out now.
Bidirectional ERP sync is a Business and Enterprise capability; standard events and webhooks are on every tier. The comparison matrix on /pricing states which is which.