Microsoft Dynamics NAV and Pipedrive integration

What moves between them

Data flows primarily from Microsoft Dynamics NAV into Pipedrive. New and updated customers in NAV are pushed via webhook to Pipedrive as organizations, and customer contact records in NAV sync to Pipedrive persons. Sales orders from NAV map to Pipedrive deals so the sales pipeline reflects backlog. In the reverse direction, Pipedrive webhooks push deal creation and updates back into NAV as sales orders or opportunity records, so your sales team's pipeline is visible in your operational forecast. Customer dimension and territory codes in NAV are mapped to Pipedrive custom fields and pipeline stages to maintain alignment on how deals are categorized.

How ml-connector handles it

ml-connector stores both credential sets encrypted and manages two separate webhook channels: one from NAV to Pipedrive for customer and sales order events, and one from Pipedrive back to NAV for deal and organization changes. On the NAV side, ml-connector subscribes to webhooks and renews subscriptions every 2 days to prevent 3-day expiry, and validates each notification using the clientState field. On the Pipedrive side, ml-connector verifies the HMAC-SHA256 signature on each incoming webhook using X-Pipedrive-Signature and the webhook secret. Customer and organization records are matched by legal name and tax ID to prevent duplicates, and sales order to deal mappings track the relationship so updates in one system flow to the other. ml-connector handles NAV's OData polling fallback if a webhook subscription expires or customer prefers polling, and it respects Pipedrive's token budget by batching reads and tracking daily usage per plan multiplier. Every record carries a full audit trail, and failed syncs are retried with exponential backoff.

A real-world example

A small distribution company runs Microsoft Dynamics NAV for order fulfillment and accounting, and uses Pipedrive to manage a sales team across three territories. Before the integration, salespeople entered deals manually in Pipedrive and the finance team exported customer lists and sales orders from NAV into a spreadsheet to reconcile against Pipedrive each week. Territory managers often updated customer records in NAV without telling sales, causing deals in Pipedrive to reference stale contact info or wrong customer codes. With NAV and Pipedrive connected, every new customer added in NAV appears in Pipedrive within seconds, salespeople see accurate contact history and customer codes in their deals, and sales orders flow from Pipedrive back into NAV without manual entry. The weekly reconciliation step is gone, and the sales team and finance team see the same customers and backlog.

What you can do

• •Sync customers, contacts, and tax IDs from Microsoft Dynamics NAV to Pipedrive organizations and persons.
• •Create and update Pipedrive deals as sales orders in NAV, keeping your sales pipeline aligned with your operational backlog.
• •Renew Microsoft Dynamics NAV webhook subscriptions automatically every 2 days to prevent 3-day expiry.
• •Verify Pipedrive webhook signatures with HMAC-SHA256 and handle both v1 and v2 webhook event formats.
• •Respect Pipedrive token budget by tracking daily usage per plan multiplier and batching reads across both systems.

Questions

Which direction does data move between Microsoft Dynamics NAV and Pipedrive?

The primary flow is from NAV to Pipedrive. Customers and sales orders in NAV push to Pipedrive as organizations and deals. In the reverse direction, Pipedrive deals and organization updates push back into NAV so your sales pipeline and your backlog stay synchronized. Customer dimension codes in NAV map to Pipedrive custom fields and pipeline stages to maintain alignment.

How does ml-connector handle the 3-day webhook subscription expiry in Microsoft Dynamics NAV?

ml-connector tracks NAV webhook subscription timestamps and renews each subscription every 2 days, staying well ahead of the 3-day expiry window. If a subscription expires before renewal completes, ml-connector falls back to OData polling so no customer or sales order changes are missed. Subscription renewal uses the same OAuth2 credentials as the initial subscription.

How does ml-connector verify Pipedrive webhooks and respect its token budget?

On every incoming Pipedrive webhook, ml-connector verifies the X-Pipedrive-Signature header using HMAC-SHA256 and the registered webhook secret, rejecting any unverified notification. ml-connector tracks daily token consumption against your Pipedrive plan multiplier and batches reads to stay within budget, prioritizing customer syncs over large entity lists during high-volume periods.