How to sync Gmail into your CRM without manual logging

The short answer. To get Gmail into your CRM without manual logging, connect each person's Gmail and Google Calendar once, let every thread land on the people, companies and deals it's about, set per-person sharing rules before anything is shared, and let an agent turn new email into field updates and follow-up drafts a rep approves. Day AI does this for teams in place of their CRM, or on top of Salesforce or HubSpot: each person connects Google once and chooses what to share, and nobody BCCs, forwards or logs an email again.

Say you run customer success at a developer-platform company, and your renewals live in Salesforce. It's 2:15 on a Tuesday, and a renewal call has just ended. You connected Google to Day AI once, so the call and the Gmail thread behind it are already in one place, and you don't open Salesforce or log either one. About 30 minutes after the call ends, Day AI has the follow-up waiting for you, written in your own voice, ready to read and send. It has also proposed the Salesforce updates the conversation supports: the MEDDPICC fields that moved, and the people from the call attached to the renewal opportunity, alongside the Gmail thread. The proposal reaches you in Slack, and you approve it there in a few seconds. Salesforce now shows the right people on the opportunity and the MEDDPICC fields as they stand today, and nobody logged anything. Your Tuesday afternoon went to the customer, and the record kept up anyway.

Where the usual answer goes wrong. Most guides to this question say to connect your inbox to the CRM, log email from known contacts, and keep a BCC address as the fallback. That gets a copy of each email onto a timeline, and stops there: the close date, the new stakeholder and the follow-up the thread called for still wait for someone to type them. The conversations are the record, and agents should do the work they imply while people approve it. Day AI provides the context graph and agent control plane to quickly and securely upgrade your company brain. If your reps already connect their inboxes and you've written a never-log list, that was the right start.

The connect, share, attach, act loop, with Day AI

Email stops needing manual logging when four things happen without a person in the middle: the inbox is connected, the owner has decided what's shared, each thread lands on the right record, and the email turns into work someone approves.

1. Connect. Each person connects their own Gmail and Google Calendar once, so no email depends on a BCC or a forward. In Day AI, each person connects Google from Settings, under Email and Meetings, and the first sync finishes within hours.
2. Share. Each person decides what their teammates can see before anything is shared. In Day AI, each person sets Email Sharing Rules: share everything or nothing by default, with exceptions by domain, email address or Gmail label.
3. Attach. Each thread lands on the people, companies and deals it's about, and new people become contacts. In Day AI, email reaches the right person, company and deal on its own, and contacts are created from the people you email.
4. Act. New email becomes proposed field changes and follow-up drafts, approved by the rep and written to the system of record. In Day AI, a skill runs after each new email thread is read, the rep approves in Slack or email, and approved changes go to Day AI's own pipeline or to Salesforce or HubSpot through their MCP servers.

How to sync Gmail into your CRM with Day AI

There are two ways to run this, and both are in Day AI. In place of your CRM: Day AI's pipeline, contacts and companies stay current from your team's email and meetings, and there's nothing else to connect. On top of Salesforce or HubSpot: the same email reaches Day AI, and agents write the results back to your CRM through its MCP server. The steps are the same for both except Step 3.

Step 1: Connect Gmail and Google Calendar to Day AI

Each person connects their Google work account, either while setting up their account or later from Settings, under Email and Meetings. One connection brings in both. Gmail is how Day AI learns from your email history, creates contacts from the people you email, and lets you draft and send email from Day AI. Calendar is how it records and preps your meetings. The first sync finishes within hours, and from then on your agents work from that history.

Have everyone who talks to customers connect: account executives, CSMs and founders. A renewal thread in a CSM's inbox or a pricing thread in a founder's is part of the deal, and once they connect, Day AI puts those threads on the record.

Step 2: Set each person's email sharing rules in Day AI

Before anyone's mail is shared with teammates, each person opens Email Sharing Rules in Settings. A new account starts with email private, and each person chooses their own default:

• Share everything with the workspace, then add exclusions for what stays private: a personal domain, your bank, a recruiter, a Gmail label like "Personal". In this mode Day AI also suggests domains you may want to exclude, for you to accept or dismiss.
• Share nothing by default, then add inclusions for what the team should see: a customer's domain, a partner's address, a Gmail label like "Customers".

When rules overlap, the more specific one wins: a Gmail label rule overrides an email address rule, which overrides a domain rule. If two equally specific rules conflict, the email isn't shared. Across teammates, the most private setting wins: a private rule from any teammate keeps a message private, and one private message keeps its whole thread private. Change a rule later and Day AI re-checks the mail it already has.

You can also ask your agent in chat to stop reading email from a domain or address, and Day AI opens your sharing rules with that exclusion ready to save. An agent inherits the permissions of the person it works for, so an agent sees only the email its person can see.

Step 3: Decide where the record lives in Day AI

If you run Day AI in place of your CRM, there's nothing to connect here: the Step 4 skill proposes changes to Day AI's own pipeline, contacts and companies, and the rep approves them the same way.

If you keep Salesforce or HubSpot, each person connects its MCP server from Settings, under Connectors, with their own login, through an OAuth app your company registers. Day AI syncs with Salesforce or HubSpot through their MCP servers, which allow reads and writes when the write tools are turned on, with that person's CRM permissions. Each MCP tool can be set to Always allow, Needs approval or Off.

Step 4: Turn on an email skill in Day AI

In Agent Studio, create a skill and set its trigger to the Email summary event, so it runs after Day AI has read a new email thread. If you keep Salesforce or HubSpot, add it under the skill's Connectors so the skill can use its tools. Write its job in plain words, for example:

When Day AI reads a new customer email on an open deal, propose any change to stage, close date, amount or next step the thread supports, propose adding new people on the thread to the deal, and draft my reply in my voice. Send me one message with the proposals and the draft.

Skills also run on a schedule or when you ask, so a Friday skill can list every open deal whose last customer email went unanswered. Every answer and proposal cites the email it came from. To build trust first, start the skill in learning mode: Day AI reports what it would have changed and asks for your feedback before it's allowed to act. Reply to any run with what to change, and later runs use the change.

Step 5: Decide what reps approve in Day AI

To get proposals in Slack, connect Slack from Workspace Settings, under Integrations, and tell the skill to send its proposals there; otherwise they arrive by email. Write the approval rules into the skill's instructions, field by field. Let Day AI write the low-risk updates, like notes, next steps and tasks, on its own. Send forecast fields like stage, amount and close date to the deal owner for approval in Slack or email. Nothing goes to a customer without the rep: follow-ups wait as drafts until the rep sends them. Every value shows its sources, and you can ask the agent what changed and why. Every skill keeps a history of its runs, including whether each run was delivered by email or Slack.

Where manual email logging breaks, and what Day AI does about it

• The BCC address depends on memory. HubSpot's BCC address logs an email "to the contact, their primary company and their five most recent open deals" (HubSpot), when someone adds it. The reply sent from a phone, or by the CSM who joined the thread late, never arrives. In Day AI, there's no address to remember: each person connects Gmail once.
• "Known contacts only" misses the new people. HubSpot's default rule logs email from known contacts (HubSpot), so the new economic buyer who joins a thread isn't logged until someone creates them. In Day AI, contacts are created from the people you email, and a skill proposes adding them to the deal.
• One sharing setting for everyone. HubSpot's inbox page says "the correspondences you track will be visible to other users in your HubSpot account" (HubSpot). With one setting for the whole team, the people with sensitive inboxes stop connecting. In Day AI, each person sets their own rules by domain, address or Gmail label, and the most private setting wins.
• A copy of the email changes no field. Inbox sync puts emails on the activity timeline of related records (Trailhead). The close date the customer just moved still waits for a rep to type it. In Day AI, a skill reads each new email with the rest of the deal and proposes the field change for the rep to approve.
• The wrong deal. One customer can have a renewal and an expansion open at once, sharing the same contacts, and an email logged by address can land on either. In Day AI, the skill reads the deal's conversations, and you tell it to ask the rep when more than one deal fits.
• The inboxes that matter get left out. When connecting an inbox takes a paid seat or a plan upgrade, the CSM or founder holding the renewal thread is the one who never connects. In Day AI, pricing is per agent with no usage-based pricing, and you can add teammates on the Free plan to capture their meetings and email; see day.ai/pricing.

For calls, see how to update your CRM automatically from call recordings. To bring Slack channels in alongside email, see a Gong alternative that also covers email and Slack.