GOOGLE WORKSPACE
Connect Gmail with clear permissions.
Set up a controlled pilot for exact, approved emails. Keep account connection, action approval and delivery verification separate.
Prepare your Google application
Create a Google Cloud project and enable the Gmail API. Configure the OAuth consent screen with accurate branding, a support contact and your intended audience. For an external test application, add the dedicated pilot account as a test user. Follow Google's web server OAuth guide.
Register the callback
Create a Web application OAuth client. Register the exact HTTPS Console address ending in /marketplace/google-return. Use the same callback in your server configuration. The current connector requires HTTPS, including a pilot; a plain HTTP localhost callback is not supported. Use a controlled HTTPS test environment.
Keep credentials on the server
Provide the client ID and client secret through your deployment's private configuration. Your platform administrator must enable encrypted, durable connection storage. Never enter a client secret in a workflow, publish it in a repository or send it to support.
Limit Google permissions
The connector requests openid, email and https://www.googleapis.com/auth/gmail.send. It does not request mailbox reading or full Workspace access. Your Google Workspace administrator may need to approve the application. Check Google's production requirements before expanding the pilot.
Connect and review access
In Console Marketplace, open Google Workspace and choose the Gmail connection controls. A company administrator selects the Google account, an accountable agent and allowed recipients. Complete Google consent with the same Console session. Connecting an account does not authorize an email.
Verify one approved email
Use a dedicated sender and an agreed test recipient. Select an active signed intent, prepare the exact recipient, subject and message, review the content and approve it. Sending is a separate action requiring an allowed authorization decision. Inspect the receipt and confirm the test message at the destination; Google acceptance alone does not prove delivery.
Test withdrawal and recovery
Confirm that unapproved or changed content cannot be sent. Review credential refresh and disconnect behavior before rollout. If an outcome is unknown, reconcile the provider result before preparing another send. Repeated clicks must not cause duplicate execution.
Understand the current scope
Gmail sending is implemented for controlled evaluation; live provider acceptance remains pending. Attachments, Cc and Bcc are unsupported. Calendar, Drive, Docs, Sheets, Contacts, Chat and Directory are planned. This guide does not establish production readiness.