Keep the source of truth
Your ledger, CRM, drawing environment or carrier can remain responsible for the records it owns.
Integrations
A bespoke manufacturer should not have to replace every specialist system to get one operational picture. ScaleBespoke connects the useful boundaries—so the ledger, pipeline, drawings, site work and delivery can stay in context.
Xero
Duett
Salesforce
HubSpot
Dalux
Bring
Revolut
Storecove
Specialist systems, shared context
Finance can work in the ledger, sales can bring its existing pipeline, and project teams can collaborate in their drawing and site environments. ScaleBespoke carries the client, order and delivery context between those moments—without pretending every connection does the same thing.
One job, many specialist systems
A good integration is not a cloud of arrows. It has a clear owner, a defined record set and a visible handoff.
Your ledger, CRM, drawing environment or carrier can remain responsible for the records it owns.
Each connector moves a defined set of records—not an unexplained copy of everything.
Sales, finance, drawings, site tasks and delivery stay attached to the client and order doing the work.
Where a connector writes back, tracks only or needs human approval, the boundary is visible before setup.
How to read this catalogue
Each integration is labelled with its real connection method. We do not call an import a live sync, or a manual referral an API.
The external system can remain the system of record while operational changes stay connected to ScaleBespoke.
A dedicated connector performs a defined task such as site-status sync, shipment tracking or payment-draft preparation.
Source records are authenticated, normalized and reviewed before becoming native ScaleBespoke records.
The page states the boundary clearly when a service is outbound-only, tracking-only or still requires a human handoff.
18 connections
Native ledger sync comes first, followed by treasury, e-invoicing and provider-specific finance adapters. Each card states whether data moves both ways, one way or through a controlled import.
Native two-way sync — keep Xero as your statutory ledger while the operational side of finance lives in ScaleBespoke.
Native two-way sync for Norwegian accounting — the same connected-finance approach as Xero, built for Duett.
Prepare supplier bill payments as drafts in your own Revolut Business account and reconcile your bank feed against Accounting. Every draft still needs a human to open Revolut and send it — nothing here can move money on its own. This is an outgoing treasury connection, not customer payment collection; clients paying by bank transfer still confirm through the Customer Portal, same as today.
Sends Norwegian sales invoices as real EHF/Peppol documents through Storecove, a certified Peppol Access Point — outbound only, and only for clients with a Norwegian organization number.
OAuth2 connects Sage Business Cloud Accounting. The adapter reads and writes sales and purchase invoices and uses incremental polling because Sage does not provide transaction webhooks.
QuickBooks Online connects through Intuit OAuth2. Customer invoices and vendor bills are read through the QBO query API and supported records can be pushed back through the matching transaction endpoints.
NetSuite Token-Based Authentication signs SuiteTalk REST requests. SuiteQL reads customer invoices and vendor bills; supported transactions can be created back in NetSuite.
Tripletex consumer and employee tokens are exchanged for a session token. The current adapter reads and writes customer invoices and can receive the documented invoice event callback.
The PowerOffice Go OAuth connector reads supported outgoing invoices and finance records and can create supported customer invoices from ScaleBespoke.
FreshBooks OAuth connects the account and reads clients, invoices and bills. The adapter supports pushing the matching invoice and bill records back through FreshBooks APIs.
The Xledger GraphQL adapter connects the configured tenant, reads supported customer and invoice data and can create supported customer invoices from ScaleBespoke.
A Visma OAuth service application reads supported customer-invoice records for the selected company and can push supported invoices back through the Visma.net API.
Visma eAccounting connects with OAuth refresh tokens. The adapter reads customers and supported sales or purchase invoice data and can create supported customer invoices.
The Business NXT GraphQL adapter currently prepares supported customer invoices from ScaleBespoke for the configured Visma company. It is an outbound invoice path, not a general ERP import.
Unimicro uses OAuth client credentials and a product-specific API base URL. The adapter reads and writes supported customer invoices after the tenant endpoints are confirmed during setup.
UNIT4 connects through the customer's own Identity Services authority, tenant and scope. The adapter targets customer and sales-invoice records using the endpoint paths confirmed for that tenant.
A Microsoft Entra application connects to the selected Business Central environment and company through the documented OData v4 API to read and create supported sales invoices.
Mark an overdue invoice as referred to one of 13 real Norwegian and UK collection agencies, generate a standard case-file export, and track status by hand. None of the researched agencies offer a public API, so this is an honest referral tracker — not an automated connector.
17 connections
Provider adapters authenticate against the source platform, normalize supported records and bring them into the native ScaleBespoke pipeline. Import is not described as live sync unless the connector actually supports it.
Bring deals, contacts and history in from Salesforce with the built-in import framework — switching doesn't mean starting from zero.
Deals, contacts and companies migrate in directly from HubSpot's CRM — pipeline and client history intact.
The Bitrix24 REST adapter reads deals and maps their stage, value and source identity into normalized ScaleBespoke deal records.
The 24SevenOffice provider adapter brings supported sales opportunities into the native pipeline while retaining the external record identity for traceability.
The SAP Business One Service Layer connector reads sales opportunities together with the business-partner context needed to create a usable CRM record.
The SAP Sales Cloud OData adapter imports opportunity records and converts their external stage and value into the ScaleBespoke pipeline format.
The separate Sage CRM connector imports sales opportunities into CRM. It is distinct from the Sage Business Cloud Accounting connection shown under finance.
Zoho OAuth is used to read Deals together with their Account and Contact context before the records enter the ScaleBespoke pipeline.
A Microsoft Entra application connects to the Dataverse Web API and imports supported Opportunity records into the native CRM pipeline.
The SugarCRM v11 OAuth2 adapter reads opportunities and their contact context, then maps them to native deals and clients.
The SuperOffice OAuth REST connector imports Sales and links the related Contacts and Companies so pipeline history does not arrive without its client context.
An Insightly API key reads Opportunities and maps their state, pipeline stage, value and creation date into ScaleBespoke deals.
Board items import as deals. An optional webhook and push adapter can then keep selected deal changes moving between monday CRM and ScaleBespoke.
The Apptivo REST adapter imports Opportunities and the supported Contact context used to build a reviewable deal record.
The Oracle CX Sales REST connector reads Opportunities from the configured Oracle environment and normalizes them into the ScaleBespoke deal model.
The Pega Sales Automation adapter authenticates against the configured API and imports supported Opportunity records for CRM review.
Zendesk tickets and their status are imported as support records for follow-up—not presented as sales opportunities in the CRM pipeline.
4 connections
Drawing files, construction-document environments and site tasks connect at the order and installation level, keeping external project collaboration tied to the work inside ScaleBespoke.
Upload, version and route DWG drawing files — the native format used by AutoCAD and most CAD tools — through the same approval workflow as everything else on the order.
Push drawings and pull BCF issue threads to and from a Catenda (formerly BIMsync) project using your own Catenda Boost account — the same connected-document approach as CAD & Drawing Management, extended to a shared contractor workspace.
Connect to an Asite Adoddle document and forms workspace using your own Asite service-account credentials — for teams whose main contractor or client already standardizes on Asite.
Pull location-based tasks from a Dalux Build project onto your own installation schedule, push status updates back, and see a live burn-up chart of on-site progress. Connect with your own Dalux company API key.
4 connections
Carrier capabilities are deliberately separated: Bring supports tracking and controlled booking, DHL and FedEx provide tracking, while Scanfreight remains a direct-contact workflow.
Real tracking and booking with Posten Bring, Norway's largest carrier — booking defaults to test mode until you explicitly turn it off, so no live shipment is created by accident.
Real-time DHL shipment tracking through DHL's own Shipment Tracking API. Booking and labels are a separate, enterprise-onboarding-gated DHL integration, not included here.
Real-time FedEx tracking via FedEx's own OAuth2 Track API. As with DHL, booking and labels need a separate, account-specific FedEx integration not included here.
A real Norwegian freight forwarder. Scanfreight has no public developer API, so this is an honest listing rather than a live connection — arrange shipments directly with their operations team.
1 connections
External booking is kept separate from ScaleBespoke Resource Planning so a website appointment is never confused with operational team capacity.
Book a demo directly from the site, no back-and-forth email required.
12 connections
Enquiries from your website and your social channels reach the CRM through one intake, and the platform's own AI can be consumed by systems outside it. Social cards state exactly which direction is live today and which still needs your own platform credentials.
Point ScaleBespoke at a website and it crawls every page, finds every form, reads each field with its visible label and proposes a mapping to CRM fields in English, Norwegian, German or Latvian. It recognises which form technology the site runs, and a Test button sends a sample submission through the real intake, reports which pipeline and stage it landed in, then removes it. Submissions pass spam screening before they reach the CRM.
Form discovery recognises Gravity Forms from the markup it renders, proposes the field mapping, and submissions reach the CRM through the token-gated intake endpoint — a per-site configuration, not a plugin you install on your side.
Form discovery recognises WPForms from the markup it renders, proposes the field mapping, and submissions reach the CRM through the token-gated intake endpoint — a per-site configuration, not a plugin you install on your side.
Form discovery recognises Contact Form 7 from the markup it renders, proposes the field mapping, and submissions reach the CRM through the token-gated intake endpoint — a per-site configuration, not a plugin you install on your side.
Form discovery recognises HubSpot forms from the markup it renders, proposes the field mapping, and submissions reach the CRM through the token-gated intake endpoint — a per-site configuration, not a plugin you install on your side.
Form discovery recognises Typeform from the markup it renders, proposes the field mapping, and submissions reach the CRM through the token-gated intake endpoint — a per-site configuration, not a plugin you install on your side.
Form discovery recognises Jotform from the markup it renders, proposes the field mapping, and submissions reach the CRM through the token-gated intake endpoint — a per-site configuration, not a plugin you install on your side.
Instagram direct messages arrive through Meta's signature-verified Instagram Messaging webhook and become CRM conversations. Publishing Gallery photos to Instagram is scheduled in Social Publisher but the publish call is not yet connected — an unconnected post reports a clear failure rather than a false success. Requires your own Meta developer app.
Facebook Page messages arrive through Meta's Messenger webhook with HMAC-verified signatures and are routed into the CRM like any other enquiry. Page publishing from Social Publisher is scheduled but not yet connected to the live API. Requires your own Meta developer app.
LinkedIn has no public API for inbound member direct messages, so what ScaleBespoke captures is comments on your company's own posts, via the Community Management API's notifications. Publishing from Social Publisher is scheduled but not yet connected to the live API. Requires your own LinkedIn developer application.
Comments and DMs arrive via the TikTok API for Business with TikTok's own signed webhooks; comment replies are limited to ad-scoped comments by the platform itself. Publishing uses the real Content Posting (Direct Post) API with a video upload path. Fully implemented, awaiting your own TikTok developer credentials to go live.
The same AI that powers Peter inside the platform is available to systems outside it. Register a consumer — your public website's assistant, a bulk translation job, a partner tool — and it calls ScaleBespoke for completions and glossary-aware translation on your own provider key, with a per-consumer on/off switch, model choice, monthly token cap and usage figures. One bill, one place to switch things off. A client's public website assistant already runs on it.
Connected beyond the screen
A completed order still has to be packed, booked, tracked, installed and reconciled. Carrier updates, site tasks and finance handoffs stay attached to the same job—so delivery does not become a separate story the moment the product leaves the workshop.