Skip to content
APFerrer
M-CON-01 · ModuleSoftware development (integrations)

Microsoft Graph and Google Workspace connectors for email and directory

Read-only connectors for Microsoft 365 and Google Workspace directory and mail metadata, with incremental sync that resumes where it stopped, retries and credentials stored encrypted.

Source codeEmbeddableOEM

Integrating with Microsoft 365 and Google Workspace looks simple until you hit rate limits, pagination, access tokens that expire and the same email showing up in several mailboxes. This module pairs a Microsoft Graph connector with a Google Workspace connector. Both read an organization's directory and mail metadata incrementally and pick up where they left off if a sync is interrupted, ready for you to build into your product.

Who it is for

Development teams that need to read their customers' users, groups and email activity without building and maintaining the integration from scratch.

What the Microsoft Graph and Google Workspace connectors solve

  • Syncs that break halfway. The progress marker is saved after each page, so an interrupted job continues where it stopped.
  • Duplicates. The same message seen in several mailboxes, or in both providers, is recorded only once.
  • Integration security. Only links from Microsoft's and Google's official addresses are followed, and credentials are stored encrypted.

What it does

Microsoft 365

  • Handles admin consent in two steps and checks that the person authorizing it really is an administrator.
  • Works with each customer's own app registration or with a shared one for several customers.
  • Reads users, groups, aliases and shared mailboxes from the directory, fetching only the changes since the last read.
  • Reads the metadata of sent and received mail and, if configured, the subject line. If Microsoft limits the initial load, the period actually covered is recorded.
  • Checks which permissions have been granted.

Google Workspace

  • Connects with a service account authorized by the domain administrator.
  • Reads the directory and Gmail metadata, with a bounded initial load and then only the changes. If the change history expires, it recovers on its own.
  • Reads send-as aliases.

In both

  • Retries when the provider throttles requests, waiting as long as the provider asks, and renews access when it expires.
  • Stores credentials encrypted, with periodic key rotation.

Benefits

  • Your team is spared a delicate integration full of edge cases.
  • You read only what you need: directory and metadata, with no message bodies or attachments.
  • An outage in the middle of a sync does not force a restart from zero.

Industry context

General industry data with its public source. These are not results of this product.

What you get with each license

Price upon request, depending on license type and scope. Integration support and maintenance are contracted separately.

  • The module code, ready to add to your application.
  • Integration examples and documentation.
  • A warranty against defects for the agreed period.

Technical specifications

Language and runtime: TypeScript 5.9 on Node.js. Minimum supported version: Node.js 20.19 (required by Prisma 7).

Frameworks: Prisma 7.10 for persistence and Zod 4.6. It does not use the Microsoft or Google SDKs: calls to their APIs are made directly.

Database: PostgreSQL.

Operating systems: Server with Node.js.

Interface languages: It has no user interface of its own.

Required infrastructure:

  • PostgreSQL.
  • A background job system to launch the syncs.
  • Your own encryption keys to store the credentials.
  • For Microsoft 365, an app registered in Microsoft Entra ID (requires your own account).
  • For Google Workspace, a Google Cloud project with a service account and domain-wide delegation (requires your own account).

Private deployment: The module runs on your infrastructure, but it needs a connection to Microsoft Graph and to the Google APIs, which are the source of the data.

Main libraries:

Library Version License
@prisma/client 7.10.0 Apache-2.0
@prisma/adapter-pg 7.10.0 Apache-2.0
pg 8.23.1 MIT
zod 4.6.7 MIT

Dependencies with specific license terms: None of the module's dependencies has a copyleft license or specific commercial terms.

Compatibility and integrations: Microsoft Graph API v1.0 and the Microsoft identity platform (OAuth 2.0, v2.0 endpoints, with admin consent); Google Workspace Admin SDK Directory API v1 and Gmail API v1, with a service account and domain-wide delegation.

Redistribution terms

The asset's own code can be integrated into the licensee's commercial products under the embeddable module, source code and OEM licenses, on the terms of the contract. None of the module's production dependencies has a copyleft license or specific commercial terms.

Installation requirements

A Node.js server application with a PostgreSQL database and a background job system to launch the syncs. For Microsoft 365, you need to register an app in Entra ID; for Google Workspace, a service account with domain-wide delegation.

FAQ

Frequently asked questions

  • Does it read the body of the emails?

    No. It reads the headers and, if configured, the subject line. Bodies and attachments are not downloaded.

  • What permissions do we have to grant?

    Read-only permissions: directory and mail metadata. The module checks what has been granted.

  • Is maintenance included?

    No. Maintenance (updates and bug fixes) and integration support are contracted separately.

Request

Request information on M-CON-01

Fill in the form with the asset reference and the license type you're considering. I reply in writing. If you need to review code, tick the NDA box and we'll sign one before anything is shared.

Controller: APFerrer. Purpose: to answer your request. You can exercise your rights as described in the privacy policy.

Price upon request, depending on license type and scope. Maintenance and support are contracted separately.