Oracle NetSuite and Monday.com integration

What moves between them

Records flow primarily from Oracle NetSuite into Monday.com. When a vendor, purchase order, or invoice is created or edited in NetSuite, ml-connector receives the Event Subscription webhook and creates or updates a corresponding item on a customer-configured Monday.com board. The item's columns (fields) are mapped to NetSuite fields such as vendor name, PO amount, due date, and approval status. The integration respects Monday.com column value constraints and batch complexity limits, queuing large updates and respecting the 40-mutation-per-minute cap to avoid throttling.

How ml-connector handles it

ml-connector handles the OAuth dance on both sides: NetSuite's 60-minute token lifecycle requires token refresh before expiry, and Monday.com's authorization code flow runs once at setup and relies on the long-lived access token returned. On the NetSuite side, the integration registers Event Subscriptions for specified record types (e.g. vendorBill, purchaseOrder) and receives webhook payloads; if Event Subscriptions are not available or coverage is incomplete, ml-connector can poll SuiteQL on a schedule instead. On the Monday.com side, the integration maps NetSuite field values to GraphQL mutation arguments, JSON-encoding column values as required by Monday.com's schema, and batches mutations to stay within the complexity budget and the 40-per-minute rate limit. Because Monday.com has no native ERP objects, the board and column schema are customer-defined, and ml-connector uses a configuration file to specify which NetSuite record type maps to which Monday.com board and which NetSuite fields map to which columns. Webhook payloads from NetSuite carry a timestamp and record ID, allowing ml-connector to idempotently create or update Monday.com items keyed on NetSuite ID; if the same NetSuite ID arrives twice (webhook retry), the same Monday.com item is updated, never duplicated.

A real-world example

A mid-sized manufacturing company runs Oracle NetSuite for procurement and accounting and uses Monday.com to track purchase orders and supplier performance across regional warehouses. Before the integration, the procurement team handled PO creation in NetSuite, then manually created corresponding work items in Monday.com to track approval and delivery status. The finance team separately received vendor invoices in NetSuite and had no visibility into Monday.com's tracking, creating a gap between what procurement was tracking and what finance was paying. With NetSuite and Monday.com connected, every new or edited purchase order and vendor invoice automatically appears as a Monday.com item with columns for vendor name, order amount, invoice status, and due date. Procurement and finance now see the same source data, and approval workflows and delivery tracking happen on the same board, eliminating the manual sync step and keeping finance in step with operations.

What you can do

• •Sync Oracle NetSuite vendors, purchase orders, and invoices to Monday.com work items on a customer-configured board.
• •Create new Monday.com items automatically when NetSuite records are created via Event Subscriptions or scheduled polling.
• •Update existing Monday.com items when NetSuite records change, mapping NetSuite fields to column values without re-entry.
• •Handle OAuth 2.0 authentication on both sides, manage NetSuite token refresh, and respect Monday.com rate limits and mutation complexity budgets.
• •Maintain a full audit trail of every record sync with timestamps and NetSuite source IDs for replay and reconciliation.

Questions

Which records flow from Oracle NetSuite to Monday.com?

Vendors, purchase orders, vendor bills, invoices, customers, and GL accounts can be synced. The specific records and the board and columns they map to are configured per customer, since Monday.com boards are customer-defined structures with no native ERP schema. ml-connector respects the column types and constraints defined in the target Monday.com board.

Does the integration use NetSuite Event Subscriptions or polling?

Event Subscriptions are preferred where available, since they push record changes immediately to ml-connector, which then updates Monday.com. Not all NetSuite record types support Event Subscriptions (e.g. some custom records do not). For unsupported types or additional coverage, ml-connector can poll SuiteQL on a schedule. The choice is configurable per customer.

How does ml-connector handle Monday.com's rate limits and complexity constraints?

Monday.com enforces a 40-board-mutation-per-minute cap and a 5,000,000-point complexity budget per GraphQL query. ml-connector batches column value updates, queues mutations if the cap is reached, and splits large queries into smaller paginated passes. The integration tracks usage and backs off if limits are approached, ensuring no mutations are dropped or rate-limited.