noCRM.io and Gmail: what syncs, what doesn't, and how to set it up
noCRM.io connects to Gmail to send and receive emails inside the CRM and attach them to leads. The full two-way sync needs the Dream edition. Other editions log email with Bcc.
- Connector
- Native, built by noCRM. Email sync runs through Nylas, a third-party synchronizer. Set up from inside noCRM.
- Sync direction
- Two-way for email; noCRM → Google Calendar for next actions (separate connection)
- Setup time
- A few clicks per user; every user connects their own inbox
- Availability
- Full email integration: Dream edition. Bcc logging: all editions. The docs state no Gmail plan requirement.
- Our rating
- 4 out of 5. Two-way Gmail send and receive with automatic lead matching, but only on the Dream edition; other editions get Bcc logging.
| What | Direction | Detail |
|---|---|---|
| Sent emails | noCRM → Gmail | Reps write to leads and prospects from noCRM. noCRM sends through the Gmail API and attaches the email to the record. |
| Received emails | Gmail → noCRM | Emails from prospects and leads land in the noCRM Inbox and attach to the matching record. |
| Replies sent from Gmail itself | Gmail → noCRM | Dream edition only. noCRM attaches the reply to the matching lead. Emails it cannot match wait under Pending emails. |
| Opens and clicks | Derived | Tick Enable emails tracking in the Preferences section. Opens and clicks show on the email in the lead form and in the notification center. |
| Email aliases | Gmail → noCRM | Dream edition only. Create the alias in Gmail first, then add it in noCRM. It then appears in the From dropdown. |
| Bcc logging | Gmail → noCRM | All editions. Bcc your noCRM address and the email attaches to the lead's comments. Leads only, not prospects. |
| Next actions as calendar events | noCRM → Google Calendar | Separate connection per user. noCRM creates the event when a lead moves from To Do to Standby with both a date and a time. |
Setting it up
- Check that your noCRM account is on the Dream edition. On other editions, use the Bcc address from the Pending Bcc emails page.
- As each user, click the envelope icon in the top navigation bar and select Email synchronization in the left-hand menu.
- Follow the on-page instructions to connect the user's Google account.
- To send from an alias, create it in Gmail first. Then go to Email synchronization, scroll to Email aliases and click Add an email alias.
- In the Preferences section of Email synchronization, tick Enable emails tracking if you want open and click data.
- To sync next actions, go to Settings > Tools > Calendar and click Connect my Google account.
Where the integration stops
- The full integration needs the Dream edition. On other editions, use Bcc. It attaches sent emails to leads only, rejects attachments over 20 MB, and accepts only mail from addresses you declared.
- Every user connects their own inbox. One email address cannot connect to two noCRM accounts. Extra addresses must be aliases of the primary one. Otherwise sync your main address and use Bcc for the rest.
- Gmail's API rate limit can block sending from noCRM. Google sets the limit, and noCRM says it cannot tell when it resets. Send from Gmail directly in the meantime.
- Reading in noCRM does not mark mail as read in Gmail. Check both places if you triage in both.
- Deleting an email from the inbox deletes it from the lead. Admins can restrict deletion to admins in Account Settings.
- Calendar events need a date and a time. A next action with a date only does not reach Google Calendar. After a Google Calendar update, you may have to reconnect.
The noCRM.io and Gmail connector lets reps send and receive Gmail messages inside noCRM. It attaches each message to the matching lead or prospect. It suits sales teams that live in Gmail and want the email history on the lead without copying it over.
The fact that surprises teams: the full sync is not on every edition. noCRM's help center says the full email integration is only available with the Dream edition. Other editions get a Bcc system that logs sent emails on leads. Check noCRM pricing before you plan around it.
Dream gets the sync, other editions get Bcc
With the Dream edition, noCRM sends through the Gmail API and receives into its own Inbox. It attaches both directions to the lead or prospect. A reply you write in Gmail attaches too, so reps can work from either place.
On other editions, the rep Bccs a personal noCRM address. noCRM attaches the email to the lead's comments. It works for leads only, not prospects, and it rejects attachments over 20 MB. If noCRM cannot tell which lead you meant, the email waits under Pending Bcc emails.
Each user connects, and Gmail sets the sending limit
noCRM does not connect one mailbox for the whole account. Every user connects their own inbox from the envelope icon. The same address cannot join two noCRM accounts. Extra sending addresses work only when they are aliases of the primary address.
Gmail's API limits are Google's, not noCRM's. A rep who sends many emails from noCRM can hit "Rate Limit Exceeded". A second tool on the same Gmail account adds to the count. Emails sent from Gmail itself still reach the lead, or wait under Pending emails.
noCRM also states that it syncs mail through Nylas. If Gmail blocks Nylas as a sender, you may see a "Message blocked due to spam content" error. The fix is on the email provider's side.
Two behaviors to explain to the team
Reading an email in noCRM does not mark it as read in Gmail. A rep who works from both places sees unread counts that disagree.
Deleting an email from the inbox also deletes it from the lead. That removes history from the record. Admins can limit deletion to admins in Account Settings. Set this before the team starts.
Calendar sync is a separate connection
Connecting Gmail for email does not connect Google Calendar. Each user connects the calendar under Settings > Tools > Calendar. noCRM creates an event when a lead moves from To Do to Standby with a date and a time. The docs describe this as noCRM → Google Calendar and mention no sync back.
The docs I read do not say whether older Gmail messages import when you connect. They also state no Gmail plan requirement, so test with one user before you roll out.