FreshBooks and Tableau integration

What moves between them

FreshBooks invoice and expense events flow into Tableau datasources. As FreshBooks fires invoice.create, invoice.update, expense.create, and expense.update webhooks, ml-connector receives them, extracts the financial dimensions (amount, date, client, category, account), and upserts rows into Tableau datasources mapped to those dimensions. Reference data such as clients and chart of accounts are synced on demand or on a schedule so Tableau dimensional tables stay aligned with FreshBooks source records. Tableau views remain read-only; ml-connector never writes to them.

How ml-connector handles it

ml-connector stores FreshBooks OAuth tokens encrypted and refreshes them before expiry using the client credentials stored in the configuration. When a FreshBooks webhook arrives, ml-connector validates the HMAC-SHA256 signature using the webhook secret, parses the JSON payload, and extracts the financial record details. For each record, it calls FreshBooks APIs to retrieve the full context (client name, account code, category), then transforms the data into Tableau's dimensional schema. It then calls Tableau's REST API using PAT-based session token auth, handling token expiry by re-authenticating. Tableau Cloud and Server use different base URLs, so ml-connector is configured per deployment type and caches the correct endpoint. If a webhook arrives out of order or a Tableau insert fails, ml-connector retries with exponential backoff and logs every attempt to the audit trail so failed records can be replayed when the issue is resolved.

A real-world example

A mid-sized professional services firm uses FreshBooks for client invoicing and expense tracking across multiple projects and cost centers. The finance team needs to track invoice aging by client, monitor project profitability, and analyze spending trends by expense category. Before the integration, someone exported FreshBooks reports weekly and rebuilt Tableau dashboards by hand, causing delays and data staleness. With FreshBooks and Tableau connected, invoice and expense records flow automatically into Tableau datasources the moment they are created or updated in FreshBooks, so dashboards refresh in near real-time and the finance team can spot overages, slow payments, and cost trends instantly without manual intervention.

What you can do

• •Receive FreshBooks invoice and expense webhooks and load them into Tableau datasources with full dimension mapping.
• •Authenticate FreshBooks via OAuth 2.0 user-delegated flow and Tableau via Personal Access Token session exchange.
• •Validate HMAC-SHA256 signatures on incoming FreshBooks webhooks to ensure integrity and prevent replay.
• •Support both Tableau Cloud and Tableau Server deployments by routing to the correct API endpoint per configuration.
• •Maintain a complete audit trail of every record received, transformed, and loaded so failed syncs can be investigated and replayed.

Questions

What FreshBooks records flow into Tableau?

Invoices, expenses, bills, and payments from FreshBooks are transformed and loaded into Tableau datasources. Clients and chart of accounts are synced as reference dimensions so every invoice and expense record can be joined to its client name and GL account code. Tableau views are read-only, so ml-connector writes only to datasources.

How does ml-connector handle FreshBooks webhook retries and failures?

ml-connector validates the HMAC-SHA256 signature on each webhook and discards unsigned or tampered payloads. If a FreshBooks API call fails during transformation or a Tableau insert fails, ml-connector backs off exponentially and retries. Every attempt is logged to the audit trail, so your team can see which records succeeded, which are pending retry, and which require investigation.

Does the integration work with both Tableau Cloud and Tableau Server?

Yes. ml-connector is configured with the Tableau deployment type and the correct base URL for your instance. Tableau Cloud uses pod-specific URLs like https://10ay.online.tableau.com/api/3.29/, while Tableau Server uses your own hostname. Session token expiry is handled automatically in both cases.