# Google Contacts The Google Contacts connector is a [Palantir-provided driver](../../data-integration/foundry-provided-drivers/index.md) for Google Contacts. To create a new Google Contacts source, follow the [standard setup flow for Palantir-provided drivers](../../data-integration/foundry-provided-drivers/index.md#setup), then use the sections below for Google Contacts-specific configuration and networking. For the complete property reference, see the [official Google Contacts driver documentation ↗](https://cdn.cdata.com/help/ECK/jdbc/pg_connectionj.htm). :::callout{theme="neutral" title="Beta"} The Google Contacts connector is in the [beta](../../platform-overview/development-life-cycle/index.md) phase of development and may not be available on your enrollment. Functionality may change during active development. ::: ## Supported capabilities | Capability | Status | |---|---| | Exploration | 🟡 Beta | | Batch syncs | 🟡 Beta | | Incremental | 🟡 Beta | | [OAuth 2.0 authentication](#oauth-20-authentication) | 🟡 Beta | | [Table exports](#table-exports) | 🟡 Beta | ## Configuration The properties below are mandatory or recommended. | Property | Required? | Description | Default | |---|---|---|---| | [`AuthScheme` ↗](https://cdn.cdata.com/help/ECK/jdbc/RSBGoogleContacts_p_AuthScheme.htm) | Recommended | The type of authentication to use when connecting to GoogleContacts. | `OAuthJWT` | | [`InitiateOAuth` ↗](https://cdn.cdata.com/help/ECK/jdbc/RSBGoogleContacts_p_InitiateOAuth.htm) | Recommended | Specifies the process for obtaining or refreshing the OAuth access token, which maintains user access while an authenticated, authorized user is working. | `GETANDREFRESH` | | [`OAuthClientId` ↗](https://cdn.cdata.com/help/ECK/jdbc/RSBGoogleContacts_p_OAuthClientId.htm) | Recommended | Specifies the client Id that was assigned when the custom OAuth application was created. (Also known as the consumer key.) This ID registers the custom application with the OAuth authorization server. | — | | [`OAuthClientSecret` ↗](https://cdn.cdata.com/help/ECK/jdbc/RSBGoogleContacts_p_OAuthClientSecret.htm) | Recommended | Specifies the client secret that was assigned when the custom OAuth application was created. (Also known as the consumer secret). This secret registers the custom application with the OAuth authorization server. | — | | [`OAuthJWTCert` ↗](https://cdn.cdata.com/help/ECK/jdbc/RSBGoogleContacts_p_OAuthJWTCert.htm) | Recommended | The JWT Certificate store. | — | | [`OAuthJWTCertType` ↗](https://cdn.cdata.com/help/ECK/jdbc/RSBGoogleContacts_p_OAuthJWTCertType.htm) | Recommended | The type of key store containing the JWT Certificate. | `GOOGLEJSONBLOB` | | [`OAuthJWTSubject` ↗](https://cdn.cdata.com/help/ECK/jdbc/RSBGoogleContacts_p_OAuthJWTSubject.htm) | Recommended | The user subject for which the application is requesting delegated access. | — | ## Networking The table below lists the domains that the source must be able to access to run. For each domain, add a corresponding [egress policy](../../administration/configure-egress/index.md). If the source is hosted on-premises and not directly reachable from Foundry, use an [agent proxy egress policy](../../administration/configure-egress/index.md#agent-proxy-egress-policies) instead. The agent host itself must also be able to reach the listed domains. See [using an agent as a proxy](../../data-connection/agent-proxy/index.md) for details. | Domain | Required | |--- |--- | | accounts.google.com | Always. Required for OAuth | | googleapis.com | Always | | \ | The UpdateOrDeleteContactPhoto stored procedure has a URL parameter that can be used. | ## OAuth 2.0 authentication This connector supports OAuth 2.0 authentication. Follow the [OAuth 2.0 guidance for Palantir-provided drivers](../../data-integration/foundry-provided-drivers/index.md#oauth-20-authentication) to configure and authorize the connection. ## Table exports This connector supports table exports. Learn how to [set up a table export](../../data-connection/export-overview/index.md#table-exports).