---
title: "Google Docs Connector"
description: "Implementation notes for building and operating the Google Docs connector in Tajo."
url: https://tajo.io/docs/connectors/google-docs/
markdown: https://tajo.io/docs/connectors/google-docs.md
lang: en-US
robots: noindex
---

# Google Docs Connector

Connector status: Planned Not built yet. Tajo does not run this connector today.

| Source field | Destination field | Sample value |
| --- | --- | --- |
| `record.id` | `source_id` | `record_1042` |
| `record.updated_at` | `updated_at` | `2026-10-18T08:00:00Z` |
| `record.value` | `value` | `sample_value` |

Connector implementation

## Build the Google Docs integration

Campaign briefs, copy drafts, and content documents that can feed Brevo email and automation creation.

Content

*Google Docs connector flow from source system to Tajo mapping and Brevo activation.*

## Implementation Overview

**Build target**

Implement a Google Docs connector that authenticates to the vendor surface, normalizes source records in Tajo, and activates eligible data in Brevo.

**Current status**

Treat this as an implementation guide. Build and validate the auth, mapping, sync, and operations paths before production use.

**Primary surface**

developers.google.com/workspace/docs/api/how-tos/overview

| Property | Value |
| --- | --- |
| Integration surface | Docs |
| Status | Planned |
| Category | Content |
| Setup complexity | advanced |
| Vendor documentation | [developers.google.com/workspace/docs/api/how-tos/overview](https://developers.google.com/workspace/docs/api/how-tos/overview) |
| Allowed host | Not recorded |
| Base URL | Not recorded |
| OpenAPI schema | Not recorded |
| MCP server | Not recorded |
| Last researched | 2026-08-19 |

Useful for Brevo content drafting and approval workflows in assistant surfaces. Google discovery docs, not OpenAPI — normalized from official-api to docs-only to match google-calendar. Docs moved under developers.google.com/workspace/.

## Authentication

- Keep [developers.google.com/workspace/docs/api/how-tos/overview](https://developers.google.com/workspace/docs/api/how-tos/overview) linked from the connector runbook so operators can confirm vendor behavior during incidents.
- Store credentials per Tajo workspace and keep tenant-specific secrets out of connector configuration files.
- Add a credential smoke test that verifies read access to a harmless resource before running backfills or enabling webhooks.

## Data To Sync

Start with these inferred data domains, then confirm exact vendor resources and permissions from the source documentation:

- Campaign, messaging, or audience state
- Custom objects and operational metadata

The connector should make source records idempotent by keeping a stable key such as a vendor object ID, email address, event ID, ticket ID, order ID, or campaign ID. If the vendor only exposes list APIs, Tajo should store the cursor strategy and replay policy explicitly.

## Sync Shape

No typed contract exists for Google Docs, so the direction of each resource and its conflict handling are not recorded. Direction is declared per resource on a connector contract; see the [connector catalog](https://tajo.io/docs/connectors) for how contracts are promoted.

## Mapping To Tajo/Brevo

No Brevo projection is recorded for Google Docs. A projection is declared on a typed connector contract, and Google Docs does not have one yet, so this page will not state a mapping it cannot source.

The conventions that apply to every connector — stable external IDs, normalization, backfill and sync strategy, error handling, and the builder checklist — are documented once under “Applies to every connector” on the [connector catalog](https://tajo.io/docs/connectors).

## Sources

- [Vendor documentation](https://developers.google.com/workspace/docs/api/how-tos/overview)