Google Workspace Integration
Connect Ascent to Google Workspace so your team can send email and turn inbound Gmail messages into tickets, all through your own Google mailbox using the Gmail API.
Overview
The Google Workspace integration lets you:
- Send Ascent email (ticket notifications, replies, and test messages) through your Google Workspace (Gmail) mailbox.
- Monitor a mailbox and automatically create or update tickets from inbound Gmail.
- Choose which Gmail label to monitor and archive processed messages under a label so they aren't re-processed.
Email is built on the Gmail API and is enabled as soon as you connect a mailbox. Unlike the Microsoft 365 integration, Google Workspace uses a single platform-level OAuth application (the same one used for Google single sign-on), so there is no per-organization app registration — you simply authorize a mailbox.
The integration does not sync contacts or calendars and is not, by itself, a single sign-on provider. (Contact and calendar sync are planned for a later phase.)
Navigate to the integration
- In the left sidebar, open Admin > Integrations (the nav item requires permission to manage integrations, typically the Owner or Admin role).
- Select Google Workspace.
The configuration page is laid out as a Connection card followed by Inbound Sync and Send a test email cards once you're connected.
Prerequisites
- A Google Workspace (Gmail) mailbox.
- Permission to manage integrations in Ascent (typically the Owner or Admin role).
- The Google OAuth application must be configured on your Ascent instance by an
operator (the
GOOGLE_CLIENT_IDandGOOGLE_CLIENT_SECRETenvironment variables). If it isn't, the page shows that the integration is not available on this platform. This is the same OAuth app used for Google SSO.
Required Google scopes
When you authorize a mailbox, Ascent requests these OAuth scopes:
| Scope | Purpose |
|---|---|
https://www.googleapis.com/auth/gmail.modify | Read messages, mark them read, and apply labels (archive) |
https://www.googleapis.com/auth/gmail.send | Send mail as the connected user |
https://www.googleapis.com/auth/userinfo.email + userinfo.profile + openid | Identify the connected mailbox address and name |
Ascent also requests offline access so it can refresh tokens without prompting you to sign in again.
The operator who configures the platform's Google OAuth client must add
https://your-instance.goascent.app/api/integrations/google/callback as an
authorized redirect URI for that client, and ensure the Gmail scopes above are
allowed.
Setup
Step 1: Connect your account
- On the Google Workspace integration page, in the Connection card, click Connect Google Workspace.
- You're redirected to Google to choose the mailbox and authorize the requested scopes.
- After approval, you return to Ascent and the card shows Connected with the connected mailbox address.
To remove the connection later, click Disconnect in this card.
Step 2: Configure inbound sync
The Inbound Sync card controls how inbound Gmail is fetched and turned into tickets.
| Setting | Description |
|---|---|
| Enable inbound sync | Automatically fetch new mail on a schedule. |
| Create tickets from email | New emails with no matching ticket open a new one (see Tickets). |
| Sync interval (minutes) | How often to check, from every 1 to every 60 minutes. |
| Mailbox label to monitor | Which Gmail label to read — Inbox by default, or any label in the connected mailbox. |
| Archive processed messages | Apply a label to processed mail and remove it from the inbox so it isn't processed again. |
| Processed label | The Gmail label applied to processed messages (shown when archiving is enabled). |
Click Save settings to apply.
Enabling Google Workspace inbound sync turns off Ascent's platform-managed inbound email for the organization, so the two never both create tickets from the same messages.
Step 3: Send a test email
In the Send a test email card, enter a recipient address and click Send test to deliver a test message from the connected mailbox and confirm outbound delivery works.
How email-to-ticket works
When inbound sync is enabled, Ascent periodically reads new messages from the monitored label and routes them:
- A new email that doesn't match an existing ticket can create a new ticket (when Create tickets from email is on).
- A reply that matches an existing ticket is added to that ticket's conversation.
Replies thread on the standard
Message-ID/In-Reply-Toemail headers, so they attach to the right ticket. - Processed messages are labeled and removed from the inbox if archiving is enabled.
Troubleshooting
| Symptom | What to check |
|---|---|
| Connect does nothing / "not configured" | The platform's Google OAuth client isn't set up. Ask your operator to configure GOOGLE_CLIENT_ID / GOOGLE_CLIENT_SECRET and the /api/integrations/google/callback redirect URI. |
| OAuth fails or returns an error | Confirm the redirect URI registered with Google exactly matches the one for your instance, and that the Gmail scopes are allowed on the OAuth client. |
| Test email fails | Make sure the account is connected; reconnect if the connection was revoked. |
| Sync isn't running | Confirm Enable inbound sync is on, then re-open the page and review the Last sync status and any error. |
| Connection dropped | Click Connect Google Workspace again to re-authorize; expired or revoked tokens require a fresh sign-in. |
Tips
- Use a dedicated helpdesk mailbox (such as
support@) rather than a personal inbox. - Pick a dedicated Processed label so archived ticket mail is easy to find in Gmail.
For other email options and the full list of integrations, see the Integrations Overview. Ascent also supports Microsoft 365 and a generic SMTP/IMAP connection.