Orders lost among newsletters
Before a manager scrolls through the mailbox in the morning and finds yesterday's order under a dozen newsletters.
After the order has the «Orders» label and a filled set of fields within minutes of arriving.
An AI agent on OpenAI sorts incoming Gmail, pulls the request details into fixed fields and prepares reply drafts that a person sends
A shared sales mailbox fills up faster than anyone reads it: orders, price requests, supplier invoices, complaints and spam all land in one list. Someone opens each letter, decides what it is, copies the phone and quantity into a CRM or a sheet and writes an answer. The Gmail ↔ OpenAI pair puts an AI agent on that mailbox: Gmail tells it about new mail, the model reads each letter and returns the same set of fields every time, the agent sorts the letter and leaves a reply draft in the same thread. A person reads the draft and presses Send. Below: what moves, which scenarios we cover and what we rely on in both systems.
Before a manager scrolls through the mailbox in the morning and finds yesterday's order under a dozen newsletters.
After the order has the «Orders» label and a filled set of fields within minutes of arriving.
Before a client asks for a price, and the answer goes out the next day because nobody had time to write it.
After a draft with the right price list section is already in the thread, and the manager only checks the numbers and sends it.
Before invoices from suppliers sit in the sales mailbox and the accountant hears about them when payment is overdue.
After letters of type «invoice» get their own label with the amount and due date pulled into fields, and the accountant works from that list.
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-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-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-27Data sent through the OpenAI platform is not used to train or improve OpenAI models by default, unless the account owner explicitly opts in.
Source: developers.openai.com ↗ checked 2026-09-27Structured Outputs makes the model always answer in a predefined structure, without missing a required field or inventing a value outside the allowed list.
Source: developers.openai.com ↗ checked 2026-09-27File transcription: upload a finished recording and get the final text, or receive the text as a stream while the model is processing the file.
Source: developers.openai.com ↗ checked 2026-09-27The limits come from both systems. The model can be wrong: it may misread a type or a quantity, so the fields and drafts are treated as proposals, and no letter is sent without a person. OpenAI limits the number of requests per minute by account level, which grows with usage, so a very busy mailbox on a new account is processed with a short queue. Gmail does not allow a letter to be changed once it exists, so the agent never edits incoming mail: it only adds labels and creates drafts next to it.
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 →Client 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.
See scenarios →OpenAI models inside your CRM: emails parsed, calls summarised, reply drafts ready for a human to check.
See scenarios →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 →OpenAI turns rows written in plain words of a Google Sheet into clean columns and writes product descriptions in bulk, while a person approves what goes further
See scenarios →An AI agent on OpenAI answers questions from 1С/BAS data, turns supplier PDFs and warehouse voice messages into draft documents, and the accountant confirms every one
See scenarios →Implementation · Development · Integrations →
Gmail ↔ OpenAI — the system names are trademarks of their owners. CoreviaFlow is not affiliated with them unless stated otherwise.