Documentation Index
Fetch the complete documentation index at: https://help.statisfy.com/llms.txt
Use this file to discover all available pages before exploring further.
Connect Google Workspace with Statisfy
The Google Workspace integration links your Gmail and Google Calendar to Statisfy through a single OAuth connection. Once connected, Statisfy can:- Pull historical and ongoing calendar events for the connected user
- Send emails from the user’s Gmail account via the Gmail Send V2 Agent Studio component
- Listen for replies via the Gmail Reply Listener V2 component
- Power role-based sends so workflow emails appear to come from the right team member
Google Workspace is a per-user integration — each user who wants Statisfy to act on their behalf must connect their own Google account. Connecting yours does not give Statisfy access to your teammates’ Gmail or Calendar.
What Gets Synced and Used
| Capability | Scope |
|---|---|
| Calendar events | Read access to your calendar so Statisfy can match meetings to accounts and run Upcoming Meeting V2 triggers |
| Gmail send | Send emails as you from Agent Studio flows |
| Gmail read | Read replies to emails Statisfy sent on your behalf (used by Gmail Reply Listener V2) |
Prerequisites
- A Google Workspace account (consumer
gmail.comaccounts also work) - The Statisfy admin must have enabled the Google Workspace integration in your org
- A connected CRM (Salesforce or HubSpot) — non-CRM integrations are gated until at least one CRM sync has completed
Steps to Connect
- Log in to Statisfy.
- Navigate to Integrations → Google Workspace.
- Click Connect. The Statisfy OAuth dialog opens; click Continue with Google.
- Sign in to your Google account when prompted.
-
Review the requested scopes:
- Calendar (read-only) — needed to import events
- Gmail send — needed for
Send Emailactions to send as you - Gmail read-only — needed to detect replies to outreach
- Profile / email — needed to identify the connected account
- Click Allow. You’ll be redirected back to Statisfy and the connection is confirmed.
- The bootstrap job runs a one-time historical backfill of recent calendar events. After that, Statisfy keeps in sync via Google’s push notifications.
Using Google Workspace in Agent Studio
Once connected, Google Workspace powers several Agent Studio components:| Component | What it does |
|---|---|
| Gmail Send V2 | Sends an email as the connected user. Use Send As Role (e.g., Account Owner, CSM) to pick the right sender per account automatically. |
| Gmail Reply Listener V2 | Pauses a flow until a recipient replies to an email previously sent by Gmail Send V2. |
| Upcoming Meeting V2 | Triggers a flow when a calendar event matches a meeting segment — uses the connected user’s calendar data. |
| Meeting Segment V2 | Triggers on past meetings ingested from Google Calendar. |
Managing Your Connection
- Go to Integrations → Google Workspace.
- To disconnect, click Disconnect. Statisfy stops accessing your Calendar and Gmail; in-flight Gmail Reply Listener nodes will time out and fail closed.
- To re-authorize (for example, to grant a newly added scope), click Reconnect. You’ll be sent back through the consent screen.
Troubleshooting
Authorization failed
Authorization failed
Calendar events not appearing in Statisfy
Calendar events not appearing in Statisfy
- Confirm your CRM integration has completed at least one successful sync.
- Bootstrap may still be running; check back after a few minutes.
- Verify the meeting has at least one external attendee whose domain matches a known account.
Gmail Send fails with 'no Gmail connection'
Gmail Send fails with 'no Gmail connection'
- The user selected via Send As Role must have personally connected their Google Workspace account. Connecting under a shared admin account does not grant send rights for other team members.
- Ask the relevant user to visit Integrations → Google Workspace and click Connect.
Replies not detected by Gmail Reply Listener
Replies not detected by Gmail Reply Listener
- The connected user must still have Gmail read access — check that the connection wasn’t revoked.
- The reply has to land in the same Gmail thread Statisfy sent from. Forwarded replies from a separate address are not matched.