By Naomi Fletcher, SaaS integration support lead with 9 years of experience troubleshooting accounting, CRM, and payroll connections
Last reviewed: July 22, 2026
FreshBooks business owners and authorized admins can connect external applications for CRM, payroll, scheduling, payments, and workflow automation. Integration problems should be traced through the connected business, authorization status, sync rules, and source application before records are recreated manually.
This independent guide is not affiliated with FreshBooks.
Check the active business first. One FreshBooks login can expose several companies, while an integration is normally authorized against one selected business.
What FreshBooks Integrations Do
FreshBooks is cloud accounting and invoicing software for small businesses and independent professionals. Its App Store and support documentation cover connections for functions such as customer management, payroll, scheduling, payments, mailing, revenue imports, and no-code automation.
An integration lets two systems exchange selected information. That may mean:
- creating a FreshBooks client from another application;
- sending invoice or payment activity back to a CRM;
- importing payroll records as expenses or journal entries;
- triggering an automated task after a FreshBooks event;
- adding functionality that FreshBooks does not provide directly.
The systems remain separate.
Connecting an application does not merge both databases into one master record. Deleting information in one service may not delete its copy in the other, and a successful authorization does not guarantee that every old record will be imported.
Small distinction. Large consequences.
Pick the Correct FreshBooks Route
| Your task | Correct starting point |
|---|---|
| Enter the accounting business | FreshBooks login |
| Browse available integrations | FreshBooks App Store |
| Review connected applications | Apps > Connected Apps |
| Remove a normal integration | Disconnect beside the connected app |
| Create a no-code automation | Zapier |
| Sync sales contacts | HubSpot integration |
| Import U.S. payroll expenses | Gusto app |
| Import Canadian payroll accounting | Wagepoint app |
| Build custom software access | FreshBooks API documentation |
| Check a broad platform failure | FreshBooks status page |
FreshBooks says connected applications can be reviewed from the Apps section. Most can be removed by selecting Disconnect beside the relevant application, although some integrations may also require changes inside the external service.
Do this first: identify which application created the questionable record. Skip deleting the FreshBooks copy until the integration’s behavior is understood.
Log In to the Correct Business
FreshBooks supports direct email-and-password access plus Google and Apple sign-in. Users who work across several businesses choose the intended company after authentication.
That selection is part of integration setup.
HubSpot, for example, asks the owner to choose a FreshBooks business when several are available. Wagepoint also requires the user to select the specific business that should receive its payroll transactions.
A connection can therefore work perfectly while sending data to the wrong company.
Confirm:
- FreshBooks business name;
- external account or workspace;
- user role;
- connected email;
- integration status;
- latest sync time where displayed.
Priority one is the business pair. Skip reconnecting until both sides are identified.
Do not provide an external consultant with the owner’s credentials merely so they can configure an application. Use an appropriate FreshBooks role and follow the integration’s authorization process.
Connect and Remove FreshBooks Apps
FreshBooks places recommended and connected applications under the Apps section and maintains a broader App Store for available integrations. The App Store currently advertises more than 100 partner connections.
A typical connection asks the user to:
- Open the integration listing.
- Sign in to FreshBooks.
- Select the intended business.
- Review the access request.
- Choose Allow or the equivalent authorization control.
- Finish configuration in the external application.
Read the authorization screen before approving it. An accounting integration may need access to clients, invoices, payments, expenses, or reports in order to perform its advertised function.
Disconnect unused applications from:
Apps > Connected Apps > Disconnect
FreshBooks also notes that an application may be removable from inside the third-party service.
Disconnecting usually stops future synchronization. It should not be assumed to erase records already created in either system.
Review existing data first. Skip removing the connection in the middle of payroll processing or a large import.
HubSpot Sync: Clients, Invoices, and Payments
The FreshBooks HubSpot integration syncs qualifying HubSpot contacts into FreshBooks as clients. Contacts must be in the Customer or Evangelist lifecycle stage and need an email address for the documented sync to work.
FreshBooks says the initial and ongoing sync can take roughly 1 to 10 minutes after the necessary conditions are met. Synced FreshBooks invoice and payment activity can also appear in HubSpot contact records.
Two hands-on details matter.
When several FreshBooks clients use the same email address, HubSpot syncs contact details to the most recently created FreshBooks client. Deleting a contact or client from one service does not automatically remove its counterpart from the other service.
A later update can even recreate a deleted HubSpot contact when its matching FreshBooks client is changed.
Do not test the integration with duplicate production contacts. Use one controlled record, wait through the stated sync window, and confirm which system should be treated as the preferred source for each field.
If invoices appear missing in HubSpot, inspect the contact’s activity filters and confirm that integration activity is enabled.
Zapier Automations
Zapier connects FreshBooks to other applications through automations called Zaps. Each Zap has a trigger and one or more actions: an event in one application causes work to occur in another.
FreshBooks says the owner or an admin can authorize Zapier access. The setup includes choosing FreshBooks as one application, selecting a trigger and action, signing in, and approving access.
Automation can create quiet duplication.
Suppose a website form creates a client in FreshBooks through Zapier while HubSpot also creates that client after its lifecycle stage changes. Both automations may be functioning as configured, yet the business receives two client records.
Map the workflow on paper before activating it:
- Which system creates the client?
- Which system updates the client?
- What unique field is used to match records?
- What happens when the email changes?
- What happens when a record is deleted?
- Can the same trigger fire more than once?
Priority two is the trigger history. Skip manually recreating a failed action until Zapier shows whether it is queued, errored, or already completed.
Gusto App and Duplicate Payroll Expenses
The separate Gusto app is intended for U.S. businesses with larger teams or more complex payroll and HR needs. It can automatically import payroll runs into FreshBooks as expenses using selected expense categories.
This is not the same product as FreshBooks Payroll powered by Gusto, which is operated inside FreshBooks.
The Gusto app can import items including gross wages, employer taxes, contractor payments, and employee reimbursements. The business can choose whether the entry date uses the check date, debit date, or end of pay period.
That date choice affects reporting.
A second friction appears when the payroll bank account is also connected to FreshBooks. The Gusto integration can create payroll expenses, while the bank feed imports the related withdrawals as additional expenses. FreshBooks recommends working with an accountant on mappings and reconciliation because the two sources can otherwise look like duplicated payroll costs.
Do not delete the more detailed Gusto entry merely because the bank transaction arrived later.
Wagepoint for Canadian Payroll
FreshBooks documents Wagepoint as a separate paid payroll integration for Canadian businesses. Wagepoint can create transactions in the FreshBooks Chart of Accounts after payroll runs.
Setup requires:
- connecting FreshBooks from Wagepoint;
- choosing the intended business;
- completing Chart of Accounts mappings;
- selecting a payroll bank account;
- configuring automatic sync options.
The status changes to Connected after required mappings are complete. Wagepoint also supports manual exports of payroll journal entries and subscription invoices.
The same duplicate-expense concern applies. A connected payroll bank account can import withdrawals while Wagepoint creates more detailed payroll records. FreshBooks recommends removing payroll-related expenses produced by the bank connection when they duplicate the integration’s accounting entries.
Check the payroll period, total, and journal mapping before deleting anything.
Rules and availability vary by region. Use Gusto documentation for U.S. businesses and Wagepoint guidance for Canadian businesses rather than combining their steps.
Why an Integration Stops Syncing
A missing sync usually belongs to one of five categories:
Authorization expired: The external app may need to be reconnected.
Wrong business selected: Data is reaching another FreshBooks company.
Required source data is absent: HubSpot contacts, for example, need the documented lifecycle stage and email address.
Sync is disabled: Gusto Auto-Sync, Wagepoint Automatic Sync, or a Zap may be turned off.
The operation is delayed or failed externally: Review the external application’s activity or task history.
A FreshBooks outage is another possibility when several unrelated features fail simultaneously. FreshBooks directs users to its status page for current availability information.
Check the source application first. Skip changing accounting records until the sync state is known.
FreshBooks API Access
FreshBooks provides an application programming interface (API) for developers who need to automate account activity or build a custom integration.
API work is different from installing an App Store product.
A developer must define which business data the application needs, how authorization will work, how records will be matched, and how errors or repeated requests will be handled. Custom integrations should be tested outside critical production workflows before they are allowed to create or modify accounting records.
Do not place private application credentials in public code repositories, ordinary support messages, or browser-side scripts where they can be exposed.
FreshBooks’ API documentation should control implementation details because endpoints and supported behavior can change. The user-facing FreshBooks password should not be treated as an API credential.
FreshBooks Integration FAQ
Where can I see connected FreshBooks apps?
Open Apps, then review Connected Apps.
Does disconnecting an app delete imported records?
Not necessarily. It normally stops the connection; records already created may remain and require separate review.
Why is HubSpot not creating a FreshBooks client?
The HubSpot contact must have an email and use the Customer or Evangelist lifecycle stage. Sync may then take roughly 1 to 10 minutes.
Why did HubSpot create the wrong client match?
When multiple FreshBooks clients share one email, HubSpot uses the most recently created client.
Who can connect Zapier to FreshBooks?
The FreshBooks owner or an admin.
Why do payroll expenses appear twice?
A payroll integration may create detailed FreshBooks entries while the connected bank imports the related withdrawal. Review the mapping and reconcile the two sources before removing a record.
Is the Gusto app the same as FreshBooks Payroll?
No. FreshBooks Payroll runs inside FreshBooks; the separate Gusto app connects an external Gusto account and imports payroll accounting records.
Can FreshBooks connect to custom software?
Yes. Developers can use the FreshBooks API to build integrations and automate supported account functions.