Content & Documents · Integration
Google Workspace
Add Google Workspace to your product for your customers, and give your AI agents governed access to it.
Embed a Google Workspace integration so your customers can work their own documents, spreadsheets, and shared drives from inside your product. Access runs through each customer's own OAuth grant, so their existing sharing and permissions apply and your product cannot open a file the connected account could not open itself. fastn handles per-customer OAuth, token refresh, pagination over large drives, and API upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers browse their own folders and shared drives inside your product and pick a file.
Create a document or spreadsheet from data in your product and file it in the customer's own Drive.
Read a document's contents so your product can summarise or index it without a download step.
Trigger your product when a file in a watched folder is created or changed.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads a customer's document to ground an answer in their own content.
An agent creates or updates a document within scoped permissions, with each action logged.
An agent files a generated report into the right shared drive folder for the customer.
Example prompt
Find documents in this shared drive changed in the last week and summarise the two most recently edited.
Set up Google Workspace in 4 steps
- 01Open the Google Workspace connector from your fastn dashboard.
- 02Have each customer authorise their own Google Workspace account with OAuth.
- 03Map the drives, folders, and file types your product may access, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the Google Workspace integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Google Workspace integration without building it. Your customers connect their own Google Workspace account inside your product and work their files, documents and versions there, with no per-customer code on your side.
- Handle the part that actually costs time: permissions and versioning are easy to get subtly wrong, and mistakes expose content. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Google Workspace update is not your on-call problem.
- One integration serves your product and your agents. The same governed Google Workspace connection powers in-product features and gives AI agents scoped, audited access, so you let your product work with your customers' documents in place without wiring it twice.
Used by these teams
Compare with
Google Docs
DropboxWorks well with
Often used alongside
Tools the same teams tend to run next to Google Workspace, across other categories.
Shopify
Stripe
Jira
AsanaGoogle Workspace integration FAQ
How do I add a Google Workspace integration to my product?
Enable the Google Workspace connector in your fastn dashboard, then let each customer authenticate their own Google Workspace account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Google Workspace client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Google Workspace account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Google Workspace account and only ever sees their own files, documents and versions. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Google Workspace integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reads a customer's document to ground an answer in their own content.
Who maintains the Google Workspace integration?
fastn does. When Google Workspace changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Whose permissions does the Google Workspace integration run under?
Each customer's own Google Workspace grant. Where Google Workspace holds a library, their existing folder and item permissions apply and your product cannot reach content the connected account could not reach itself. Where it processes content you supply rather than storing it, the call runs under that customer's own credentials and is logged per tenant.
Can my product create or update content in Google Workspace automatically?
Where Google Workspace supports writes, documents, entries and assets can be created, updated and filed from your product or by an agent within scoped permissions, with each action logged. Where it is a read surface, the same connection serves reads only.
What can I build with the Google Workspace integration?
A common starting point: browse their own folders and shared drives inside your product and pick a file. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Google Workspace integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Google Workspace does not change your per-connector cost. You can start free with 3 connected accounts.
Add Google Workspace to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.