How does ml-connector sync data if Sage 300 has no webhooks?

ml-connector polls Sage 300 on a scheduled cadence using OData date filters and pagination to retrieve new and changed records since the last run. The polling interval is configurable and does not require Sage 300 to push any notifications. Each sync run queries vendors, customers, or GL accounts modified after the previous run timestamp.

What do Sage 300 records look like when they arrive in Monday.com?

Each Sage 300 record becomes a Monday.com item (row) on the target board. A vendor record appears as an item with columns for vendor number, name, payment terms, and other key fields. You can add additional Monday.com columns for project codes, approval status, or other metadata that exists only in Monday.com.

Does the integration work if Sage 300 is behind a firewall or on a private network?

Sage 300 is self-hosted on the customer's Windows IIS server, so ml-connector must be able to reach that server's HTTPS endpoint. If Sage 300 is behind a firewall, the IIS server must be exposed to the internet or to ml-connector's IP range. Once the URL is reachable, ml-connector stores and sends the HTTP Basic Auth credentials with every call.

Sage 300Monday.com

Sage 300 and Monday.com integration

Sage 300 is your ERP source of truth for vendors, customers, and the chart of accounts. Monday.com is where your teams track projects and collaborate. Connecting the two keeps your finance reference data visible in Monday.com boards without manual re-entry. Vendor lists, customer master records, and GL accounts sync from Sage 300 to Monday.com on a schedule you control, and the board model lets your team add their own columns for project allocation, cost center tags, or approval status. ml-connector handles the difference between Sage 300's REST API and Monday.com's GraphQL, and it keeps the sync running even when the cadence changes.

How Sage 300 works

Sage 300 exposes accounts payable vendors, accounts receivable customers, general ledger accounts, segments, structures, purchase orders, sales orders, and inventory items through REST endpoints with OData filtering. Each customer deploys Sage 300 on their own Windows IIS server with SQL Server backend, so there is no Sage-managed cloud URL. Authentication is HTTP Basic Auth with base64-encoded uppercase username and password sent in every request. The API user must be created in Administrative Services with Web API security group assigned, and the IIS server must have Anonymous Authentication enabled and Windows Authentication disabled. Sage 300 has no webhooks or push notifications, so all sync is pull-based polling using OData date filters and pagination.

How Monday.com works

Monday.com organises work into boards containing items (rows) with typed columns (fields). All operations go through a single GraphQL endpoint at https://api.monday.com/v2 with mutations for creating and updating items and column values. Authentication is either a personal API token sent raw in the Authorization header or OAuth 2.0 with an access token. Monday.com supports webhooks for board-level events including item creation, column updates, item archival, and deletion, though webhooks require challenge-based verification at registration. Rate limits vary by plan, from 1,000 requests per minute at the Free tier to 5,000 per minute on Enterprise, with a complexity limit of 5,000,000 points per query. Column values in mutations must be JSON-encoded strings, and the platform has no sandbox, so testing uses a free developer account with test boards.

What moves between them

Master data flows from Sage 300 into Monday.com. Vendor records (APVendors), customer records (ARCustomers), and general ledger accounts (GLAccounts) are polled from Sage 300 on a daily or weekly cadence and synced to corresponding Monday.com boards where they appear as items. Each vendor, customer, or account becomes a row in its board, with columns mapped to key fields such as vendor name, status, and account code. General ledger accounts include the account number, description, and account type as columns. Because Sage 300 has no webhooks, polling triggers the sync at fixed intervals. Monday.com receives the data and can trigger notifications or cascading board changes when new items arrive.

How ml-connector handles it

ml-connector stores Sage 300 credentials as base64-encoded uppercase username and password and sends them in the Authorization header with every REST call. It polls Sage 300's OData endpoints using date filters and pagination to retrieve new and changed records since the last sync run. For Monday.com, ml-connector uses either a personal API token or OAuth access token and converts each Sage 300 record into a GraphQL mutation that creates or updates an item on the target board, setting column values as JSON-encoded strings. The mapping between Sage 300 fields and Monday.com columns is configured per board, so vendors map to one board structure and GL accounts to another. ml-connector respects Monday.com's rate limits (1,000 to 5,000 requests per minute depending on plan tier) and backs off on 429 responses. Because Sage 300 is self-hosted, ml-connector accepts the customer's full IIS URL per instance. Every sync run logs which records were added or updated, and a failure on the Monday.com side can be replayed once the board or token issue is resolved.

A real-world example

A mid-market distribution company runs Sage 300 on their local network for accounts payable and inventory. The accounts payable team used to maintain a spreadsheet of active vendors exported from Sage 300 and email it to the procurement team each week. With Sage 300 and Monday.com connected, new vendors and vendor status changes from Sage 300 appear automatically in a Monday.com board where the procurement team tracks supplier performance and compliance. The board includes columns for vendor name, payment terms, YTD spending, and approval status, some pulled from Sage 300 and others maintained directly in Monday.com. When a vendor is marked inactive in Sage 300, the sync updates the status in Monday.com, and the procurement team can see at a glance which suppliers are still active. Manual vendor spreadsheet exports are gone, and the data is always current.

What you can do

Sync Sage 300 vendor master records to a Monday.com board with automatic updates on schedule.
Sync Sage 300 customer records and AR attributes to a configurable Monday.com board.
Sync Sage 300 general ledger accounts and chart of accounts structure to Monday.com for visibility.
Handle Sage 300 HTTP Basic Authentication with uppercase credentials and polling via OData filters and pagination.
Support both Monday.com personal API tokens and OAuth access tokens, with configurable rate-limit handling per plan tier.

Questions

How does ml-connector sync data if Sage 300 has no webhooks?: ml-connector polls Sage 300 on a scheduled cadence using OData date filters and pagination to retrieve new and changed records since the last run. The polling interval is configurable and does not require Sage 300 to push any notifications. Each sync run queries vendors, customers, or GL accounts modified after the previous run timestamp.
What do Sage 300 records look like when they arrive in Monday.com?: Each Sage 300 record becomes a Monday.com item (row) on the target board. A vendor record appears as an item with columns for vendor number, name, payment terms, and other key fields. You can add additional Monday.com columns for project codes, approval status, or other metadata that exists only in Monday.com.
Does the integration work if Sage 300 is behind a firewall or on a private network?: Sage 300 is self-hosted on the customer's Windows IIS server, so ml-connector must be able to reach that server's HTTPS endpoint. If Sage 300 is behind a firewall, the IIS server must be exposed to the internet or to ml-connector's IP range. Once the URL is reachable, ml-connector stores and sends the HTTP Basic Auth credentials with every call.

Connect Sage 300 and Monday.com

Free to use. Add your credentials, ping your real systems, and see if we fit.

Get started