A customer asks for a quote on Monday. Someone replies with a price, makes a note to follow up on Thursday, and by Thursday the week has filled up. The enquiry is in Gmail and the notes are in the CRM, but the follow-up message never goes out.

You may be wondering whether Gemini could take over part of this work. One option is to have Gemini check Gmail for a customer's latest message, draft a reply and add a follow-up task in a project management app.¹ That can work. The order of decisions matters more than the tool, though.

Start with one task, not with the connectors

It is tempting to begin with the list of business apps Gemini can connect to.¹ A better start is one task that comes back every week and costs the team time. One task to consider is the follow-ups that slip after a busy week: a quote that got no answer, or an enquiry that needs a second message.

Write that task down in plain words. Where does the enquiry arrive? Where is the customer's history kept? What does a good follow-up look like, and how soon should it go out?

Then name the person who approves each draft. Consider naming the sales manager or the owner. If nobody can be named, the task is not ready to automate yet.

One clear task also tells you which apps Gemini needs to see, and which it does not. If you are still choosing between several tasks, our guide on how to choose your first AI automation walks through that decision.

What it means to connect Gemini to business apps

A connector is a permission link. A connector can let Gemini retrieve information from an app, and some also let it take actions there.¹

Reading means Gemini pulls information from a connected app, for example to find a lead in your CRM.¹ Acting means some connectors also let Gemini create tasks, send messages and update records.¹

Consider what information Gemini could retrieve from connected apps and who should be able to use that connection.¹ Acting adds more, because a message sent to a customer cannot be taken back, and a changed record may go unnoticed for weeks.

Gemini Enterprise has more than 100 connectors for business and productivity services.¹ They cover Google Workspace, Microsoft 365 apps such as Outlook and Teams, Slack, Salesforce, Zendesk and others.¹ Connectors also reach sources such as Confluence, Jira and SharePoint.¹

For a first task, connect only the apps it needs. For a sales follow-up, that is usually email, the CRM and perhaps the place where the team keeps tasks.

Two routes: Gemini Enterprise connectors or a Gemini step in Zapier

There are two practical routes. Which one suits you depends mainly on how the work starts.

Route one: ask Gemini Enterprise in chat

In this route, a person can use the Zapier connector to access apps from the Gemini Enterprise chat window.² Through it, teams can reach more than 9,000 apps from the chat window.² An administrator decides exactly which apps and actions that connector may touch.²

This route suits work that starts with a person asking, such as "draft a follow-up for this customer". If you are comparing Gemini Enterprise plans, check which connectors your plan includes. Ask whoever manages your Google account to confirm this, and which actions are switched on, before you plan the task.

Route two: a Gemini step in a Zap

Consider whether a Zap-based workflow fits this task. A Gemini step in a Zap runs automatically when the Zap triggers.²

With AI by Zapier, you can add a Gemini step to a Zap without a separate Google AI Studio account.² The step runs every time the Zap triggers, and its usage is paid in Zapier tasks rather than on a Google bill.²

This route suits work that should start by itself whenever a new enquiry comes in.

Google AI Studio provides an API key for integrating Gemini models into apps.³

A sales follow-up from enquiry to approved reply

Here is how one follow-up can move from the inbox to a sent reply, with a person in control. This flow matches a pattern Zapier describes: Gemini checks Gmail for a customer's latest message, drafts a reply and adds a follow-up task in a project management app.¹

Workflow · Enquiry to approved sales follow-up
  1. Trigger

    Enquiry arrives in Gmail

    A customer asks for a quote or replies to an earlier offer.

  2. Prepared by the system

    Lead and history found

    Gemini can find a lead in a connected CRM and check Gmail for a customer's latest message.¹

  3. Prepared by the system

    Follow-up drafted

    Gemini can draft a reply and add a follow-up task.¹

  4. Checked by a person

    Sales manager checks

    The named person checks prices, dates and tone, then edits, approves or rejects.

  5. Result

    Reply sent, task logged

    The reviewer sends the approved reply and the follow-up task appears in the team's tool.

How do approval and sending fit together? A simple setup is to have the draft saved where the reviewer already works, for example as an email draft or a task, with no sending action allowed. The reviewer opens it, corrects it and presses send themselves.

The lookup step depends on reading access, which lets Gemini find the lead in the CRM.¹ The drafting step is where most of the tuning happens. In a Zapier Gemini step, you can adjust the prompt (the written instruction), attach knowledge sources such as your price list, and test the output until it looks right.²

A first instruction can be short: "Draft a polite follow-up in the language the customer wrote in. Use only prices from the attached price list. If anything is unclear, list your questions for the reviewer instead of guessing." That last line matters: an unclear request, a message from another channel, or a late change to an earlier request should go to the named person, not into a confident draft.

If enquiries or orders also arrive by WhatsApp or phone, leave those with a person at first. Once the email flow works, the team can forward such messages to the shared inbox so they follow the same checked path. We confirm access during discovery, and if an integration or access limit gets in the way, we explain the options before proposing a solution.⁴

Expect the first drafts to need correction. Collect the edits the sales manager makes in the first weeks, and use them to improve the instruction and the material Gemini reads.

For a safe first setup, start testing with made-up examples or anonymised copies of past enquiries, not real customer data, and leave sending disabled. Feed it a handful of these, let the reviewer judge the results, and switch it to real traffic only when the drafts are reliably close.

The same pattern works for other repeat tasks, such as entering orders into a shared spreadsheet with columns for customer, product, quantity, date and status, where the reviewer checks each row before it counts. Sketch a three-part order workflow: start with a labelled message, extract the order lines, and prepare a row marked "to check" for review. For a supplier order email, the reviewer compares the prepared row with the email, checks quantity and delivery date, notes any unusual request such as a split delivery, and only then sets the status to confirmed. For example, a workflow can use Gemini to decide which form submissions need the product team's attention and send flagged submissions to Slack.² The shape stays the same: the system sorts or drafts, and a person decides.

Decide who approves and what Gemini may touch

Write down three things before the first draft goes to the reviewer. Who approves each follow-up? What do they check, such as the price, the delivery date and the tone? Who handles the exceptions, such as a complaint or a request for a discount the reviewer cannot grant?

Then keep access narrow. When Gemini Enterprise uses the Zapier connector, administrators choose which apps and actions it may use.² For a first follow-up task, reading the inbox and the CRM is usually enough, plus drafting. Sending can stay with a person.

Also decide who may view or change the automation itself: the Zap, the instruction and the connector settings. Keep that to a small group of named people, so nobody widens access to customer data without the owner knowing.

Customer data needs its own short check. Before connecting anything, ask your administrator where message content will be stored, how long it will be kept, and how to delete it. Write the answers down next to the approver's name.

Approval can also be part of the design itself. Agent workflows can be built to pause and wait for human review before they act.⁵ Our article on building reliable AI workflows with human review covers this in more detail.

Warning

Some connectors let Gemini send messages and update records, not just read them.[¹](https://zapier.com/blog/gemini-connectors) Keep sending behind a named person's approval until your business decides that a specific step can safely run on its own.

What drives the effort, the running cost and the language fit

The effort depends less on the connector and more on your own material. If CRM records are incomplete or the price list is out of date, the drafts will be wrong in the same way. Plan a few hours of the owner's or sales manager's time to describe what a good reply looks like, with real examples. Also decide who keeps the price list and service details current after launch.

Running cost grows with volume. A Gemini step in Zapier runs every time its Zap triggers, and each run is paid in Zapier tasks.² Estimate your monthly enquiry count before you choose a plan.

For a small team, list three cost lines. The first is the Google plan your staff use Gemini through, if you take route one. The second is the Zapier plan: on route two, the Gemini step's usage counts against Zapier tasks, not a Google bill.² The third is the reviewer's time, so check each provider's current pricing page against your estimated monthly runs.

Language needs its own test. Do not assume quality in Latvian, Lithuanian or Estonian. Take a sample of real past enquiries in each language your team receives, Russian included if relevant, and let the reviewer judge the drafts for tone and correct terms.

List any nicknames or short forms your customers use for products. Attach a short list of your product names with the everyday names customers use, in each language, as a knowledge source for the Gemini step.² Anything not on the list should go to the reviewer as a question.

Frequently Asked Questions

Can Gemini open and work inside my other apps?

Through connectors, Gemini can read from connected apps, for example to find a lead in your CRM.¹ Some connectors also let it act by creating tasks, sending messages or updating records.¹ With the Gemini Enterprise Zapier connector, administrators decide which apps and actions Gemini can access.²

Do I need Gemini Enterprise to use Gemini in my automations?

No. AI by Zapier lets you add a Gemini step to a Zap without a separate Google AI Studio account.² Gemini Enterprise has its own connectors, including a Zapier connector that reaches more than 9,000 apps from the chat window.¹,² Choose the route by how the work starts: a request typed in chat, or an event such as a new email.

Can Gemini send follow-up emails to customers on its own?

Technically yes, if a connector has write access that allows sending messages.¹ Agent workflows can also be built to pause for human review before acting.⁵ Our advice is that a named person approves each follow-up until the business decides a step can run on its own.

What does running a Gemini step in Zapier cost?

A Gemini step in Zapier runs every time the Zap triggers and is paid in Zapier tasks, not on a Google bill.² Estimate how often your Zap will run when planning for task usage. Ask for a quote for your engagement.

Will it handle enquiries in Latvian, Lithuanian or Estonian?

Test it rather than assume it. Run a sample of real past enquiries in each language your team receives, including Russian if your customers write in it. The reviewer should check tone and terms before anything is sent.

Sources (5)

Have a process you'd like to talk through?

Book a discovery call (opens in a new tab)