Automation & workspaceUSClient emails land in the CRM deal card, replies go out from the manager's own address, and the AI prepares a draft — without sending it.
Gmail is the mailbox where most requests actually arrive: forms from the website, replies from clients, quotes from suppliers. The trouble is that the mailbox and the CRM live apart — a manager reads a letter, forgets to put it into the deal, and a week later nobody remembers what the client asked. We connect the mailbox to the client's CRM: a letter from a known address goes into that contact's deal card, a letter from an unknown address becomes a new lead, and the reply written in the CRM goes out from the manager's own Gmail address in the same conversation thread. An AI assistant can read the letter and prepare a reply as a draft in Gmail; a person checks it and presses Send. The connection works only with the mailboxes whose owners granted access to it.
Before the website form writes to a shared mailbox; three people read it, each thinks a colleague took the letter, and the request sits unanswered.
After every letter from the form becomes a lead in the CRM with the sender's name, address and the text of the request, gets an owner by the CRM's rules, and the letter in Gmail is marked with an 'in CRM' label.
Before the client replies to a manager's letter; the reply stays in that manager's mailbox, and the deal card in the CRM says nothing about it.
After a letter from a known address is attached to the deal of that contact, and the manager answers straight from the CRM — the letter goes out from his own Gmail address and lands in the same thread, so the client sees an ordinary reply.
Before a manager spends the first hour of the day typing the same answers — 'yes, in stock', 'the price list is attached', 'we deliver to your city'.
After the AI reads the incoming letter and the deal history, prepares a reply as a draft in the manager's Gmail; the manager opens Drafts, fixes a couple of words and sends. Nothing leaves the mailbox without a person.
Before a letter from a new company sits among newsletters and notifications, and whether it becomes a client depends on who noticed it.
After a letter from an address that is not in the CRM creates a lead in the chosen pipeline; the letter text goes into the lead's notes, and newsletters and automatic notifications are filtered out by the rules we agreed at setup.
For those who want to check: each point links to the official documentation page it comes from.
Gmail can notify the connected application itself whenever a mailbox changes — Google offers this as the way to learn about new letters without checking the mailbox on a schedule.
Source: developers.google.com ↗ checked 2026-09-27Replies and the original letter are grouped into one conversation thread, so the whole exchange on a deal can be read in order.
Source: developers.google.com ↗ checked 2026-09-27A draft in Gmail is an unsent letter with the system label DRAFT; when it is sent, the draft disappears and a letter with the label SENT appears — this is how the AI draft waits for the manager.
Source: developers.google.com ↗ checked 2026-09-27A Gmail user can grant access to his mailbox to another user within the same Google Workspace organisation; the delegate can read, send and delete letters on his behalf.
Source: developers.google.com ↗ checked 2026-09-27Google recommends requesting the narrowest set of permissions possible and not asking for access the application does not need.
Source: developers.google.com ↗ checked 2026-09-27Once a letter is created in Gmail it cannot be changed — the connection stores letters as they are and writes a copy into the CRM.
Source: developers.google.com ↗ checked 2026-09-27Google measures the load on Gmail in its own units and limits how many a project may spend per minute and how many a single user may spend; when the limit is hit the request is refused and repeated after a pause, so bulk work is done in small groups. One letter may have at most 500 recipients. The subscription to notifications about mailbox changes must be renewed at least once every seven days; Google itself says notifications may in rare cases be delayed or lost, so a scheduled check of the change history is always kept as a backup, and the history is usually available for about a week. An application that reads and sends mail must pass Google's verification, and if the letters are stored on the application's servers a separate security assessment is required — we take this into account when planning the setup. The connection works only with mailboxes whose owners have granted access; nobody else's mail is visible. A letter once created cannot be changed.
Three steps from a first message to work on your project.
Describe the task in the form — in text or by voice. Budget and timing are optional.
A developer studies the brief, asks about anything unclear and sends an estimate.
Once scope and price are agreed, the work begins.
or write to info@coreviaflow.space
Describe the task in text or a voice message. We look at your setup and reply with a plan.
Four services people come to us for most often. Each page explains what we do, how the work goes and where to start.
Choose the system, set up the pipeline, migrate data, train the team.
Learn more →Accounting, telephony, website, payments and messengers feed the CRM on their own.
Learn more →Orders, requests and answers around the clock, straight into your CRM.
Learn more →Flows between CRM, email, spreadsheets, payments and AI, on your own server.
Learn more →
↔An AI agent on Claude reads the whole Gmail thread with its PDF attachments, drafts the next reply in context and leaves it for a person to send
See scenarios →↔
An AI agent on OpenAI sorts incoming Gmail, pulls the request details into fixed fields and prepares reply drafts that a person sends
See scenarios →
CRMUAUkrainian CRM that pulls orders from your site, marketplaces and chat apps into one pipeline
See scenarios →
CRMUSUS CRM with built-in calling and no-code automation, ready to plug into the tools you already run
See scenarios →
CRMEUThe deal-focused CRM: connect it once, and deals, contacts and follow-ups keep themselves in sync
See scenarios →
CRMUAThe CRM built for order-taking: every lead from every channel lands in one place on its own
See scenarios →
Automation & workspaceUSThe spreadsheet your team already lives in: leads flow from a Google Sheet into your CRM, reports flow back into the sheet, and nobody copies rows by hand
See scenarios →
Automation & workspaceUSSlack as the team's alert desk: leads, deals and calls from the CRM land in a channel, and the team acts on them without leaving the chat
See scenarios →Implementation · Development · Integrations →
Gmail is a trademark of its owner. CoreviaFlow is not affiliated with it unless stated otherwise. Screenshots are taken from public vendor materials; the source is shown under each one.
