Send email with Gmail (Zapier)

Ask an AI employee to “email this customer” or “sum up yesterday’s mail,” and it reads, writes, and sends mail from your own Gmail (or Google Workspace) account. Recipients see your usual address, not an UpServe address.

UpServe does not connect to Gmail directly, though. The Gmail skill uses Gmail through the Zapier connection you set up. So there are two layers to set up: connect Zapier to UpServe, then connect your Gmail account inside Zapier.

At a glance

How is this different from Agent Email?

UpServe also has a separate email skill called Agent Email. The two start from different sender addresses.

For Agent Email, see “Verifying your email for notifications” in Connecting External Services. If Agent Email can’t reach an outside recipient, that doesn’t mean you can’t send email. To send from your own address, use the Gmail skill on this page.

Setup: four steps

   [1] Register Zapier on the Connections screen (sign in to Zapier)
              │
              ▼
   [2] Attach that Zapier connection to the employee that will send mail
              │
              ▼
   [3] Inside Zapier: connect your Gmail account + turn on Gmail actions
              │
              ▼
   [4] Review the final message the employee shows → approve to send

You don’t have to track these steps yourself the first time. Tell an employee “send this with Gmail,” and it finds and uses the Gmail skill; if a step is missing, it shows a connect card or instructions in the chat. Below is where each step lives on screen.

Step 1. Register Zapier on the Connections screen

1. Go to the Skills tab → Connections sub-tab (open ). It’s in the same place on the web, the iOS app, and the Android app.
2. Open the Zapier card in the Automation hub category.
3. In the External tools (MCP) area of the detail panel, tap + Register server, then Register. If you belong to an organization, you also pick Who owns this connection here (choose Just me (personal) to keep it to yourself).
4. When the Zapier sign-in screen opens, sign in and allow access. Once you’re back in UpServe and the Zapier server appears in the panel, you’re done.

The Zapier card’s How to use area also carries a short version of this guidance (Gmail works through the Gmail skill and the Google account you connect).

Step 2. Attach Zapier to the employee that will send mail

Registering Zapier does not make every employee use it automatically. You attach it to the employee that will send mail. There are two ways.

• From the connect card in chat (easiest): when an employee wants to use the Gmail skill but has no Zapier connection, a “Connection required” card with a Connect Zapier button appears in the chat.
  • If you’ve already registered Zapier, tap the button and then Connect in the confirmation dialog. It’s attached to this employee right away.
  • If you haven’t registered it yet, the button takes you to the Zapier card on the Connections screen with the registration form already open. Finish Step 1 there and it is attached automatically to the employee that showed the card. You don’t need to go back to the employee’s settings.
• From employee settings: employee page → Settings tab → External tools (MCP), then turn Zapier on.
  • In the iOS and Android apps, tap the External tools (MCP) row in the employee’s settings. This row is available in app version v1.21.93 and later. If you don’t see it, update the app.

If you started registration directly on the Connections screen (not from a card), or the employee keeps asking for a connection after you registered, check that Zapier is turned on under the employee’s External tools (MCP) settings.

Step 3. Connect Gmail and turn on Gmail actions inside Zapier

Connecting Zapier does not connect Gmail. Inside Zapier you still choose which Gmail account to use and which actions to allow (send email, find email, create draft, reply, and so on).

1. When the employee sees that a Gmail account connection is needed, it gives you the connection link Zapier returns, right in the chat.
2. Open that link and complete the Google sign-in and permission screen yourself. This happens on Google’s and Zapier’s screens; the employee cannot give consent for you.
3. Only the Gmail actions the task needs are turned on. Turning them on also goes through UpServe’s approval steps.

Never paste a password or verification code into the chat. Google sign-in always happens on Google’s own screen behind the connection link. An employee should never ask you for a password or code in chat.

Turning on new actions in Zapier can change the list of Zapier features UpServe knows about. If the employee asks you to refresh, open the Zapier card on the Connections screen, tap Refresh tools, review the changes, and tap Apply changes.

Step 4. Final check and send

Before sending, the employee always shows all of the following together and asks for your approval:

• The sending account (which Gmail address the mail comes from)
• Recipients: To, Cc, and Bcc
• Subject
• The full body
• Attachments (or a note that there are none)

The mail goes out only after you approve, for example by choosing Send. If you decline or don’t answer, nothing is sent. If the recipients, subject, body, or attachments change, the employee shows the revised message and asks again. Approval for one message covers only that message; it never extends to other people or follow-up mail.

After sending, the employee checks the result and tells you it was sent. If the result is unclear (an error or a timeout), it checks your Sent folder before trying again, so the same mail doesn’t go out twice.

Replies are not watched automatically. Gmail replies land in your mailbox, and that alone does not wake the employee. Ask the employee to check for replies, or set up a scheduled run so it checks at set times. Replies you send also go through the same final check and approval as a new email.

Try it like this

Before: You research the customer’s company, write the email, open Gmail, paste it in, double-check the recipient, and send.

After: You say, “Send a follow-up to the contact at Company A about last week’s meeting, with the quote attached.” The employee gathers the material, writes the email, and shows you the sender, recipients, subject, body, and attachment. Approve it and it goes out from your Gmail.

Requests like these work too:

• “Find the emails from Company B this week and summarize them”
• “Draft a reply to the inquiry that just came in”
• With a scheduled run: “Every Monday morning, list the customers to follow up with, prepare the emails, and ask me to approve them”

Good to know

• Zapier tasks are used. Each time the employee successfully calls a Gmail action through Zapier, it uses tasks on your Zapier plan. Failed calls are not counted. Check your remaining tasks and pricing in Zapier. This is separate from UpServe SU.
• Zapier connected ≠ Gmail connected. Even if Zapier shows up on the Connections screen, the employee can’t send mail until you connect your Gmail account and turn on the actions inside Zapier (Step 3).
• Attach it per employee. Attaching Zapier to one employee doesn’t give it to other employees automatically. To let another employee send mail, repeat Step 2 for that employee. You don’t need to register again (Step 1).
• For organization employees, if an organization owner attaches their personal Zapier connection to an organization employee, organization members using that employee can also request email work through that account. Always check whose address the mail will come from.
• Approval doesn’t replace legal consent. Recipient consent, laws on promotional email, and Google’s policies still apply. A publicly listed address is not consent to receive marketing mail. The employee stops contacting anyone who has opted out.
• Sent is not the same as delivered. When the employee says it sent a message, Gmail accepted it for sending; that does not guarantee it reached the recipient’s inbox.

Troubleshooting

Advanced

Most users don’t need this section. Read on only if you want the details of how the connection and approvals work.

How the connection is built

• The Gmail skill is an official (system) skill and declares only one requirement: a Zapier MCP connection. It isn’t auto-equipped, so the employee finds and uses it, or you install it from Skills Explore.
• UpServe’s Zapier entry connects to Zapier’s shared MCP address using OAuth (sign-in). Zapier’s token-style addresses, which differ per account, aren’t part of the catalog.
• UpServe has no direct sign-in connection for Gmail. If an employee looks for a direct connection named “Gmail” or “Google,” the server tells it there is no direct connection and points it to the Gmail skill. This Zapier guidance applies to Gmail only.

How the connect card attaches Zapier to the employee automatically

• The connect card’s buttons are filled in by the server. If you (or your organization) already registered an active Zapier server, the card carries an “attach to this employee” button; otherwise it carries a button to the Zapier card on the Connections screen.
• In the second case, the link to the Connections screen also carries the employee that showed the card. For sign-in servers, the server attaches it to that employee when sign-in completes (even if the first feature-list check fails, as long as the token is valid). The server re-checks your permission to attach; without it, the server is registered but not attached. A failed attach never fails the registration itself.
• The chat connect card appears on the web, iOS, and Android. If the server wasn’t attached automatically after registering, turn it on under the employee’s External tools (MCP) settings.

How approvals stack

• The final pre-send check is a Gmail skill rule: the employee asks with a question card containing the complete message and send/cancel options. If a tool approval card already presents the same message for that decision, it doesn’t ask twice.
• Separately, Zapier tool calls follow Approval for this server under the employee’s External tools (MCP) settings. The default is Ask every time. Loosening it does not remove the Gmail skill’s final message check.
• Connecting an account, installing the skill, permission to research, and setting up a scheduled run are none of them approval to send a particular message.

The Zapier feature list is pinned

UpServe stores and uses the Zapier feature list as of registration or the last applied Refresh tools. Turning on a new Gmail action in Zapier changes the remote list, but the employee won’t call the new action until you apply the refresh. See “The MCP tool list is pinned at registration/refresh time” in Connecting External Services for details.

Reply detection

Gmail replies don’t come through Agent Email’s inbound route, so they don’t wake the employee automatically. The employee reads the thread during requested work or a scheduled run. When replying, it keeps the thread identifier, confirms the actual reply recipients, and gets a new approval.