PlaybooksSystemUser Guide

Gmail Setup for Playbooks Emails

By March 4, 2021March 8th, 2021No Comments

Gmail Setup for Playbooks Emails

How to set up Gmail to send emails from Playbooks

Setting Up Gmail for Playbooks Emails

Playbooks allows users to send emails directly from the product using their own email accounts. These emails are tracked and reps are notified when their prospects engage with their emails.

Setting up Gmail for Playbooks emails is pretty simple for most customers. The Playbooks admin will specify Gmail in the Email Service Provider dropdown in the Playbooks Manager > Settings > Email, and that’s it!

Permissions Required/Granted by Playbooks for Gmail OAuth Process

  • https://www.googleapis.com/auth/userinfo.email – Used to obtain the user’s email address.
  • https://www.googleapis.com/auth/userinfo.profile – Used to provide basic user profile info.
  • https://www.googleapis.com/auth/gmail.compose – Used to send email through Gmail on behalf of the end-user.
  • https://www.googleapis.com/auth/gmail.send – Used to send email through Gmail on behalf of the end-user.
  • https://www.googleapis.com/auth/gmail.readonly – Used to look for reply messages from prospects the user has created in Playbooks. This enables our reply tracking functionality.
  • https://www.googleapis.com/auth/calendar.events – Used to create calendar events when a prospect requests a meeting.

Gmail Administrator Actions and End User Impact

  • All actions taken by the administrator occur within the customer’s Gmail instance, not within Playbooks or any XANT systems.
  • Gmail administrator credentials are never entered, seen, used, or stored by the Playbooks application or XANT.
  • Configurations that are set by the Gmail administrator remains in place as part of the customer’s Gmail instance unless manually removed; settings are not tied to any specific Gmail administrator.
  • Permissions listed above are granted for end-users with an active subscription to the Playbooks application.
  • Permissions requested are for delegated permissions, meaning each end-user must go through the setup and OAuth flow upon initial use before Playbooks can access resources on their behalf.
  • Application permissions can be configured on a per-client basis.
  • Application permissions are limited to least privileged based on permissions granted by the customers Gmail administrator. Meaning that if Playbooks requests permissions that were not granted during admin consent in Gmail, the authentication flow will halt.

For additional information regarding the admin consent process and scope, please refer to Gmail’s documentation located at https://developers.google.com/gmail/api/auth/scopes.

Was this article helpful?