Skip to content
Integrations
Google
Integration Scopes

Integration Scopes

Role:
User

Revenue.io requests specific OAuth scopes when you connect Gmail so that email, calendar, and scheduling features work correctly.

Revenue.io provides email and calendar integration for Gmail, powered by the Nylas API. Key capabilities include:

  • Meeting Assistant: Allows your Meeting Assistant Bot to automatically join meetings from connected calendars.
  • Email integration: Enables you to send emails directly from Gmail within Guided Selling.
  • Scheduling pages: Allows you to create and manage scheduling pages for easy meeting booking with prospects and customers.

How users connect to Revenue.io

Users must individually grant access to their Gmail and Google Calendar through the Revenue.io integrations page as part of a secure, user-authorized OAuth 2.0 connection. The Nylas API interfaces with Google’s API.

  1. Open the Admin Console.
  2. Go to User Settings → Integrations.
  3. Click Connect under Gmail.
  4. Complete the OAuth sign-in flow on Google’s website.

For detailed step-by-step instructions, see Connect Gmail to Revenue.io in the Support Knowledge Base.

OAuth scopes

Google scopes

Required scopes:

  • userinfo.profile – Access to basic profile information
  • userinfo.email – Access to your email address
  • openid – OpenID Connect authentication
  • gmail.compose – Create and send email drafts
  • gmail.modify – Read and modify email messages
  • calendar – Full access to Google Calendar for reading and creating events

FAQ

Q: Are all scopes required? Are any optional?

A: All listed scopes are required. Revenue.io requests only the minimum permissions necessary for the integration to function. Each scope serves a specific purpose:

  • Email scopes enable sending emails, reading messages for reply tracking, and managing drafts.
  • Calendar scopes enable meeting discovery, scheduling page functionality, and calendar event synchronization.
  • Profile and authentication scopes are required by OAuth 2.0 for secure user identification.

Removing any scope would block core functionality. Revenue.io does not request unnecessary permissions such as Google Drive access or shared mailbox access. Scope is restricted to the individual user who grants access.

Last updated on