FreshBooks and Pipedrive integration

What moves between them

The main flow moves from FreshBooks into Pipedrive. When a client is created or updated in FreshBooks, ml-connector writes it as an organization to Pipedrive with the client name, address, and currency. When an invoice is created or updated in FreshBooks, ml-connector creates or updates a deal in Pipedrive linked to the matching organization, with invoice amount, due date, and invoice status mapped to custom deal fields. Invoice status transitions (draft to sent to viewed to paid) update the deal stage, advancing it through the pipeline. Bill records in FreshBooks are not synced to Pipedrive. Data moves on FreshBooks' webhook delivery schedule, typically within a few minutes of a change in FreshBooks.

How ml-connector handles it

ml-connector listens for FreshBooks webhook POST requests at a dedicated endpoint, verifies the HMAC-SHA256 signature in the X-FreshBooks-Hmac-SHA256 header against the shared webhook secret, and decodes the payload. For client events (client.create, client.update), it looks up the organization in Pipedrive by FreshBooks client ID; if not found, it creates a new organization with the client name, address, and currency mapped to Pipedrive fields. For invoice events (invoice.create, invoice.update), it ensures the matching organization exists in Pipedrive first, then creates or updates a deal linked to that organization. Invoice totals, due dates, and status (draft, sent, viewed, paid, overdue) map to custom deal fields and pipeline stage. FreshBooks and Pipedrive both support OAuth2, but use different token formats and lifetimes; ml-connector stores both credential sets and handles each vendor's token refresh independently. Pipedrive's rate limits (20 to 480 requests per 2 seconds depending on plan and auth type) are respected via queuing; if a write hits the limit, ml-connector backs off and retries. All records carry full audit trail for replay if a Pipedrive write fails.

A real-world example

A small professional services firm uses FreshBooks to manage invoicing and expenses, and Pipedrive to track sales deals. Before the integration, the sales team tracked revenue manually by searching Pipedrive notes or spreadsheets, and the accounting team had no visibility into which deals had turned into invoiced revenue. With FreshBooks and Pipedrive connected, each client created in FreshBooks appears as an organization in Pipedrive, and each invoice is represented as a deal showing amount, due date, and payment status. When an invoice is marked paid in FreshBooks, the deal advances automatically in the pipeline. The sales team can now see which deals have been invoiced and which invoices are outstanding, and the accounting team has a clear revenue pipeline view without manual work.

What you can do

• •Sync FreshBooks clients into Pipedrive organizations with address and currency information preserved.
• •Create and update Pipedrive deals from FreshBooks invoices, linked to the correct organization.
• •Map invoice status (sent, viewed, paid, overdue) to Pipedrive deal custom fields and pipeline stages.
• •Verify FreshBooks webhook signatures with HMAC-SHA256 and handle OAuth2 token refresh for both platforms.
• •Track every record with a full audit trail for replay and reconciliation if a Pipedrive write fails.

Questions

Which direction does data move between FreshBooks and Pipedrive?

The main flow is from FreshBooks into Pipedrive. Clients become organizations and invoices become deals in Pipedrive. FreshBooks bills are not synced to Pipedrive because Pipedrive is CRM-only and has no accounting features. Updates to clients and invoices in FreshBooks flow into Pipedrive via webhook, but changes in Pipedrive do not flow back to FreshBooks.

How does ml-connector handle FreshBooks webhooks and Pipedrive rate limits?

ml-connector verifies the HMAC-SHA256 signature in FreshBooks webhook headers before processing, ensuring only legitimate events are synced. Pipedrive imposes burst rate limits of 20 to 480 requests per 2 seconds depending on plan and authentication type. ml-connector queues writes, respects the limit, and backs off if a write hits the ceiling, retrying when capacity returns.

What happens if an invoice is created in FreshBooks before its client is synced to Pipedrive?

ml-connector ensures the matching organization exists in Pipedrive before creating the deal. If the client is not yet synced, ml-connector first creates the organization in Pipedrive, then creates the deal linked to that organization. This ensures referential integrity and prevents orphaned deals.