Google Workspace Connector

Use the Google Workspace Connector when your team keeps reference material in Google Drive and wants that material available inside Applied.

This is a strong fit for help centers, internal support playbooks, product notes, policy documents, and other content your AI agent should learn from.

What this Connector is best for

Google Workspace is most useful when:

Your team stores source material in Google Drive.
You want one place to maintain documents that Applied can use.
You want to bring approved documents into Data and then connect them to Knowledge.

Many teams also use Google tools operationally in Flows, but this guide focuses on the document sync path that supports customer answers.

Before you begin

Before connecting Google Workspace, make sure:

The right person has access to the Drive files you want to use.
The files are up to date and written clearly.
Sensitive internal-only material is separated from customer-facing guidance.

If a document is messy or outdated in Google Drive, syncing it into Applied will not improve it automatically.

Connect Google Workspace

Open Connectors.
Click New.
Choose Google Workspace or the Google option shown in your workspace.
Complete the authorization flow.

Once connected, you can use the connection to bring files into Applied.

Import files into Data

After the connection is ready:

Open Data.
Choose the import option for Google Drive.
Select the connected Google resource.
Enter the file you want to bring in.
Save the import.

The imported file will appear in Data, where you can review its status, source, topic, intent, and connected Knowledge.

Turn Data into Knowledge

After a file is in Data, you have two main options:

Autogenerate Knowledge when you want Applied to draft Knowledge from the synced material.
Review the Data first and then create or refine Knowledge more manually when wording and quality need tighter control.

This is usually the right pattern:

Import a clean source document.
Review the synced Data.
Generate or connect Knowledge.
Test real questions before relying on it in production.

When to use autogenerated Knowledge

Autogenerated Knowledge works best when the source document is:

Structured clearly.
Written in direct language.
Limited to one topic or workflow.
Updated by a reliable owner.

Use more manual review when the source includes:

Internal notes mixed with customer guidance.
Long multi-topic documents.
Draft language your team would not want sent to customers.

Keeping Google-based material current

When the source document changes, resync the Data so Applied can refresh what it knows.

You can usually manage this in one of two ways:

Run a manual resync when an important change is published.
Set a schedule for regular refreshes.

After a resync, review whether connected Knowledge still looks right before treating the update as fully production-ready.

Best practices

Use one source of truth for each policy or workflow.
Prefer smaller, focused documents over one giant file.
Remove outdated content from Google Drive instead of leaving competing versions around.
Test high-volume questions after major updates.

Common issues

The wrong file was imported

Check the file identifier and verify the file lives in the connected Drive resource you selected.

The Data looks fine but answers still need work

The source material may be too broad, too long, or not written in a customer-ready format. Refine the document or curate the connected Knowledge more directly.

Updates are not showing up yet

Run a manual resync or review the configured sync schedule.