Microsoft Dynamics NAV and Monday.com integration

What moves between them

Vendor invoices and purchase orders flow from Microsoft Dynamics NAV into Monday.com as board items, with columns for amount, due date, vendor, and posting status. Vendor master data from NAV populates Monday column options so team members select from the actual vendor list. When team members update the status column in Monday (e.g. from 'Pending Review' to 'Approved'), ml-connector writes the status change back into NAV as a journal line or updates the invoice approval flag. Dimension values such as cost center are synced in both directions so Monday items reflect current NAV dimensions and mapped back when the status changes.

How ml-connector handles it

ml-connector stores both NAV and Monday.com credentials encrypted and refreshes the OAuth tokens as needed. It subscribes to NAV vendor invoice webhooks and polls NAV purchase orders on a schedule, since purchaseOrders is not in the standard NAV webhook subscription list. New invoices land on the Monday board as items with columns auto-populated from NAV data (vendor code, amount, due date, journal status). Monday.com's GraphQL mutations are called to create and update items; column values are JSON-encoded strings as required by the Monday API. When an item's status column changes in Monday, ml-connector reads the change via webhook and updates the corresponding invoice or PO record in NAV. NAV's 3-day webhook subscription is renewed before expiry so the stream is never broken. Monday rate limits are handled with exponential backoff and jitter. Every record carries a timestamp and source, and failed writes are queued for replay when the downstream API recovers.

A real-world example

A mid-sized distribution company runs Microsoft Dynamics NAV for purchasing and finance and uses Monday.com for general team project tracking. Before the integration, the accounts payable team managed vendor invoices in NAV but had no visibility into approval workflows outside the ERP, and purchase orders were tracked on spreadsheets. With NAV and Monday.com connected, new invoices automatically appear as items on a Monday board with vendor name, amount, and due date pre-filled from NAV. Team members and supervisors can comment on invoices, update status, and flag issues in one place, and when an invoice is approved in Monday, the approval flows back into NAV's approval workflow without re-entry. The finance team sees what is pending across the company, and the lag between PO receipt and payment is reduced.

What you can do

• •Sync vendor invoices from Microsoft Dynamics NAV to Monday.com as board items with amount, due date, vendor, and status columns.
• •Sync purchase orders from NAV purchase order tables into Monday as tracked items with material and delivery details.
• •Renew NAV webhook subscriptions automatically before 3-day expiry to keep the push stream unbroken.
• •Map NAV vendor master and dimension tables to Monday column options so team members select from live NAV data.
• •Write approval and posting status changes from Monday back into NAV journal lines and invoice records.

Questions

Which direction does data move between Microsoft Dynamics NAV and Monday.com?

Vendor invoices and purchase orders move from NAV into Monday.com as board items. Vendor master data and dimensions are synced in both directions so column options stay current. When team members update the status column in Monday, the change flows back into NAV as an approval or posting status. GL entries themselves are not synced back into NAV because NAV GL entries are immutable once posted.

Why does ml-connector poll purchase orders instead of relying on NAV webhooks?

Microsoft Dynamics NAV webhooks support vendors, purchaseInvoices, items, and many other entities, but purchaseOrders is not in the standard webhook subscription list. ml-connector polls the purchaseOrders endpoint on a schedule you control to catch new and updated POs, ensuring no orders are missed while invoices are pushed in real time.

How does the integration handle NAV's 3-day webhook subscription expiry?

ml-connector tracks the expiry date of each NAV webhook subscription and renews it automatically before the 3-day window closes. A renewal failure triggers an alert so your team can investigate, but under normal operation the subscription is never allowed to lapse and the data stream remains unbroken.