monday.com Integration Guide for Production Scheduling with SkyPlanner APS

monday.com exposes one GraphQL API at POST https://api.monday.com/v2. It is versioned quarterly, and you pin a version with the API-Version header. Deprecations are announced at least six months ahead. (API versioning)

The objects a scheduling integration uses:

• Boards and groups, often used for stages or weeks.
• Items and subitems. An item is usually an order or job, and subitems hold operations.
• Column values: Status, Date, Timeline, Numbers, People, Dependency, Time Tracking, Connect Boards and Mirror.
• Webhooks for change events.

Reads use items_page nested in a board or group. The default page is 25 items and “the maximum is 500.” You continue with next_items_page, and “each cursor will expire 60 minutes after the first request.” Filter with query_params to read only open orders. (items_page)

Writes use create_item, create_subitem, change_column_value and change_multiple_column_values. The last one updates several columns of one item in a single call, which is what schedule write-back needs.

For large loads, API version 2026-07 and later adds ingest_items and backfill_items. You upload a CSV to a pre-signed URL and poll the job status. (bulk import)

Create a subscription with create_webhook(board_id, url, event, config). The events a scheduling integration needs:

• create_item and create_subitem for new orders and operations.
• change_column_value or change_specific_column_value for due date, quantity or priority changes.
• change_status_column_value for status changes made by people.
• item_archived, item_deleted and item_moved_to_specific_group for cancelled or completed orders.

The receiving URL must answer a challenge token when the webhook is created. Failed deliveries “retry once a minute for 30 minutes,” then stop. So the integration also runs a periodic reconciliation read with items_page and a filter on recently updated items. (webhooks)

In the other direction, SkyPlanner sends webhooks when state or the schedule changes. The integration service receives them and writes the new dates to monday.com, so write-back is event-driven.

1. Initial master data load. Read products, materials and open orders with items_page. Create workstations, shifts and constraints in SkyPlanner, or import them from Excel. Decide early whether operations live as subitems or on a linked board.

2. Order sync. Webhooks on the production board send new and changed items to SkyPlanner as orders. If you track purchase orders on a board, SkyPlanner treats ordered material as available on the delivery date and updates stock when the PO is marked Delivered.

3. Schedule write-back. For every order the engine placed or moved, the integration calls change_multiple_column_values. It sets the Timeline column to the planned start and finish and fills the workstation column. One call per item keeps the request count low.

4. Shop-floor progress. Operators log work with Mobile Confirmations, the Production Timer or Quick Log Mode. The timelogs keep the schedule current, and the matching Status label goes back to the board, so sales sees progress without asking.

5. Ownership and conflict rules. Write them down before go-live:

The main conflict source is people editing the Timeline column by hand. Agree that only SkyPlanner writes that column, or treat a manual edit as a request and let SkyPlanner reschedule. Autopilot reschedules automatically when production changes.

• Every account models orders differently. One board per customer, operations as items or subitems, machines as People or Status columns. Map column IDs per account, never by column title.
• Plan limits. Free, Basic and Standard allow 1,000 API calls per day, Pro 10,000 and Enterprise 25,000. Use webhooks for changes and batch write-back with change_multiple_column_values. (rate limits)
• Connected boards are capped. Basic allows one board connection and Standard five, which limits linked operation or product boards. (Connect Boards limits)
• Pin the API version. Versions move quarterly. Multi-level boards were excluded from the default boards query before version 2026-04.
• Cursor expiry. An items_page cursor lasts 60 minutes. Long reconciliation runs must restart cleanly.
• Webhook limits. The URL may be at most 255 characters, and retries stop after 30 minutes. The receiver must be idempotent.
• Units and durations. Numbers columns carry no unit. Agree whether a duration is minutes or hours before the first import.