Eddie Blomkvist
Yes, monday.com can be connected to Microsoft Outlook. With the integration, emails to a shared mailbox become tickets in monday.com, the reps' emails are logged on the right deal and contact in monday CRM without anyone copying them, and monday.com can send emails from your Outlook address when something happens on a board. Most of it is built into monday.com, and the rest is built in an integration platform like Make. This article covers what the integration does, what is built in, what needs Make and what to decide before you get started.
- An email arrives at a shared mailbox in Outlook
- Router · Is it from a known customer?YesThe ticket is linked to the customerNoThe ticket is created with the sender as a new contact
- The ticket lands on the service board with an owner
Emails to the info or support address become tickets with status and owner instead of unread rows in a mailbox several people share.
- The rep emails a contact from Outlook
- Emails & Activities matches the recipient to the contact in monday CRM
- The email and the reply are logged on the deal
The full email history with the customer sits on the deal, no matter who on the team wrote.
- The status changes to Ready for delivery in monday.com
- The email is built from a template with the customer's details
- The email is sent from your Outlook address
The customer is notified the minute the status changes, and nobody has to remember to write it.
- A date for the kickoff meeting is set on the project in monday.com
- The integration creates the meeting in the Outlook calendar
- The customer and project team get the invitation
Kickoff and check-in meetings are booked from the project plan instead of the project manager creating them by hand. This requires Make.
The flows above are only examples of how it can work. Every integration is built around your process: which steps to include, what should happen in each situation and who is responsible for what.
Short answer
There are two built-in parts. The Outlook integration in the monday.com Integrations Center creates items or updates from incoming emails and sends emails when something happens on a board. Emails & Activities in monday CRM syncs the reps' Outlook accounts in both directions, so emails are logged on the right contact and deal, with templates and open and click tracking. Together they cover most needs. When the email needs to be parsed, attachments handled, the calendar controlled or the flow needs conditions and several steps, it is built in Make or Zapier. Make is where we build most of those integrations.
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.
Emails to a shared mailbox in Outlook become tickets on a board in monday.com, with sender, subject and content in place. Replies in the same thread can be added as updates on the ticket instead of becoming new tickets.
With Emails & Activities in monday CRM, the reps' Outlook accounts are connected to monday.com. Emails to and from a contact are logged on the contact and the deal, and the rep can write from monday.com with templates and see whether the customer opened the email.
When a status changes, a date arrives or a ticket is created, monday.com sends an email from your Outlook address, built from a template with details from the item. Confirmations, welcome emails and reminders go out without anyone lifting a finger.
Meetings can be created in the Outlook calendar from dates in monday.com, and emails with attachments can be read and turned into tickets with the details filled in. This requires Make.
Why connect monday.com and Microsoft Outlook?
- No email is forgotten. Whatever arrives in the shared mailbox gets an owner and a status, and stays on the board until it is done.
- The full customer history in one place. The rep sees every email with the customer on the deal, including what a colleague wrote, without searching Outlook.
- The customer hears back on time. Confirmations and reminders go out when the status changes, not when someone remembers.
- Meetings follow the plan. Kickoffs and check-ins land in the calendar when the dates are set in the project, and move when the plan moves.
How the integration is built
There are three ways to build it, and which one fits depends on how advanced the flow is.
| Option | Best when | Keep in mind |
|---|---|---|
| monday.com's Outlook integration and Emails & Activities | Emails to a shared mailbox should become tickets, the reps' emails should be logged on deals and monday.com should send emails on status changes | Included in monday.com. Emails & Activities is available in monday CRM from the Standard plan. The recipe conditions are fixed, and attachments, parsing and the calendar are not handled |
| Make or Zapier | Flows with conditions and several steps, for example emails filtered by content, attachments that are saved, meetings created in the calendar or emails with custom logic | Zapier is enough for simple flows. Make fits when the flow has conditions, several steps or needs error handling. The connection is made to a Microsoft 365 account, and an administrator may need to approve the app in your Microsoft environment |
| Custom code against Microsoft Graph | Large volumes or requirements to process email and calendar in ways the platforms cannot handle | The most flexible, but requires someone to own and maintain the code and the app registration in Microsoft Entra |
For most companies, the built-in parts cover day-to-day needs, and Make is added for the calendar, attachments and filtering. What determines whether the integration holds up is the rules: which emails should become tickets and which should be left alone, how replies to an existing thread are recognized so they do not become new tickets, and how senders are matched to contacts so you avoid duplicates. That is why we start with a defined mailbox and clear rules, and build with logging so you can see what was created and why.
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 mailboxes should be connected? A shared mailbox for tickets, the reps' own accounts for deals, or both. Do not mix them up.
- What should become a ticket? Every email to the mailbox, or only those that meet a condition. Also decide what happens with auto-replies and newsletters.
- How is the sender matched? Email address against the contact list is the usual choice. Decide what happens when the address is unknown.
- Which emails should monday.com send, and from whom? List the emails, which address appears as the sender and who owns the template.
- What happens when something goes wrong? A good flow logs every run and flags when an email could not be turned into a ticket or sent, instead of silently skipping it.
Outlook for sales, Outlook for service
The integration does different things depending on which part of monday.com it sits in. In monday CRM, the point is that the rep's emails land on the right deal, and Emails & Activities handles that with a connection to each rep's Outlook account. In monday service, the point is that a shared mailbox becomes a ticket queue, and then it is the Outlook integration or Make that feeds the board. Many companies need both, and they should be built separately so a support email is not logged as sales activity. If you use Google Workspace instead, the same setup works with Gmail, which we describe in monday.com and Gmail.
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 Microsoft 365, using the built-in parts where they are enough and Make where the flow needs more. We start with the process: which mailboxes should be connected, what should become tickets and which emails monday.com should send. 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 Microsoft Outlook?
Yes. monday.com has its own Outlook integration in the Integrations Center and Emails & Activities in monday CRM for the reps' emails. Flows with conditions, the calendar or attachments are built in Make or Zapier, or with custom code against Microsoft Graph.
Can an email to our shared mailbox become a ticket in monday.com?
Yes. The Outlook integration creates a ticket on the board you choose when an email arrives at the connected mailbox, with sender, subject and content. Replies can be added as updates on the ticket.
Can the reps' emails be logged on the right deal?
Yes. Emails & Activities in monday CRM connects each rep's Outlook account to monday.com and logs emails to and from contacts on the contact and the deal. The rep can also write from monday.com with templates and see whether the customer opened the email.
Can monday.com send emails automatically from Outlook?
Yes. The built-in integration sends emails from your Outlook address when a status changes, a date arrives or a ticket is created, built from a template with details from the item.
Can meetings in the Outlook calendar be created from monday.com?
Yes, through Make. When a date is set or changed on a project, the integration can create or move the meeting in the Outlook calendar and invite the attendees.
What do we need in Microsoft 365 to connect the systems?
A Microsoft 365 account with access to the mailboxes being connected. An administrator may need to approve monday.com and Make to read and send email.
Next steps
Start by describing which emails come in and go out today: to which mailboxes, what should happen to them and who is responsible. From there, setting it up goes quickly. See also all integrations we build with monday.com. If you want help, you can book a free mapping session and we will go through it together.