Salesforce monday.com Integration: Options, Setup and Limits (2026 Guide)

What a Salesforce monday.com integration is for

The pattern is almost always the same. Salesforce is where sales tracks leads, accounts and opportunities. monday.com is where onboarding, delivery, marketing or ops teams plan the work. The two drift apart unless something connects them.

The jobs people actually want done:

• Closed-won to project. When an opportunity closes, an item (or a whole project) appears on the delivery board with the account, amount, products and owner filled in.
• Status back to sales. The account manager sees in Salesforce that onboarding is “In progress” or “Blocked” without asking.
• Account changes downstream. A new billing contact or renewal date in Salesforce updates the matching item, so delivery doesn’t work from stale data.
• Requests into Salesforce. A lead or partner request captured on a monday.com form becomes a lead or case in Salesforce.

It should not be a full mirror. Salesforce stays the system of record for customers and deals; monday.com stays the system of record for tasks, timelines and workload. Sync only the fields one side needs from the other. For the wider picture of patterns and tools, see our Salesforce integration guide.

monday.com’s native Salesforce integration

monday.com builds the integration itself and sells it as a paid add-on. According to monday.com’s help center, as of October 2026:

• monday.com plan: Enterprise. Pricing for the add-on comes from your account owner or monday.com support, not a public price list.
• Salesforce edition: Enterprise or Unlimited. monday.com states that Essentials and Professional are not supported.
• Salesforce package: a Salesforce admin installs monday.com’s package in the org. The person who installs it and the people who later connect boards need the “API Enabled” permission.
• Environments: production and sandbox orgs are both supported.

Inside monday.com you will find it under the Integrate button on a board. There are two ways to use it.

Recipe templates (the original integration)

Recipes are sentences you fill in, such as “When an object meets these conditions, create an item and sync all future changes from Salesforce.” Each recipe moves data one way. For two-way sync you add a second recipe that creates or updates a Salesforce object when a board item changes.

The details that catch people out, from monday.com’s own documentation:

• Conditions are checked once, when the item is created. After that, the item keeps syncing every change even if the record no longer matches.
• Conditions are AND only. You can’t build “stage is X or Y” in one recipe.
• Required Salesforce fields must be mapped in the push recipe. If one is left blank, the sync fails without an error message.
• Supported standard objects are Campaign, Account, Case, Lead, Opportunity, Contact, Orders and Users, plus custom objects and custom fields.
• A cap per object type: fewer than 90 pulling recipes per Salesforce object type. At the limit, monday.com refuses new recipes until you delete unused ones.

The Salesforce 2-way sync app (the newer option)

The 2-way sync app sets up the whole connection in one screen. You pick a Salesforce object (monday.com lists all non-deprecated standard and custom objects), choose one-way or two-way, map fields and, for two-way, set the direction field by field. Separate incoming and outgoing conditions, with AND and OR groups, decide which records cross in each direction.

It also maps the Salesforce record owner to a monday.com People column when the email addresses match. Sync errors show in Run History with Salesforce’s own error message, and sandboxes are supported. Teams on the old recipes get a prompt to switch, and can reconnect items that are already synced.

The 2026 package change and polling

In 2026 monday.com moved the integration to a new Salesforce package that, in monday.com’s words, aligns with Salesforce’s official partner and security requirements. It recommended migrating by July 31, 2026, and warns that connections left on the previous package stop working once Salesforce retires it. Migration has two steps: a Salesforce admin installs the new package and allows users, then each integration owner reconnects in monday.com.

The bigger change for design: the new package polls Salesforce every 3 minutes instead of using Apex-based webhook simulation. Each poll uses Salesforce API calls, and several edits to one record inside a window are combined. Treat the sync as near real time, and plan your Salesforce API budget accordingly.

What it doesn’t do

• No subitems. Mapping to or from subitems is not supported, so line items or task lists under an item stay in monday.com.
• No deletions. By design, deleting a record or item on one side doesn’t delete it on the other.
• Lookups one way. Salesforce lookup fields come into monday.com as text; changes to them in monday.com don’t go back.
• No type conversion. Fields map only to compatible types. Mixing a date field with a date-time field causes drift.
• Calculated columns stay home. Formula, connect boards and mirror columns don’t sync to Salesforce. Salesforce formula fields arrive in monday.com as read-only text.
• No import. There is no bulk import of existing records; monday.com suggests triggering the sync through an automation on a field.
• No app inside Salesforce. The package is the connector’s back end. monday.com’s help center doesn’t describe an app that shows boards on Salesforce pages, so sales sees project data only as synced fields.

Integration actions and limits

Every integration run on monday.com consumes actions from a monthly quota.

According to monday.com’s pricing help articles, as of October 2026 the integration quotas are 250 actions a month on Standard, 25,000 on Pro and 250,000 on Enterprise, with a separate quota of the same size for automations. Because the native Salesforce integration is Enterprise-only, 250,000 is the number that applies to it.

Three things eat that quota faster than expected:

• Duplicate recipes. monday.com recommends one Salesforce integration per board and object type; several on the same object compete and multiply action and API use.
• Deleted items. The integration keeps running on synced items after they are deleted (so a restored item stays current), and those runs count.
• Mixed workflows. Custom workflows that combine automation and integration blocks count against the automation quota, not the integration one.

On top of monthly quotas, monday.com warns that duplicate integrations make it easier to hit rate limits, and Salesforce applies its own API limits to the polling. Admins or billing contacts get email alerts as the quota fills up; you can check usage in the Usage tab of the Autopilot hub or under Administration, Usage stats.

Your options compared

monday.com also offers Salesforce blocks in its workflow builder (create object, update object, get object data), listed for Pro and Enterprise. As of October 2026 they were in beta and rolling out gradually, and they don’t support lookup fields. They suit one-off steps inside a bigger monday.com workflow rather than a record sync.

Which option fits you?

Start with your monday.com plan, because the native app is Enterprise-only. The other three questions cover what a closed deal should trigger, how fast changes must show up and who owns the sync.

How the data flows

The design that holds up: Salesforce owns the customer and the deal, monday.com owns the work. Deal data flows to the board once the deal is won; a handful of status fields flow back so sales can see progress.

Field mapping: what goes where

Start with this minimum set for the closed-won handoff. Add a field only when someone can name the decision they will make with it.

Two rules prevent most trouble. First, give every field one direction, even in the 2-way app: two-way on the same field invites overwrites every polling cycle. Second, write back to dedicated custom fields on the opportunity or account, never to Stage, Amount or Owner, so delivery can’t change the sales pipeline by accident.

How to set it up, step by step

Budget time for the board as well as Salesforce: column types have to match field types before the 2-way sync app can map them. monday.com’s help center shows the current screens for each step.

1. Agree on the handoffWhich Salesforce event starts the work (usually Closed Won on certain record types) and which board receives it. Then which fields delivery needs, and which two or three fields sales wants back. This is your mapping.
2. Check plans and buy the add-onConfirm monday.com Enterprise and Salesforce Enterprise or Unlimited, and ask monday.com for the Salesforce add-on. If either is missing, go to the iPaaS or API routes below.
3. Prepare a Salesforce sandboxCreate the custom fields that will receive monday.com data (Project Status, Go-Live Date). Note every field that is required on the object; it must be mapped.
4. Install the package in the sandboxA Salesforce admin installs monday.com’s current package from the link in monday.com’s help center (sandbox installs use test.salesforce.com) and allows the users who will connect. Use the updated package; the previous one is being retired.
5. Pick the connecting userThe sync runs on behalf of whoever connects, and it breaks if that account is removed. Use a dedicated integration account with API Enabled and access only to the objects and fields you map, so every synced change shows that account as its author.
6. Build the boardCreate columns that match Salesforce field types: Status columns whose labels equal the picklist values, Date columns for date fields, People for owners. Convert formula or mirror columns you want to send into plain columns.
7. Connect and mapOn the board, open Integrate, search for Salesforce, open the 2-way sync app, enter your subdomain and sign in. Choose the object, the sync scope, then map fields and set each field’s direction.
8. Set incoming and outgoing conditionsIncoming: only opportunities with Stage Closed Won (and the right record type). Outgoing: only items that have a Salesforce ID, so test items never create records.
9. Test real scenariosA new closed-won deal, a deal reopened and closed again, and a picklist value missing on the board. Then a renamed account, an owner without a monday.com account, and a status change on the board. Wait out the 3-minute cycle and check Run History.
10. Go live and watch usageRepeat the setup against production, brief both teams on what syncs where, and check action usage and Run History weekly for the first month.

Built by Gilzor

Results we’ve shipped

70+products launched

98%delivered on time

85%clients come back

Aviation33%faster baggage weigh-inWeb and Mobile application for Airlines→Healthcare+30%lab test ordersMedical Lab Web and Native Mobile Applications→Retail · Startup700+stores aggregatedMobile application for Grocery shops→

Talk to the people who build it. Tell us about your project and get a free estimate of scope, timeline and cost.

See how we’d approach yours →

Pitfalls and how to fix them

iPaaS and custom integration via the monday.com API

An iPaaS makes sense when you are not on monday.com Enterprise, or when one Salesforce event should do several things. For example: create an item from a template, add subitems per product, post to Slack, and write the item link back to the opportunity.

Zapier, Make and Workato all have monday.com and Salesforce connectors; Unito sells two-way sync of monday.com items with Salesforce records. Check each vendor’s current plan limits against your volume. If your project team uses Asana rather than monday.com, our Asana Salesforce integration guide covers that pair.

A custom integration pays off when you need subitems for opportunity line items, rollups from several boards back to one account, sub-minute reaction times, or rules you can audit. It usually means a small middleware service:

• monday.com side: the GraphQL API for creating and updating items. Webhooks fire on events such as item created, column value changed or subitem created. monday.com verifies a webhook URL with a challenge request and retries failed deliveries once a minute for 30 minutes.
• Salesforce side: Platform Events or Change Data Capture to react to closed-won deals, the REST API to write status back, and a dedicated integration user.
• In between: a link table of opportunity IDs and item IDs, idempotent writes so retries don’t duplicate items, a queue for rate limits, and alerts.

Plan for monday.com’s API limits. According to monday.com’s developer documentation, as of October 2026 accounts have a daily call limit (25,000 on Enterprise, 10,000 on Pro). There is also a per-minute request limit and a complexity budget per minute, so bulk backfills must be paced. The Salesforce API integration guide covers the Salesforce half in more depth.

The ranges are from our API integration cost guide, where you can see what makes a build cheaper or more expensive. Compare them with the add-on price and the extra plan cost if you would upgrade to Enterprise only for the integration.

Go-live checklist

Score your setup before you repeat it against production. Gaps in field ownership or conditions are cheaper to fix in the sandbox than after delivery starts working from it.

FAQ

Where Gilzor fits

The right monday.com route depends on your plan: the native app needs Enterprise and the add-on, while iPaaS and API builds work without them. Gilzor, a software development company in Poland and Cyprus, builds and maintains Salesforce integrations.

We can map the handoff with your sales and delivery leads, configure monday.com’s integration or an iPaaS flow, or build a custom integration on the monday.com and Salesforce APIs, and support it after launch. For how we scope it, see Salesforce integration services.