Skip to main content
Source reviewedConfirm availabilityConnection profile

Gmail

Source-reviewed capability blueprint for Gmail: Connect an individual Gmail or Google Workspace mailbox for one-to-one email sync with existing contacts. Confirm Hoop availability before setup.

Ask about setup
PublisherGoogle
Expected behaviorRecord sync
SetupConfirm path and access
ReviewedAug 9, 2026
Confirm this connection path before setup.

This source-reviewed capability blueprint describes expected behavior and vendor requirements. It does not confirm that Hoop has enabled this connection for your account.

Overview

This profile describes the expected connection path if it is enabled in Hoop. Personal Gmail sync keeps supported one-to-one messages visible in both Gmail and Hoop. Mail sent from Hoop can appear in Gmail, and replies from an existing contact can appear in the matching conversation. Campaign and workflow email use a separate account-level sending provider.

Expected data flow

From Hoop

Hoop email to Gmail

Expected when enabled: A supported one-to-one email sent from Hoop can appear in the connected Gmail Sent folder.

Into Hoop

Gmail reply to Hoop

Expected when enabled: An eligible email from an existing contact can appear in the matching Hoop conversation and contact record.

Expected capabilities

  • Expected when enabled: Keep supported one-to-one sent mail in Gmail
  • Expected when enabled: Bring eligible replies from existing contacts into Hoop
  • Expected when enabled: Use BCC logging to add supported messages when needed

Expected setup

  1. 01

    Expected setup step when enabled: A Google account with Gmail

  2. 02

    Expected setup step when enabled: The mailbox connected from the user profile

  3. 03

    Expected setup step when enabled: Google permission approval for the requested email access

Expected requirements and limits

  • Expected constraint for this path: Past mailbox history is not imported.
  • Expected constraint for this path: Unknown senders generally do not enter Hoop through normal personal sync until a contact or supported logging path exists.
  • Expected constraint for this path: Bulk, campaign, and workflow email use the account-level sending provider, not this personal Gmail connection.
  • Expected constraint for this path: Google account sending limits and recipient restrictions apply.
  • Expected constraint for this path: Multi-recipient threads can be associated with one contact rather than copied as a shared mailbox thread.
Authentication
Expected authentication if this path is enabled: Open the user profile, choose Email two-way sync, select Gmail, and approve the requested Google permissions.
Account requirements
Setup assumptions only; confirm Hoop access first. A Google account with Gmail enabled and a Hoop user profile that can connect a personal mailbox.

Sources

The linked sources and profile copy were reviewed on Aug 9, 2026. These sources document the connected service's rules and APIs; they do not confirm that the connection is enabled in Hoop or in a particular account. The next source review is due Nov 9, 2026.

Implementation support

Want help setting up this integration?

Keep browsing

Related integrations

Google Calendar

Source-reviewed capability blueprint for Google Calendar: Use Google Calendar busy time to prevent conflicts and write Hoop bookings to one linked calendar. Confirm Hoop availability before setup.

Slack

Source-reviewed capability blueprint for Slack: Send workflow updates from Hoop to people or channels in a connected Slack workspace. Confirm Hoop availability before setup.

Facebook

Source-reviewed capability blueprint for Facebook: Capture Facebook leads, manage Page conversations, schedule Page content, and run supported Meta ad campaigns from Hoop. Confirm Hoop availability before setup.