Ship deep Gmail and Google Calendar integrations in days

Gmail and Google Calendar each have their own API, real-time updates need watch channels and Pub/Sub topics, and every account keeps its own calendars, labels, and filters. With Ampersand, you can get this integration live for your customers in days.

Build a custom data model to handle complex configurations

No two Google Workspace accounts are the same. Every customer has their own calendars, sharing rules, labels, and filters. AI agents need infrastructure that understands Gmail and Google Calendar at the per-tenant level.

3 / 4 customers

3 / 8 customers

  • Customer A: Event (standard), Message (standard), Label (standard)
  • Customer B: Event (standard), Calendar (standard), Filter (standard)
  • Customer C: Message (standard), Draft (standard), Thread (standard)

Enable software and agents to take bi-directional action

With Ampersand, your engineers don’t need to learn the Gmail and Calendar APIs, watch channels, or Pub/Sub push notifications. Simply declare the actions you want your agents to take: read, write, subscribe, proxy.

Example. Subscribe: “Notify me as soon as a meeting is booked or moved.”

  1. Ampersand opens a watch channel on this customer’s primary calendar.
  2. Push notifications arrive, and each one says only that something changed.
  3. Ampersand fetches the events updated since the last checkpoint.
  4. Ampersand tells new, edited, and canceled events apart.
  5. Ampersand applies this customer’s field mappings.
  6. Ampersand sends the event to your product.

Ensure your Google integration is always available

  • Managed auth

    Fully offload Google OAuth. Ampersand stores and refreshes every customer’s tokens for the Gmail and Calendar scopes you choose.

  • Managed watch channels

    Ampersand opens the Calendar watch channel and the Gmail watch when each customer installs your integration, so you don’t set up webhooks yourself.

  • Incremental reads

    After a historic backfill, Calendar event and Gmail message syncs read only what changed, so your integration moves less data on every run.

Not all Gmail and Calendar integrations are created equal

Gmail and Google Calendar are where many teams email their customers and book meetings with them. With Ampersand, your developers can create a best-in-class Google integration.

In-House DIY Build Unified APIs Embedded iPaaS Ampersand
Data schema that works for all customers Lots of switch statements and special casesOnly access standard objects and fieldsBuild customer-specific workflows Flexible model with mappings
Real-time data Run Pub/Sub topics and calendar watch channels for every customerNo real-time dataYou can get real-time data, but not batch data You pick between real-time data and scheduled syncs
Object coverage Write and maintain clients for the Gmail and Calendar APIsOnly common models and their standard fieldsLimited to the objects its prebuilt actions cover Gmail and Calendar objects, plus proxy calls to other Google APIs
OAuth token custody You own the tokens, but you also have to manage refreshesVendor lock-inVendor lock-in Export at any time via API
Integration workflow Imperative custom codeSingle API clientDrag-and-drop, not integrated with Git Declarative manifest you can version control

The Gmail and Calendar objects your agents can read and write

Ampersand reads and writes Google Calendar and Gmail, subscribes to calendar events and new mail, and proxies calls to other Google APIs, such as Drive.

Objects What’s included Read Write Subscribe
Calendar events (Module: calendar)
  • Events
Supported Supported Partly supported, see the note below the table
Calendars and sharing (Module: calendar)
  • Calendar list
  • Access control rules
Supported Supported Not supported
Calendar settings (Module: calendar)
  • Settings
Supported Not supported Not supported
Messages and threads (Module: gmail)
  • Messages
  • Threads
Supported Partly supported, see the note below the table Partly supported, see the note below the table
Drafts and labels (Module: gmail)
  • Drafts
  • Labels
Supported Supported Not supported
Mail settings (Module: gmail)
  • Filters
  • Send-as aliases
  • Forwarding addresses
  • Delegates
  • Identities
  • Key pairs
Supported Supported Not supported

Write sends new Gmail messages; threads are read-only. Subscribe covers Calendar events on each customer’s primary calendar, and Gmail messages in the inbox. Gmail needs a one-time Pub/Sub setup in your Google Cloud project.

Calendar events backfill at most 28 days of history, a limit of the Google API. Incremental reads cover Calendar events and Gmail drafts, messages, and threads; other objects are read in full on each scheduled read.

See every object in the docs

Questions people ask before they book a demo

  • Which Gmail and Google Calendar objects can I read and write?

    In Google Calendar, you can read and write events, the calendar list, and access control rules, and read settings. In Gmail, you can read and write drafts, labels, filters, send-as aliases, forwarding addresses, and delegates, send messages, and read messages and threads.

  • Can I get real-time updates from Gmail and Google Calendar?

    Yes. For Calendar events, Ampersand creates and manages the watch channels when a customer installs your integration, with no webhook setup on your side. For Gmail messages, you set up a Pub/Sub topic in your Google Cloud project once, and Ampersand watches each customer’s inbox.

  • Does Google need to verify my app?

    Yes, before you connect external customers. While you build, add up to 100 test users to your app. When you are ready to launch, publish the app from the OAuth consent screen and complete Google’s verification.

  • Does Ampersand offer a unified API?

    Ampersand doesn’t offer a unified API. It works with Google’s own objects and fields as each customer sets them up, which differs from how a unified API works. We also give you the primitives to build your own unified data model.