QAD and Monday.com integration

What moves between them

The main flow runs from QAD into Monday.com. ml-connector reads QAD suppliers, purchase orders, supplier invoices, and goods receipts on a schedule and writes each one as an item on the board you nominate, with QAD fields landing in the column IDs that hold amount, status, due date, and vendor. New records create items and later changes update the matching item rather than duplicating it. In the other direction, Monday.com board events such as a status column change can be received and used to flag progress back to the QAD team. Monday.com is the operational view here, so ml-connector does not post financial entries into the ERP.

How ml-connector handles it

ml-connector stores both credential sets encrypted. It accepts the full QAD tenant URL per customer, since QAD publishes no shared base address, and sends the Monday.com personal token as the raw Authorization header with no Bearer prefix, or refreshes an OAuth2 token if one is used. Because Monday.com has no native ERP objects, you tell the connector the target board IDs and the column IDs for amount, status, due date, and vendor, and each QAD field is mapped to the matching column; values are written as JSON-encoded strings through the change_column_value mutation. Since QAD cloud is pull-only, it polls QAD on a schedule rather than waiting for a push, while it can also create Monday.com board webhooks and answer the challenge handshake to receive item and status events. Monday.com rate limits return HTTP 429 with a Retry-After header and cap board mutations at 40 per minute, so ml-connector honors that header and paces writes; item reads use cursor pagination that must finish in one pass, so it completes each board sync without long stalls to avoid a CursorExpiredError. Mutations carry an Idempotency-Key so a retry after a network failure does not create a duplicate item, and every record carries a full audit trail and can be replayed if a call fails.

A real-world example

A mid-sized contract manufacturer runs QAD Adaptive ERP for procurement and AP, while its operations and finance leads track open work on Monday.com boards. Before the integration, a coordinator copied new purchase orders and supplier invoices out of QAD into a Monday.com board by hand each morning so the team could see what was outstanding, and the board drifted out of step with the ERP by the afternoon. With QAD and Monday.com connected, each new PO and supplier invoice appears as an item on the right board automatically, with amount, status, and due date in the correct columns, and a status change on the board is sent back so the AP team knows when a record has been actioned. The manual morning copy is gone, and the board reflects the real state of the ERP.

What you can do

• •Push QAD suppliers, purchase orders, supplier invoices, and goods receipts onto the Monday.com boards you nominate.
• •Map each QAD field to the Monday.com column IDs that hold amount, status, due date, and vendor.
• •Update the matching Monday.com item when a QAD record changes, instead of creating duplicates.
• •Receive Monday.com board events such as status column changes to flag progress back to the QAD team.
• •Poll QAD on your schedule and honor Monday.com rate limits, with retries and a full audit trail on every record.

Questions

Which direction does data move between QAD and Monday.com?

The main flow is QAD into Monday.com. Suppliers, purchase orders, supplier invoices, and goods receipts are read from QAD and written as items on the boards you configure. Monday.com board events such as a status change can flow back to flag progress, but ml-connector does not post financial entries into QAD.

Monday.com has no invoice or PO objects, so how does the mapping work?

Everything in Monday.com is a board with items and typed columns, so there are no native ERP objects. You give ml-connector the target board IDs and the column IDs for amount, status, due date, and vendor, and each QAD field is mapped to the matching column. Column values are written as JSON-encoded strings through the change_column_value mutation, exactly as the Monday.com API requires.

How does the integration handle QAD's lack of webhooks and Monday.com's rate limits?

QAD cloud is pull-only, so ml-connector polls QAD on a schedule using the full tenant URL configured per customer rather than relying on a push. On the Monday.com side it honors the Retry-After header on 429 responses, paces board mutations under the 40-per-minute cap, and completes cursor-based item reads in one pass to avoid a CursorExpiredError.