Eddie Blomkvist
Yes, monday.com can be connected to Gmail. With the integration, emails sent to a shared inbox 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 when something happens on a board, for example an order confirmation when the status changes. 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 address in Gmail
- 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 an inbox several people share.
- The rep emails a contact from Gmail
- 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 Delivered in monday.com
- The email is built from a template with the customer's details
- The email is sent from your Gmail address
The customer is notified the minute the delivery is complete, and nobody has to remember to write it.
- An email with a PDF quote or order arrives
- The integration reads the attachment and extracts the details
- The ticket is created with the details filled in and the PDF attached
Orders that arrive as attachments do not have to be retyped by hand. This requires Make, often together with a parsing step.
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 Gmail 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' Gmail 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 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 Gmail address 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' Gmail 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 Gmail address, built from a template with details from the item. Order confirmations, welcome emails and reminders go out without anyone lifting a finger.
Emails with orders, quotes or form responses as attachments can be read and turned into tickets with the details filled in. This requires Make, often with a parsing step in between.
Why connect monday.com and Gmail?
- No email is forgotten. Whatever arrives in the shared inbox 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 the inbox.
- The customer hears back on time. Confirmations and reminders go out when the status changes, not when someone remembers.
- Less retyping. Orders and requests that arrive by email do not have to be keyed in by hand.
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 Gmail integration and Emails & Activities | Emails to a shared address 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 and parsing are not handled |
| Make or Zapier | Flows with conditions and several steps, for example emails filtered by content, attachments that are saved and parsed, or emails sent with custom logic | Zapier is enough for simple flows. Make fits when the flow has conditions, several steps or needs error handling. Personal gmail.com accounts often need their own OAuth client with Google to connect to Make, while Google Workspace accounts connect directly |
| Custom code against the Gmail API | Large volumes or requirements to process email in ways the platforms cannot handle | The most flexible, but requires someone to own and maintain the code, plus Google's security review of the app |
For most companies, the built-in parts cover day-to-day needs, and Make is added for whatever needs to be parsed or filtered. 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 address 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 addresses should be connected? A shared address for tickets, the reps' own accounts for deals, or both. Do not mix them up.
- What should become a ticket? Every email to the address, 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, who 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.
Email for sales, email 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 Gmail account. In monday service, the point is that a shared address becomes a ticket queue, and then it is the Gmail 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 Microsoft 365 instead, the same setup works with Outlook, which we describe in monday.com and Microsoft Outlook.
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 email, using the built-in parts where they are enough and Make where the flow needs more. We start with the process: which addresses 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 Gmail?
Yes. monday.com has its own Gmail integration in the Integrations Center and Emails & Activities in monday CRM for the reps' emails. Flows with conditions, parsing or attachments are built in Make or Zapier, or with custom code against the Gmail API.
Can an email to our shared address become a ticket in monday.com?
Yes. The Gmail integration creates a ticket on the board you choose when an email arrives at the connected address, 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 Gmail 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 Gmail?
Yes. The built-in integration sends emails from your Gmail address when a status changes, a date arrives or a ticket is created, built from a template with details from the item.
Does it work with personal gmail.com accounts?
With monday.com's own integration, yes. With Make, personal gmail.com accounts often require you to create your own OAuth client with Google, while Google Workspace accounts connect directly. For a company, Google Workspace is the sensible starting point.
Next steps
Start by describing which emails come in and go out today: to which addresses, 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.