Getting monday.com Salesforce integration right is one of the most requested things we help teams with – and one of the most commonly misunderstood. The setup looks simple on the surface. But the plan requirements, field mapping rules, and sync direction settings have real teeth. Get them wrong and you end up with boards full of duplicated records, broken automations, and a data mess that takes days to untangle.
This guide covers everything you need to know: what the native connector can actually do, the plan requirements upfront (not buried in a support doc), how to map fields without breaking things, and what to do if you’re not on monday.com Enterprise.
📋 What We’ll Cover
🎯 What the Integration Actually Does
At its core, the monday.com Salesforce integration lets you sync records between the two platforms without writing code. You pick a Salesforce object – a Lead, an Opportunity, a Contact – set some filter conditions, map fields to monday.com columns, and the data flows. Create a new Lead in Salesforce that matches your conditions, and a new item appears on your monday.com board. Update a field in monday.com, and it pushes back to Salesforce. That’s the dream, and it generally works.
The integration supports the following standard Salesforce objects out of the box: Leads, Contacts, Accounts, Opportunities, Cases, Campaigns, Orders, and Users. Custom Objects are also supported – though they use a polling mechanism and can take up to 3 minutes to sync rather than updating in near real-time like standard objects.
You can run the integration one-directionally (Salesforce to monday.com only) or enable two-way sync, where changes in either system propagate to the other. Most teams start with one-way and add bidirectional sync once they’re confident the field mapping is clean.
Standard Salesforce objects update in near real-time when records change. Custom Objects use polling and can take up to 3 minutes. Multiple rapid updates to the same record within a short window are batched into one API call – so you won’t burn through your action limit from a single bulk import.
⚠️ Plan Requirements You Need to Know First
This is where a lot of teams hit a wall. The native monday.com Salesforce integration is not available on all plans. To use it, you need:
- monday.com: Enterprise plan
- Salesforce: Enterprise or Unlimited edition
- Salesforce side: A user with “API Enabled” permission – typically your Salesforce System Administrator
If you’re on monday.com Pro or below, or if your Salesforce subscription is Essentials or Professional, the native integration is not available to you. That’s not a bug – it’s a hard platform restriction. The good news is there are solid alternatives (more on those in a moment).
Confirm your monday.com plan and Salesforce edition before spending time on setup. If you’re not on Enterprise on both sides, skip to the Make.com and Zapier section – those options work on lower-tier plans and are often simpler to manage anyway.
🔧 Setting Up the Native Connector
Assuming you’ve confirmed your plans, here’s how to actually set up the monday.com Salesforce integration from scratch.
Open the board and click Integrate
Go to the monday.com board where you want Salesforce records to appear. Click the Integrate button in the upper right corner. Search for “Salesforce” or click the Salesforce banner if it appears in the suggested integrations.
Enter your Salesforce subdomain
You’ll be asked for your Salesforce subdomain – the unique identifier in your Salesforce URL. Find it under the Account tab in the top-right corner of your Salesforce home page. Enter it in monday.com and click Connect.
Authenticate and grant access
Click Allow access to authorize the connection. The Salesforce user completing this step should have API access – otherwise the connection will fail with a permissions error.
Choose your Salesforce object
Select the object type you want to sync – Lead, Opportunity, Contact, Account, Case, or another supported object. Each board-object pair runs as its own integration template. You can have multiple templates per board, capped at 90 active templates per object type.
Set your filter conditions
Conditions control which Salesforce records pull into monday.com. You can add multiple conditions, but they are AND conditions. Important: conditions are only evaluated when an item is first created. Once a record pulls in, it continues syncing regardless of whether it still meets your conditions.
Map your fields
Match monday.com columns to Salesforce fields. Only fields of the same type can be mapped. Any Salesforce field marked as required for the object must be mapped – if a required field is left unmapped, the integration will not activate.
Set sync direction and activate
Choose one-way (Salesforce to monday.com) or two-way sync. Confirm everything looks right, then turn it on.
📊 Field Mapping Rules and What Won’t Sync
Field mapping is where most integrations quietly break. The UI looks forgiving – you can technically map almost anything – but the rules matter.
The most important restriction: only fields of the same type can be mapped to each other. A Salesforce phone field that doesn’t match monday.com’s phone column type will be mapped as plain text. But date vs. date-time mismatches cause real problems – if you map a Salesforce date-time field to a monday.com date column, you’ll lose the time portion and create discrepancies that are hard to notice until they cause a downstream issue.
If you need to sync data that lives in a formula or mirror column, create a dedicated text or number column, mirror the formula value into it using an automation, and map that plain column to Salesforce instead.
🔄 Two-Way Sync: How to Configure It Correctly
Two-way sync is powerful. It’s also where things can go sideways if you’re not deliberate about it.
When you enable two-way sync, changes in monday.com push to Salesforce, and changes in Salesforce pull into monday.com. A few behaviors catch people off guard.
First: conditions only apply at item creation. Once a Salesforce record lands on your board, the integration keeps it in sync permanently – even if the record later fails your original filter conditions.
Second: multiple integration templates on the same board pointing at the same Salesforce object multiply your API action consumption. High-volume Salesforce accounts can hit monday.com’s rate limits. Audit your active templates periodically and delete unused ones.
Third: deleting a synced item from monday.com does not stop the integration from running on that item. It continues counting against your action limit as a safeguard in case the item is restored. Pause integration templates before bulk-deleting synced items.
🔀 Alternatives for Non-Enterprise Teams
If you’re on monday.com Pro (or below) or Salesforce Professional, the native integration is off the table. But you still have good options.
Make.com (formerly Integromat)
Make.com is the most flexible middleware option and tends to be the most cost-effective for teams doing high-volume syncs. You build visual scenarios that trigger on events in either system and push data to the other. The learning curve is real – but the control you get is unmatched. If your sync has complex conditional logic or multi-step transformations, Make is worth the investment.
Zapier
Zapier is simpler to set up for straightforward trigger-action flows. “When a new Lead is created in Salesforce, create an item in monday.com” takes about 10 minutes. Where Zapier falls short is volume – its pricing scales with the number of tasks, which gets expensive quickly for accounts with heavy Salesforce activity.
🔥 Common Issues and How to Fix Them
We’ve helped a lot of teams debug monday.com Salesforce integrations. Here are the problems we see most often.
🚫 The integration activates but records aren’t coming through
Usually a field mapping issue. Go back to your integration setup and check whether all required Salesforce fields are mapped. Any required field left blank will silently block the integration from pulling records.
🚫 Date fields are showing up with wrong values
Date vs. date-time mismatches. If you’ve mapped a Salesforce date-time field to a monday.com date column, the conversion drops the time component and can shift the date by a day depending on time zone settings.
🚫 Records that should be filtered out are still appearing
Conditions are only evaluated at item creation. If a record matched your conditions when it first synced and later changed, it stays on the board and keeps syncing. This is by design.
🚫 We’re hitting the action limit unexpectedly
Multiple integration templates pointing at the same Salesforce object on the same board multiply your API consumption. A Salesforce account with high record-change volume can exhaust your monday.com action limit faster than expected.
🚫 Formula column data isn’t making it to Salesforce
Formula columns, mirror columns, and connected board columns cannot sync from monday.com to Salesforce. This is a platform limitation, not a config error.
