Google Mail

Overview

Gmail, Google’s email service, offers a comprehensive platform for communication and productivity. With features like advanced search capabilities, powerful filters, and seamless integration with other Google Workspace tools, Gmail is a cornerstone of modern email management.

By integrating Suger with Gmail, users can leverage automation workflows to enhance email productivity. Tasks such as sending emails, applying labels for organization, and managing threads can be automated, improving efficiency and enabling customized email workflows tailored to specific needs.

You can connect Gmail at two levels:

• Org-Level: Connect once for your organization, so Suger can send automated email from a corporate mailbox that everyone’s workflows share. There are two connection methods to choose from — a Service account with domain-wide delegation, or Sign in with Google — described below.
• User-Level: Each user connects their own Gmail account via OAuth 2.0, so automated emails are sent from that person’s own inbox.

How the connection works

Whichever method you use, Google issues the credential and Suger refreshes it for you — Suger never holds your Google password. What differs afterwards is how a given Gmail operation reaches Google. Composing operations — creating, updating, sending and deleting drafts, and sending a message — are performed by Suger directly, so a slow send is not cut short by an action timeout and never leaves you unsure whether the mail went out. Every other Gmail action (labels, filters, send-as aliases, vacation settings) runs through Suger’s standard connector path.

Create Integration (Org-Level)

Org-level Gmail offers two connection methods. Both are set up from the same Gmail card under Settings → Integrations: click the Connect dropdown and pick the method you want.

Your organization connects one way at a time. Once connected, the Gmail card shows “Connected via {method}” — for example Connected via Sign in with Google — so you can always tell which method is in force. To switch methods, delete the integration and connect again with the other one.

Method 1 — Service account (domain-wide delegation)

This method is designed for company-wide automation where Suger sends email by impersonating a specific corporate address (for example, sales@company.com) without a user manually signing in.

1. Create a service account in your target GCP project for Google Mail integration.
2. Enable the Gmail API in the same Google project.
3. Create the service account key, and download the associated JSON file. It is required for the following integration.
4. Enable G-Suite Domain-wide Delegation for the service account.
5. Specify the impersonated email address, select the appropriate scopes configured in the previous step, and store the JSON key file contents within the Suger console integration page.

The default scope for this method is send only (https://www.googleapis.com/auth/gmail.send). Domain-wide delegation is all-or-nothing: a request asking for any scope your Workspace admin did not authorize fails entirely, so if you need Suger to read mail as well, use Sign in with Google instead.

Method 2 — Sign in with Google (OAuth)

This method authorizes a mailbox directly in the browser, using the same Google OAuth application as the user-level connection. No Workspace admin action is required, and it grants both send and read scopes.

1. In the Suger Console, go to Settings → Integrations and find the Gmail card.
2. Open the Connect dropdown and choose Sign in with Google.
3. You are redirected to the Google sign-in page. Sign in with the mailbox your organization should send from — this is the account every workflow in your organization will send as, so use a shared or role mailbox rather than a personal one.
4. Review the requested access and click Allow.
5. Once you are redirected back to the Suger Console, click Verify. A Verified status confirms the connection is ready.

Create User Integration

User-Level integration is personal and precise. It lets Suger send emails that look like they came from you, while automation handles the repetitive work.

• OAuth 2.0 Security: Suger never sees, asks for, or stores your Google password. The connection is a secure, token-based handshake.
• Responsive automation: Send automated private offer links and follow-up sequences the moment a buyer hits a milestone.
• Thread management: Keep your deal discussions organized without jumping between tabs.

1. In the Suger Console, go to the User Integrations section (under your profile settings). Locate the Google Mail card and click Connect Now.

   

2. You will be redirected to the Google sign-in page. Select the account you want to use for your marketplace deals.

3. Review the request and click Allow. This grants Suger the permissions needed to read and send emails related to your marketplace workflows.

   

4. Once you are redirected back to the Suger Console, find your new integration and click Verify. A Verified status confirms Suger is ready to send on your behalf.

Suger AI Tools

When Gmail is connected, the Suger AI agent works your mailbox through Suger’s built-in tools. The composing tools are the ones you will name most often; they carry a google_email__ prefix.

You never have to hand the agent a pre-assembled raw email: it supplies the recipients, subject and body as ordinary fields, and Suger builds the message — including correct handling of non-ASCII subject lines.

Edit Integration

Editing is not supported for security reasons. To change configuration, delete the integration and create a new one.

Delete Integration

The Google Mail integration can be deleted like all other integrations. Once the deletion is triggered, all integration info including the service account key and access tokens will be deleted immediately & permanently from Suger. No time window or methods to recover.