Eddie Blomkvist
Yes, monday.com can be connected to Salesforce. The integration turns a won opportunity in Salesforce into a project in monday.com with the customer, contacts and what was sold already in place, keeps accounts and contacts the same in both systems, and shows delivery status in Salesforce without the sales rep having to ask. It is built either with monday.com's own Salesforce integration or in an integration platform like Make, depending on which plan you have and what the flow should do. This article covers what the integration does, how it is built and what to decide before you get started.
- The opportunity is marked won in Salesforce
- Router · Does the customer exist in monday.com?YesThe project is linked to the existing customerNoThe customer is added to the customer board
- The project is created from the right template
The integration pulls account, contacts, products and amount from the opportunity. The project manager gets a ready-made project with the right template instead of an email from the sales rep.
- An account is changed in Salesforce
- The integration searches on the Salesforce ID in monday.com
- The customer record is updated
Address, account owner and contacts stay the same in both systems. Salesforce is the source of customer data, and monday.com gets the copy that delivery works from.
- The project status changes in monday.com
- The status is written to a field on the opportunity or account
- The sales rep sees delivery status in Salesforce
The sales rep does not need to log in to monday.com to know how delivery is going, and the account manager sees right away when the project is done.
- The project is marked delivered in monday.com
- Router · Is there an agreed continuation?YesThe renewal is created as an opportunity in SalesforceNoTask for the account manager to follow up
What delivery learns about the customer is not lost. New opportunities end up in Salesforce, where sales works.
The flows above are only examples of how it can work. Every integration is built around your process: which steps it should include, what should happen in each situation and who is responsible for what.
Short answer
There are two ways. monday.com has its own Salesforce integration in the Integrations Center that keeps boards synced with Salesforce objects, in one direction or both, but it requires monday.com's Enterprise plan. For companies on other plans, or when the integration should do more than mirror data, the flow is built in Make or Zapier. Either way, Salesforce must have API access, which is included in Enterprise Edition and up but is an add-on in Professional. Make is where we build most integrations, since the flow from deal to project almost always has conditions and multiple steps.
What the integration can do
Here are four common examples. Your integration can do more, less or something entirely different, depending on how you work.
When an opportunity is marked won in Salesforce, a project is created in monday.com. Customer, contacts, products and amount come along, and the project is created from the template that fits what was sold.
Accounts and contacts in Salesforce are mirrored to a customer board in monday.com, so delivery works from the same details as sales. The integration matches on the Salesforce ID, so the same customer never ends up there twice.
When a project changes status in monday.com, it is written to a field on the opportunity or account in Salesforce. Sales reps see delivery status where they already work.
When delivery is done, the integration can create a new opportunity or a task in Salesforce, so renewals and upsells are captured in the sales process instead of in someone's memory.
Why connect monday.com and Salesforce?
- Sales stays in Salesforce. Sales reps do not need to learn another system, and Salesforce remains the source for accounts, contacts and opportunities.
- Delivery gets the right details from the start. The project is created with customer, contacts and scope in place, without a handover meeting and without anyone copying things over.
- One customer register, not two. If the address or account owner changes in Salesforce, it carries through to monday.com.
- Leadership sees the whole chain. From deal to delivered project can be followed in one view, and the question of what has been sold but not delivered gets an answer.
How the integration is built
There are three options, and the right one depends on which plan you have and how advanced the flow is.
| Option | Best when | Keep in mind |
|---|---|---|
| monday.com's Salesforce integration | You have the Enterprise plan in monday.com and want to mirror accounts, opportunities or custom objects to boards, in one direction or both | Included in monday.com without an extra platform, but mirrors data rather than building processes. Requires the Enterprise plan in monday.com and API access in Salesforce |
| Make or Zapier | Flows with conditions and multiple steps, for example a project from a template on a won deal and status flowing back, regardless of monday.com plan | Zapier is enough for simple one-way flows. Make is the better fit when the flow has conditions, multiple steps or needs error handling and logging |
| Custom code against the Salesforce API | Large volumes, complex data models or a requirement that the logic live in Salesforce | Most flexible, but requires someone to own the code and keep up as objects and fields in Salesforce change |
Whichever option you choose, Salesforce needs API access and an integration user with the right permissions. API access is included in Enterprise, Unlimited, Performance and Developer Edition, can be purchased as an add-on in Professional Edition and is not available in Starter. What then determines whether the integration holds up is how it is built: how an opportunity maps to projects, groups and columns in monday.com, how customers are matched so there are no duplicates, how the flow handles exceptions like deals split into several projects, and what happens when something goes wrong. That is why we build with logging and alerts from the start.
What to decide before you build
An integration is never better than the process it automates. These questions determine whether it works in practice:
- Which system owns what? Salesforce should own accounts, contacts and opportunities; monday.com should own projects, tasks and delivery status. Decide this explicitly, or data gets overwritten in the wrong direction.
- What should trigger the project? The opportunity being marked won is the most common, but it can also be a signed contract or a specific stage in the sales process. Decide exactly which field and which value.
- How are customers matched? Store the Salesforce ID on the customer board in monday.com and match on it. A name is not enough, since the same company can be spelled several ways.
- Which details should come along, and in which direction? List the fields delivery needs and the fields sales wants to see flowing back. Leave everything else out.
- What happens when something goes wrong? A good flow logs every run and flags when a project could not be created, instead of silently skipping it.
Salesforce for sales, monday.com for delivery
For many companies, the question is not monday.com or Salesforce, but how they should live side by side. Salesforce is often chosen centrally, for the whole group or for a sales team that needs its depth, while delivery needs something project managers and consultants actually want to work in. Then Salesforce can be the CRM and monday work management can take care of projects, resources and follow-up, with the integration as the bridge. If sales is small and delivery is large, it is worth asking whether Salesforce is needed at all. We go through that in monday CRM vs Salesforce and in monday CRM or a separate sales system. Either way, the integration should be built so it can be replaced without delivery grinding to a halt.
Straviont builds the integration
We are an official monday.com partner and certified CRM specialists with monday.com, and we build integrations between monday.com and sales systems like Salesforce, in monday.com's own integration when the plan allows and in Make when the flow needs more. We start with the process: what should trigger the project, which system owns which details and who is responsible for what. Only then is the flow built, with logging and error handling, and we manage it as your business changes.
Frequently asked questions
Can monday.com be connected to Salesforce?
Yes. monday.com has its own Salesforce integration in the Integrations Center that requires the Enterprise plan, and on any plan the integration can be built in Make or Zapier or with custom code against the Salesforce API. The integration can create projects on won deals, sync accounts and contacts and send delivery status back.
Can a won opportunity in Salesforce create a project in monday.com automatically?
Yes. When the opportunity is marked won, the integration creates a project in monday.com from the template that fits what was sold, with customer, contacts, products and amount in place.
Does the integration work in both directions?
Yes. monday.com's own Salesforce integration can sync in one direction or both, and in Make you build flows in both directions, for example accounts from Salesforce to monday.com and delivery status back.
Does the integration require the Enterprise plan in monday.com?
Only if you want to use monday.com's own Salesforce integration. An integration in Make or Zapier works regardless of monday.com plan, but requires Salesforce to have API access.
Which Salesforce edition is needed?
API access is included in Enterprise, Unlimited, Performance and Developer Edition. In Professional Edition it is purchased as an add-on, and in Starter it is not available. The user the integration runs as also needs API permission.
Next steps
Start by describing the flow from won deal to delivered project: what triggers the project, which details delivery needs and what sales wants to see flowing back. From there, building it goes quickly. See also all integrations we build for monday.com. If you want help, you can book a free mapping session and we will go through it together.