Gmail + SalesCrew
Connect a Gmail or Google Workspace mailbox over IMAP and SMTP. Mail arrives in the shared inbox, replies send from your own address, and the thread sits on the contact record.
- IMAP and SMTP, two-way
- Many mailboxes on one instance
- Unsubscribes hit suppression
The short answer
- The mechanism is IMAP for reading and SMTP for sending, not the Gmail API and not a Google Marketplace app. You add the mailbox in Settings and the credentials go into your instance's Supabase Vault.
- Sync is two-way. Incoming mail becomes threads you can read, snooze, draft against and reply to inside SalesCrew, and a reply you send leaves from your Gmail address so the customer sees the same sender they always did.
- Connect as many Gmail mailboxes as you want on one instance. Unlimited seats means the whole team's inboxes can sit in the same queue without a per-mailbox charge.
Mechanism
What connects to what, in which direction, and whether it is available today.
| What | Mechanism | Direction | Objects | Status |
|---|---|---|---|---|
| Mailbox connection | IMAP (read) and SMTP (send) | Two-way | Threads, messages, drafts | Available |
| Thread to record | Matched on the email address in the message | Inbound | Contacts, companies, deals timeline | Available |
| Sending a reply | SMTP from the connected mailbox | Outbound | Messages, timeline | Available |
| Cadence sending | Native mailbox pool over SMTP, with per-account daily caps | Outbound | Cadence steps, campaigns | Available |
| Unsubscribe and bounce | Parsed on receipt, written to the suppression list | Inbound | Suppression entries | Available |
| Draft with AI | Agent writes a draft, a person approves it in the queue | Internal | Drafts, approvals, audit log | Available |
| Open and click tracking | Not built | , | , | On the roadmap |
| Gmail API or Marketplace app | Not used. There is no Google Marketplace listing | , | , | Not planned for launch |
Mechanisms read from the SalesCrew integration table, September 2026. Gmail requires an app password when two-step verification is on; that is a Google account setting, not a SalesCrew one.
Setup
About ten minutes for the first mailbox, less for the ones after it.
- 1
Turn on IMAP in Gmail
In Gmail settings, under Forwarding and POP/IMAP, enable IMAP. On Google Workspace an administrator may need to allow IMAP for the domain first.
- 2
Create an app password
If the account uses two-step verification, generate a Google app password for mail. SalesCrew stores it in your instance's vault and never displays it again.
- 3
Add the mailbox in Settings
Give the host imap.gmail.com on port 993 and smtp.gmail.com on port 465, the address, and the app password. The MCP twin is mailbox_connect.
- 4
Run the first sync
Threads appear in the unified inbox and attach themselves to matching contacts. inbox_sync pulls on demand; after that it runs on a schedule.
- 5
Set the classification rules
Rules run first and label threads by pattern. An LLM fallback labels what the rules miss. Editing them is inbox_category_upsert or the Inbox settings screen.
- 6
Decide the agent mode
The Inbox agent ships in review. It drafts a reply, you approve, edit or reject, and the rejection reason feeds its next run.
Questions
- Is this an official Google integration?
- No. SalesCrew connects over IMAP and SMTP, the open mail protocols Gmail supports. There is no Google Workspace Marketplace listing and no OAuth app. That is worth knowing if your security team requires a reviewed Marketplace app.
- Will sending through SalesCrew hurt my domain reputation?
- It sends from your mailbox over SMTP, so reputation behaves as it does when you send from Gmail. Guardrails cap sends per account and per domain each day, hold sends inside a business-hours window and re-check suppression at send time. Warmup itself is not a SalesCrew feature.
- Can several people share one Gmail inbox?
- Yes. Connect it once and the threads sit in the shared queue with snooze, SLA timers and assignment. Seats are unlimited on every tier, so nobody is left out to save money.
- What happens to an unsubscribe reply?
- It is parsed on receipt and written to the suppression list, which is then enforced when an audience is frozen and again at send time. Bounces do the same.
- Can an agent read my mail?
- Only through a scoped MCP token that you issue and can revoke. Reading and classifying is auto by default; any reply that leaves the building waits in the approval queue. Every tool call is logged with its actor.
Put your Gmail threads next to the pipeline
Connect the first mailbox on day one of the 14-day trial and watch threads attach themselves to records.