Service Fusion API, QuickBooks sync and Zapier: how to connect it, and how to get the reports it doesn't show

Service Fusion gives you three ways to get data in or out: the built-in QuickBooks sync, Zapier, and the API. They are not interchangeable. The sync only talks to one other app, Zapier only reaches a handful of actions, and the API is the one that can actually feed a live dashboard, but it sits on the highest-priced plan and Service Fusion turns it on by hand rather than letting you flip a switch yourself.

This page covers what each one does, where it stops, how to actually get API access switched on, and three ways to get the profit report Service Fusion's own screens don't show. Plan prices and feature gating come from Service Fusion's own pricing page, re-checked on 28 October 2026.

What does Service Fusion integrate with?

Service Fusion's own pages name a short list of built-in connections:

• QuickBooks Online and Desktop: on every plan, including Starter.
• Stripe: a mobile card reader for taking payments in the field.
• Flat Rate Integration: listed in the app menu for flat-rate pricing.
• ServiceCall.ai: Service Fusion's own phone and call-tracking add-on.
• GPS fleet tracking: a separate add-on.
• Acorn Finance: customer financing, mentioned on the home page.

Beyond that, Zapier reaches a longer list of apps, including HubSpot, Airtable, Google Calendar, Mailchimp, CompanyCam, Salesforce and Pipedrive. Those connections run through Zapier, so they only do what a Zapier trigger or action allows, not a full two-way sync.

How does the Service Fusion QuickBooks integration work?

Service Fusion's QuickBooks Online integration page states plainly what moves: invoices created in Service Fusion sync to QuickBooks Online, payments recorded in Service Fusion sync automatically, and customer records stay aligned between the two systems. You connect it from your account settings using Intuit's own OAuth sign-in, so you are authorizing Service Fusion to talk to your QuickBooks company file, not handing over a password.

Three things the page doesn't cover, so confirm them with Service Fusion before you rely on them for bookkeeping:

• Direction: the described flow is Service Fusion to QuickBooks. Nothing on Service Fusion's public pages says whether an edit made inside QuickBooks flows back.
• Job costs, classes and hours: not mentioned. If you run job costing in Service Fusion and want it to land in QuickBooks as a class or a job, ask for that in writing; don't assume it's included just because invoices sync.
• Error handling: nothing published on how a failed sync shows up or gets fixed.

If you're searching for how to export Service Fusion invoices to QuickBooks, this sync is the answer. There is no separate manual export step. What I'd actually do: check your first week of invoices against QuickBooks line by line, not just the totals. A sync that matches on total revenue can still misfile which customer or which job a payment belongs to, and that's the kind of error that's expensive to find three months later during tax prep.

Does Service Fusion have an API, and how do I get access?

Yes, but only on the top plan, and you can't switch it on yourself. Here is the actual sequence:

1. Confirm you're on Pro. Service Fusion's pricing page lists Open API Integration under Pro only, at $533 a month billed yearly or $627 billed monthly. Starter and Plus don't have it, at any price, including as a paid add-on. The full plan breakdown is in Service Fusion pricing.
2. Ask Service Fusion to turn it on for your account. Access isn't self-serve from a settings page. Email or call your account rep and ask them to enable API access, and ask for the current API documentation link while you're at it, since the public docs site doesn't show much without a login.
3. Register an OAuth 2.0 app to get credentials. Integration platforms that connect to Service Fusion describe registering an application with Service Fusion to receive a Client ID and Client Secret, the standard OAuth 2.0 pattern. That's the mechanism your developer will use, whether they're using a platform like that or writing the calls directly.
4. Get the request limits in writing. Service Fusion's own pages don't publish a rate limit, and the third-party sites that try to document one disagree with each other, which tells you they're guessing too. Don't let a developer build a live-polling dashboard on an assumed number. Ask Service Fusion directly what the limit is for your account before you scope the build.
5. Point your developer at the official docs for the actual calls. Service Fusion publishes API documentation at docs.servicefusion.com. The exact objects (customers, jobs, estimates, invoices and related records) and methods should be confirmed there against your account's access, since it's gated per account rather than uniformly switched on.

Here's my honest read on this, from building on a lot of vendor APIs: gating the API behind the single most expensive plan, with no self-serve toggle and no published rate limit, is a real cost and a real planning risk, not a minor inconvenience. If you also run Simpro, its access rules are in a separate guide, Simpro API. Before you commit to Pro just to get the API, check whether Zapier's six triggers and three actions already solve your actual problem. If what you want is "notify me and create a job when a lead comes in," Zapier does that on every plan. You only need Pro and the API when you want to read history back out, join it with other data, or build something that runs on a schedule rather than firing off one event at a time.

What can Zapier do with Service Fusion?

Zapier's own app page for Service Fusion lists six triggers and three actions, confirmed live:

Type	What it does
Trigger	New customer, new job, new estimate, new invoice, new tech created
Trigger	Job status updated, to a status you choose
Action	Create a customer
Action	Create a job
Action	Create a calendar task

Zapier's QuickBooks Online page suggests two uses built from these: create a Service Fusion customer automatically when one is added in QuickBooks, and update a QuickBooks invoice when a job's status changes in Service Fusion. Two of the ready-made templates there are marked Premium, which needs a paid Zapier plan.

This genuinely covers simple cases: a web form lead creating a job, a finished job triggering a review request. What it can't do is update an existing record beyond the one action listed, or read back a history of past jobs, so it will never feed a dashboard on its own. If your actual need is "look at everything that happened last month," Zapier is the wrong tool regardless of plan.

What reports does Service Fusion have, and can I customize them?

Service Fusion's pricing page lists reporting on every plan but doesn't name the report types on its public pages. In your own account, open the Reports menu to see what's actually there for your plan, and ask your onboarding contact which ones export to a file and in what format, since that's also not published.

Two specific gaps worth knowing before you build around this tool:

• No published report builder that joins jobs, crews and lead sources. Capterra reviewers describe filtered results and job reports as weak, which is one user's view, not a vendor claim, but it lines up with the fact that Service Fusion doesn't advertise a custom-report feature the way some competitors do.
• No ready-made templates. If you want a Jobber-style report template, Service Fusion doesn't publish one. The simplest version you can build yourself is a saved export plus one spreadsheet that reads the same file structure every month.

How do I get a profit-per-job report?

Three paths, cheapest to most work, and the right one depends on how often you need the answer:

1. Monthly spreadsheet. Export your sales and job reports, if your plan allows it, and join them by hand in a sheet. Fine for a monthly review; it stops scaling once the file gets large or you need it weekly.
2. Zapier to a sheet. Send each new job and invoice to Airtable or a spreadsheet as it happens, using the triggers above. You build a history automatically instead of re-exporting it, but you're still limited to what those six triggers capture.
3. API dashboard, on Pro. A developer reads jobs and invoices through the API and builds a live view by job, crew and customer, and can email the owner a weekly summary.

Pick the lowest one that actually answers your question. I've seen businesses pay for Pro specifically to get the API, then use it to build exactly the report a careful spreadsheet would have given them for free. Don't upgrade a plan to solve a problem a spreadsheet already solves.

How I'd approach this

When the gap is a report, a portal or a link, and the crew is happy with the app day to day, I keep Service Fusion and build the missing layer on top of it. The flat monthly fee doesn't change as you add technicians, so adding a layer is usually far cheaper than migrating to a different platform just to get better reporting. How that flat fee compares with per-user pricing is covered in Service Fusion vs Jobber vs Housecall Pro.

My starting point is always the cheapest path that solves the actual problem: a spreadsheet first, Zapier second, and the API only when the business genuinely needs live, joined data. If a client is already paying for Pro and the API is sitting there unused beyond what a spreadsheet would give them, I'll say so plainly. And if the real issue is the mobile app or support response time rather than data, that's not something an API layer fixes; see Service Fusion alternatives for that conversation instead.