Monday.com

Webflow forms can store submissions in Site settings, email them to your team, or route them through webhooks, connected apps, and custom actions. Without one of those routes, nothing assigns the lead, tracks its status, or hands it to the right person. On the content side, editorial approvals live in monday.com boards while publishing happens in the Webflow CMS. Someone copies data between the two systems by hand.

Connecting the two closes that loop. Form and editorial data can move automatically between monday.com boards and Webflow CMS collections. Public board views and WorkForms can also appear on Webflow pages as iframes.

Marketing ops teams use the integration to capture inbound leads in monday CRM. Content and recruiting teams push approved posts, open roles, and listings from boards into CMS collections. Agencies embed project boards on client portal pages so clients see status without a monday.com seat.

How to integrate monday.com with Webflow

What is monday.com? monday.com is a work management platform built around boards, items, groups, and columns. Teams layer automations, dashboards, workdocs, and WorkForms on top of those boards, and the same core runs monday CRM, monday dev, and monday service. A GraphQL API and board webhooks expose every item and column change to outside systems.

Teams pair the two tools when they track work in monday.com while the public output lives on a Webflow site. Recruiting and editorial boards feed public pages, while contact forms feed CRM pipelines. No monday.com app exists in the Webflow Marketplace, and Webflow is absent from monday.com's native integration blocks, which cover Slack, Gmail, Outlook, Microsoft Teams, and Salesforce. Every path below runs through an embed, an automation platform, or both APIs.

The monday.com-Webflow integration supports 3 approaches:

• Code Embed elements place monday.com WorkForms and public board views on a Webflow page without writing code.
• Zapier, Make, and other automation platforms connect Webflow form submissions, orders, and CMS items to monday.com boards.
• The Webflow Data API and monday.com APIs give you full control over two-way sync, but require server-side development.

Most implementations combine two or more of these methods depending on the complexity of the setup.

Embed monday.com WorkForms and board views with Code Embed elements

A Code Embed element renders any iframe monday.com generates, so a WorkForm or a public board view appears inside your Webflow layout. Use this method when you want a monday.com form on a landing page or a live project board on a client portal where field mapping is unnecessary. You need a Core, Growth, Agency, or Freelancer Workspace or an active Site plan, and each element holds up to 50,000 characters. Code inside the element renders on the published site. The canvas does not render it.

Embed a WorkForm

WorkForms write each submission into a board as a new item, and anyone with the embed can submit without a monday.com account. Basic embedding carries no plan restriction in the WorkForms settings docs. Hiding monday.com branding needs Pro or Enterprise, and password protection needs Enterprise.

To embed a WorkForm:

1. In monday.com, click the blue + icon in the left panel and choose Form.
2. Build the form, then click Share form in the top right and pick the option to embed in a webpage.
3. Copy the iframe HTML.
4. In Webflow, open the Add panel, drag a Code Embed element onto the page, and paste the code.
5. Save and publish the site.

If the iframe leaves whitespace below the form, change its height attribute in the embed code, or target the iframe with a CSS rule in your site's custom code settings.

Embed a public board view

A shared board view shows a live, read-only slice of a board to anyone with the link. Only board owners can share a view. Mirrored items, hidden columns, and restricted-view columns do not appear. Boards with Item Viewing permissions cannot be shared publicly at all.

To embed a board view:

1. Open the board, click the three-dot menu to the right of the view name, and choose Share.
2. Select Embed Code and click Copy.
3. For a full-screen embed, insert /embed/ after view.monday.com/ in the URL.
4. Paste the iframe into a Code Embed element in Webflow and publish.

Enterprise accounts with the HIPAA feature turned on cannot share boards or views, so this path is closed to them. Embeds display data. Automation platforms move it.

Connect with Zapier, Make, n8n, or other automation platforms

A form submission or CMS event can create or update a board item through the Webflow and monday.com connectors that Zapier, Make, and n8n each offer. This path gives marketing and content teams field mapping through a hosted connector. Zapier's Webflow and monday.com page lists the full trigger and action catalog.

To set up a Zap:

1. Publish the Webflow form and send one test submission through it.
2. In Zapier, pick Webflow as the trigger app, choose the New Form Submission trigger, and select your Site and Form.
3. Add a monday.com Create Item action. Authorize with a personal API token from your profile picture > Developers.
4. Choose the Board ID and Group ID, then map form fields to Item Name and the board columns.
5. Test the Zap and turn it on.

Common pairings across these platforms:

• Webflow New Form Submission → monday.com Create Item (Zapier)
• Webflow New Order or Updated Order → monday.com Create Item or Update Item
• Webflow New Comment → monday.com Create Item (a Make scenario carries the comment, its author, its location, and a direct link into the task)
• Webflow Collection Item Created, Changed, or Deleted → monday.com Create Item or Change a column value (through a Webflow webhook; Zapier lists no collection item triggers for this pairing)
• monday.com New Item in Board → Webflow Create Live Item
• monday.com Specific Columns Values Changed in Board → Webflow Update Live Item

Zapier publishes pre-built templates for this pairing, including one that turns form submissions into items and one that creates live CMS items from new board items. A third updates live items when specific column values change. Zapier cannot map Webflow reference or multi-reference CMS fields, per its Webflow guide, so keep those relationships in the CMS or handle them through the API. In Make, the Webflow Watch Events webhook module pairs with the monday.com Create an Item and Update Column Values of a Specific Item modules; Make retired its v1 modules for monday.com on May 1, 2026, so rebuild older scenarios on v2. The n8n monday.com node needs a current n8n release. IFTTT Applets run one trigger to one action; the Webflow service offers Form submitted, New order, and New collection item as triggers and Create live collection item as an action, while the monday service offers New item in board as a trigger and Create an item and Post an update on an item as actions, which limits it to single-step workflows.

Build with the Webflow and monday.com APIs

A server-side endpoint receives webhooks, holds tokens, and controls field mapping, deduplication, error handling, and both sync directions. Webflow Cloud, Cloudflare Workers, and Vercel Functions are hosting options; Starter and Basic site plans cannot mount a Webflow Cloud app on a custom domain. Keep monday.com API calls out of Code Embed elements and page custom code. Those slots run only HTML, CSS, and browser JavaScript, so any personal API token placed there is public, and monday.com's auth guidance advises against global API tokens for most apps because they are unscoped and can do everything. The Webflow v1 API was deprecated on March 31, 2025, so build against Data API v2 only.

• monday.com GraphQL API handles boards, items, column values, and board webhooks through one endpoint at https://api.monday.com/v2
• Webflow's Data API handles CMS collections and form submissions
• Webflow webhooks trigger real-time events between systems

Authenticate to monday.com with the header Authorization: YOUR_API_KEY_HERE and pin a release with API-Version: {version}. Webflow requests take Authorization: Bearer <token>. Generate a Webflow site token under Site settings > Apps & integrations > API access > Generate API token; each site allows up to 5 tokens, and a token expires after 365 consecutive days of inactivity. The monday.com token is the same personal token you generated for Zapier.

Create monday.com items from Webflow form submissions

This flow replaces a Zap when you need dedupe logic, routing to several boards, or column types Zapier handles poorly. A form_submission webhook fires, your endpoint verifies the signature, then calls the create_item mutation.

To implement this:

1. Register the webhook with POST https://api.webflow.com/v2/sites/{site_id}/webhooks and triggerType: "form_submission". Registration needs the sites:write scope and delivery needs forms:read. You can also add it under Site settings > Apps & integrations > Webhooks > Add webhook. Use the filter parameter to target one form by name.
2. Verify each delivery. Concatenate x-webflow-timestamp + : + the raw request body, compute a SHA-256 HMAC with your signing secret, and compare it to x-webflow-signature. Reject timestamps older than 300,000 ms.
3. Read payload.data, which holds the submitted fields as key/value pairs, along with payload.formId, payload.name, and payload.submittedAt.
4. Build column_values as a JSON string (JSON.stringify() in JavaScript) and POST the mutation to https://api.monday.com/v2:

mutation {
  create_item(
    board_id: 1234567890
    group_id: "group_one"
    item_name: "new item"
    column_values: "{\"email9\":{\"email\":\"zaphod@heartofgold.ai\",\"text\":\"zaphod@heartofgold.ai\"},\"phone\":{\"phone\":\"+15550000000\",\"countryShortName\":\"US\"},\"text\":\"Zaphod Beeblebrox\"}"
  ) { id }
}

5. Return HTTP 200. A failed delivery retries up to 3 more times at 10-minute intervals.

Email columns take {"email": "...", "text": "..."}, phone columns take {"phone": "...", "countryShortName": "US"}, and date columns take {"date": "YYYY-MM-DD", "time": "HH:MM:SS"}. The full set of formats lives in the column values guide. Keep card numbers out of the form entirely, because every field you map lands in a monday.com board.

Publish monday.com board items to the Webflow CMS

A board webhook fires when someone creates an item, your endpoint fetches whatever the payload omits, then writes a live CMS item. Register the webhook with the create_webhook mutation (scope webhooks:write), or from the board via Automations Center > Integrations, search "webhooks", and paste your URL. Either way the target URL must stay under 255 characters.

To implement this:

1. Run the mutation:

mutation {
  create_webhook(
    board_id: 1234567890
    url: "https://your-endpoint.com/webhook"
    event: create_item
  ) { id board_id }
}

2. Answer the verification handshake. monday.com posts {"challenge": "<token>"} to the URL, and the endpoint must return that same token in a challenge field, or the webhook is never created.
3. Parse the event. The payload arrives as { "event": { … } } with event.pulseId, event.pulseName, and event.boardId. The event.type value is create_pulse, while the subscription event is create_item. event.columnValues may be empty, so query items_page with the pulseId when you need column data.
4. Fetch the collection's field slugs with GET /v2/collections/{collection_id} (scope cms:read).
5. Create the item live with POST /v2/collections/{collection_id}/items/live and a fieldData object (scope cms:write). For a review step instead, POST /v2/collections/{collection_id}/items with "isDraft": false, then POST /v2/collections/{collection_id}/items/publish with {"itemIds": ["item_id"]}.

Write the monday.com pulseId into a text field on the CMS item so later runs update instead of duplicating. Staged items stay invisible until published, and the bulk staged-update endpoint caps at 100 items per request. The monday.com webhook reference says failed deliveries retry once per minute for 30 minutes. The error-handling page says requests through the webhook integration will not be retried. Given the conflicting guidance, build the endpoint to be idempotent.

Sync status changes to live CMS items

When an editor moves an item to Done on an editorial board, this webhook updates the matching CMS item or flips a published switch field. It depends on the pulseId mapping stored in the previous method.

To implement this:

1. Subscribe to status changes with a config filter:

mutation {
  create_webhook(
    board_id: 1234567890
    url: "https://your-endpoint.com/webhook"
    event: change_status_column_value
    config: "{\"columnId\":\"status\", \"columnValue\":{\"$any$\":true}}"
  ) { id board_id }
}

2. Read event.columnId and event.value.label.index. Branch on index because admins can rename label.text, while the index stays stable.
3. Look up the CMS item_id for event.pulseId, then PATCH /v2/collections/{collection_id}/items/{item_id}/live with the changed fieldData.

For the reverse direction, register a Webflow collection_item_published webhook and call change_column_value to mark the board item Published. Checkbox, timeline, and connect boards columns require change_multiple_column_values; change_simple_column_value does not support them. Other Webflow trigger types worth wiring include collection_item_created, collection_item_changed, collection_item_deleted, site_publish, ecomm_new_order, and ecomm_order_changed, with a limit of 75 registrations per trigger type per site.

What you can build with the monday.com Webflow integration

• Lead and booking intake into monday CRM: The Hotel Savoy site in the Made in Webflow showcase uses a custom monday.com integration so the hotel team tracks inquiries and bookings from form submissions. A native monday.com automation can assign the resulting CRM item to a rep.
• Careers page fed by a recruiting board: The job board pattern adds an external ID field so repeated runs stay safe and a validThrough date so a daily scenario expires filled roles. A Collection List on the careers page renders each open role.
• Editorial calendar that publishes itself: The status-sync workflow above can publish approved board items and report each published Webflow item back to the board with a Published status and date.
• Client portal with a live project board: A public board view embedded through a Code Embed element gives each client a real-time status page without a monday.com seat. Webflow User Accounts were sunset on January 29, 2026, so gate the page with Clerk on Webflow Cloud when clients need role-based access.

If you need more control over deduplicating repeat submissions or syncing reference fields between boards and collections, the API integration path covers those cases with full flexibility.