Developer Tools · Integration
Google Cloud
Add Google Cloud to your product for your customers, and give your AI agents governed access to it.
Google Cloud is organised around the project, and a Google Cloud integration inherits that shape. A customer creates a service account in their project, grants it IAM roles, and either hands over a key or federates workload identity instead. The step teams forget is that every API is enabled individually per project: until the customer turns a specific service API on, calls fail with a message about the API rather than about permissions, which sends people hunting through IAM for a problem that is not there. Quotas are counted per project too, and audit logs record the service account that acted. Analytics belongs to the BigQuery connector. fastn holds each service account credential per tenant and follows Google's API changes.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Have each customer create a service account in their own project, so your product runs under an identity they control.
Check that the specific service APIs a feature needs are enabled on the project before onboarding finishes.
Keep usage and quota consumption on the project that caused it rather than on a key you own.
Leave analytics workloads that need dataset and query job depth to the BigQuery connector.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads what a project contains within the roles its service account holds, and the project is recorded.
An agent applies an approved change, traceable in the customer's own audit log to the service account it used.
An agent tells a customer which API needs enabling when a call comes back refused for that reason.
Example prompt
Which APIs are enabled on this project, and does our service account have the roles it needs to read them?
Set up Google Cloud in 4 steps
- 01Enable the Google Cloud connector from your fastn dashboard.
- 02Have each customer authorise their own Google Cloud account, so calls run under their credentials rather than a shared key.
- 03Decide which projects, roles and resources your product needs, then enable each API you call on those projects individually.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Google Cloud integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Google Cloud integration without building it. Your customers connect their own Google Cloud account inside your product and work their services, builds and deployments there, with no per-customer code on your side.
- Handle the part that actually costs time: these systems emit a lot of webhooks, and replay after downtime has to be handled. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Google Cloud update is not your on-call problem.
- One integration serves your product and your agents. The same governed Google Cloud connection powers in-product features and gives AI agents scoped, audited access, so you connect engineering activity to the rest of the business without wiring it twice.
Used by these teams
Compare with
AWS
AzureWorks well with
BigQueryOften used alongside
Tools the same teams tend to run next to Google Cloud, across other categories.
Slack
Snowflake
Airtable
PostgreSQLGoogle Cloud integration FAQ
How do I add a Google Cloud integration to my product?
Enable the Google Cloud connector in your fastn dashboard, then let each customer authenticate their own Google Cloud account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Google Cloud 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 Cloud account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Google Cloud account and only ever sees their own services, builds and deployments. 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 Cloud 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 what a project contains within the roles its service account holds, and the project is recorded.
Who maintains the Google Cloud integration?
fastn does. When Google Cloud 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.
Can I react to Google Cloud events in real time?
Yes, through event triggers. Events are delivered per tenant and can be replayed after an outage, so a webhook missed during downtime is not silently lost.
Can an agent open or update items in Google Cloud?
Yes, within scoped permissions, and every action is audited so an agent's changes are attributable.
What can I build with the Google Cloud integration?
A common starting point: have each customer create a service account in their own project, so your product runs under an identity they control. 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 Cloud integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Google Cloud does not change your per-connector cost. You can start free with 3 connected accounts.
Add Google Cloud to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.