How to Integrate Monday.com with Your Headless CMS

What is Monday.com?

Monday.com is a work management platform for planning projects, tracking tasks, assigning owners, and visualizing work across boards, timelines, calendars, and dashboards. Teams use it to coordinate content calendars, launches, campaigns, product work, and customer-facing operations. Its core capability is turning work into structured board items with statuses, people, dates, automations, and API access through Monday.com's GraphQL API.

Why integrate Monday.com with a headless CMS?

Content work usually doesn't stop at publish. A product page update may need legal review, a campaign launch may need design assets, and a support article change may need customer-facing teams to know what changed. If Monday.com is where your team coordinates work, connecting it to your headless CMS keeps those follow-up tasks tied to the content event that created them.

Architecture overview

A typical Sanity and Monday.com integration starts when an editor publishes or updates a document in Sanity Studio. A Sanity webhook fires on the matching mutation, usually filtered by document type and publish state. The webhook sends the document ID to a Sanity Function or webhook listener. That server-side code uses @sanity/client and a GROQ query to fetch the exact fields Monday.com needs, such as title, slug, publish date, locale, owner, campaign, and review status. The handler then calls Monday.com's GraphQL API through monday-sdk-js, usually with create_item for new board items or change_multiple_column_values for updates. Monday.com turns that payload into a board item with mapped columns like Status, Date, People, Link, and Long Text. The end user sees the result inside the Monday.com board they already use for planning, without copying content data by hand.

Common use cases

Step-by-step integration

1. 1

   Set up Monday.com API access

   Create or open a Monday.com account, choose the workspace and board you want to sync into, then generate an API token from your Monday.com developer settings. Note the board ID and the column IDs for fields like status, date, owner, link, and long text. Install the SDK with npm install monday-sdk-js.

2. 2

   Model the content in Sanity Studio

   Add fields that match how your team works in Monday.com. For an article, that might include title, slug, publishDate, owner, campaign, locale, workflowStatus, and mondayItemId. Keeping mondayItemId on the Sanity document lets your sync update an existing Monday.com item instead of creating duplicates.

3. 3

   Create a publish-triggered sync

   Use a Sanity webhook filtered to the document types you want to send, such as article, landingPage, or helpArticle. Point the webhook at a Sanity Function, an API route, or a small middleware service. Send the document ID in the payload, then fetch the full document with GROQ.

4. 4

   Map Sanity fields to Monday.com columns

   Use Monday.com's GraphQL API with create_item for first-time syncs and change_multiple_column_values for updates. Column values must be sent as a JSON string, and each key must match a real Monday.com column ID, not the visible column name.

5. 5

   Test with real publish events

   Publish one test document, confirm that the Monday.com item is created with the right status, date, owner, and content link, then update the document and confirm it doesn't create a duplicate. Also test missing optional fields, unpublished drafts, and API rate limit behavior.

6. 6

   Build the team experience

   Add the Monday.com item URL back into Sanity Studio if editors need a direct link from content to work tracking. On the frontend, keep rendering from Sanity's Content Lake, while Monday.com handles planning, assignments, and collaboration.

Code example

Minimal Express webhook handler that receives a Sanity webhook, fetches the published document with GROQ, and creates a Monday.com board item.

import express from 'express';
import mondaySdk from 'monday-sdk-js';
import {createClient} from '@sanity/client';

const app = express();
app.use(express.json());

const sanity = createClient({
  projectId: process.env.SANITY_PROJECT_ID!,
  dataset: process.env.SANITY_DATASET!,
  apiVersion: '2025-01-01',
  token: process.env.SANITY_TOKEN!,
  useCdn: false
});

const monday = mondaySdk();
monday.setToken(process.env.MONDAY_API_TOKEN!);

app.post('/api/sanity-to-monday', async (req, res) => {
  const id = req.body._id || req.body.ids?.created?.[0] || req.body.ids?.updated?.[0];
  if (!id) return res.status(400).send('Missing document id');

  const doc = await sanity.fetch(`*[_id == $id][0]{
    title,
    "url": "https://www.example.com/" + slug.current,
    publishDate,
    workflowStatus,
    locale
  }`, {id});

  if (!doc) return res.status(404).send('Document not found');

  const columnValues = JSON.stringify({
    status: {label: doc.workflowStatus || 'Published'},
    date4: {date: doc.publishDate?.slice(0, 10)},
    link: {url: doc.url, text: doc.title},
    text: doc.locale || 'en-US'
  });

  await monday.api(`mutation ($boardId: ID!, $name: String!, $values: JSON!) {
    create_item(board_id: $boardId, item_name: $name, column_values: $values) { id }
  }`, {
    variables: {
      boardId: process.env.MONDAY_BOARD_ID!,
      name: doc.title,
      values: columnValues
    }
  });

  res.status(200).json({ok: true});
});

app.listen(3000);

How Sanity + Monday.com works

CMS approaches to Monday.com

Keep building

Explore related integrations to complete your content stack.