Engineering integration guide
Google Cloud + UbiGrowth workflows
Google Cloud is Google's cloud platform, covering infrastructure, data services, and analytics workloads. This guide covers the records that matter, how the connection should be scoped, and what the first bounded workflow should be.
Introduction
Make Google Cloud part of the workflow, not another silo.
Validate connector availability for your workspace
This guide covers how a team designs a engineering workflow around Google Cloud with UbiGrowth: which records stay authoritative, how the connection should be scoped, what the first bounded workflow should be, and how to tell whether it worked.
The records that matter are Project, Service Account, IAM Policy, Cloud Logging Entry, Billing Account, and Resource. Google Cloud scopes almost everything to a Project, and Service Accounts are themselves identities that can be granted access across projects. The effective permission set is the union of several bindings, not one role.
Google Cloud is not currently on UbiVibe's verified connector list. This page is an implementation design reference: use it to specify the workflow, then validate whether the connection is available and correctly scoped for your workspace before you make it a dependency. The verified UbiVibe connections today are Salesforce, HubSpot, Gmail, Google Drive, Slack, and GitHub.
The platform layer is the usual destination for this connection, because the value shows up as governed context and execution shared across more than one team.
Why teams evaluate this connection
Integrations create value when they remove operating friction.
The first design decision is not which API endpoint to call; it is which system owns the record, what event should trigger work, who owns the exception path, and what successful completion means.
Engineering systems produce more signal than any other part of the business and the least usable summary. Google Cloud knows exactly what happened; turning that into something the rest of the company can act on is manual work that nobody owns.
The second problem is direction of risk. An integration that reads engineering activity is low-risk and useful. An integration that can act on infrastructure or production systems is a different category entirely, and the two are often discussed as if they were the same project.
You're likely here because
- Engineering activity is invisible outside the engineering team
- Incident context has to be reassembled manually every time
- Internal tool requests sit behind product work indefinitely
Record model
What a Google Cloud integration actually reads and writes.
Integration design starts from the objects the system really exposes, not from a generic connector diagram. These are Google Cloud's.
Identity and matching
Google Cloud scopes almost everything to a Project, and Service Accounts are themselves identities that can be granted access across projects. The effective permission set is the union of several bindings, not one role.
Start here
Read Service Accounts with keys older than the rotation policy and route the rotation to the project owner.
What this will not do
It will not centralise identity. Workload Identity and service account keys are different security postures; an integration should not quietly pick the weaker one.
The constraint to plan around
Each API must be enabled per project before it can be called, so an integration that works in one project returns a not-enabled error in another with identical permissions.
Build notes
What you actually have to reason about in Google Cloud.
The fields that carry meaning, how the connection authenticates, and whether the event surface can be trusted. This is the part that decides whether the integration works in month three.
| Field | Why it matters |
|---|---|
| project id | the primary scope for resources, quota, and billing |
| service account email | an identity in its own right, grantable across projects |
| IAM binding | effective permission is the union of bindings, so a single role tells you little |
| API enabled state | per project, and a disabled API returns an error that reads like a permission problem |
| labels | the cost-attribution mechanism, exported to BigQuery billing |
Authentication
Service account with Workload Identity Federation where possible, avoiding downloadable keys entirely. A service account key file is a long-lived credential that grants everything the account has, and they leak through repositories more than any other credential type.
Events and delivery
Pub/Sub carries events with at-least-once delivery and no ordering unless explicitly enabled. Cloud Audit Logs record control-plane activity and can be routed to Pub/Sub, which is the supported path for reacting to changes.
Workflow
How the Google Cloud workflow runs.
The operating sequence, from reading the source system through to the result landing back where it belongs.
Step 01
Connect read-only first
Google Cloud is connected with scoped, read-only credentials so context and reporting value can be proven without any action risk.
Step 02
Assemble the engineering picture
Delivery, incident, or operational activity is summarized in a form the rest of the business can act on rather than a raw feed.
Step 03
Build the internal surface
Launch produces the dashboard or internal tool that was never going to clear the product backlog, reviewed like any other internal service.
Step 04
Bound any action path
If the workflow needs to act, that path is specified separately with explicit scope, approval, and a record of what ran.
Design decisions
The engineering decisions this connection forces.
Each of these has to be settled before the Google Cloud workflow is allowed to write anything.
Step 01
Separate read from act
Reading Google Cloud for context and reporting is a different risk decision from letting a workflow act on it. Do not bundle them into one project.
Step 02
Make execution paths explicit
Any action that reaches a real environment should run through a reviewable execution path with a record of what ran, not an implicit side effect.
Implementation path
How to implement the Google Cloud workflow.
- 01
Start read-only against Google Cloud and produce something the team already wants: delivery visibility, incident context, or an operational summary.
- 02
Use scoped credentials rather than a shared token, and confirm what the scope can actually reach.
- 03
Build the internal surface in Launch, and review the result as you would any other contribution.
- 04
Once key rotation is routed, extend to eliminating keys entirely in favour of federated identity, project by project.
Governance
Controls that matter.
Control 01
Credentials are scoped and workspace-approved; no shared secret belongs in a prompt or in generated code.
Control 02
Actions that reach production systems run through explicit, reviewable execution paths.
Control 03
Generated code and configuration are reviewed on the same terms as any other change.
Failure modes
How a Google Cloud integration breaks in production.
Not generic integration advice. These follow from how this system actually behaves, which is why they look nothing like the list on the next guide over.
Symptom 01
An operation fails in one project and works in another with identical permissions.
Cause
The API is not enabled on that project.
Fix
Check and surface API enablement state distinctly from permission errors — the messages look alike and the remedies differ.
Symptom 02
A service account key is found in a public repository.
Cause
Downloadable keys are long-lived credentials that leak like any other file.
Fix
Use Workload Identity Federation and disable key creation by policy where possible.
Symptom 03
Effective permissions are broader than any single role suggests.
Cause
Permissions are the union of all bindings across the hierarchy.
Fix
Audit effective permissions with the policy analyser rather than reading individual role grants.
What changes at scale
Quotas are per project and per API, so a multi-project sweep has independent budgets that can each throttle. Handle throttling per project rather than globally.
Examples
What a working Google Cloud workflow looks like.
Bounded scenarios rather than a feature list. Each one can be verified against work the team already does.
Cloud operations
With Google Cloud connected read-only, delivery and operational activity can appear alongside commercial context instead of living in a separate report.
Internal tool that was stuck in the backlog
A small tool reading Google Cloud gets built in Launch and reviewed like any other internal service, without consuming sprint capacity.
Limitations and considerations
What to validate before you depend on this.
- Each API must be enabled per project before it can be called, so an integration that works in one project returns a not-enabled error in another with identical permissions.
- IAM writes change who can reach what, across projects if the binding is set high enough. An automation with IAM write permission can grant itself more, which is the definition of privilege escalation.
- When key-based authentication would be required. If the integration cannot use federated identity, that is worth solving before granting long-lived keys.
- Write or action access to Google Cloud is a materially different risk decision from read access and should be scoped, reviewed, and approved separately.
- Generated code and configuration still require review. Speed of production does not change ownership of what ships.
FAQ
Google Cloud integration questions.
What records does a Google Cloud integration actually work with?
The primary records are Project, Service Account, IAM Policy, Cloud Logging Entry, Billing Account, and Resource. Google Cloud scopes almost everything to a Project, and Service Accounts are themselves identities that can be granted access across projects. The effective permission set is the union of several bindings, not one role.
What should the first Google Cloud workflow be?
Read Service Accounts with keys older than the rotation policy and route the rotation to the project owner.
What will a Google Cloud integration not do?
It will not centralise identity. Workload Identity and service account keys are different security postures; an integration should not quietly pick the weaker one.
What is the main constraint to plan around?
Each API must be enabled per project before it can be called, so an integration that works in one project returns a not-enabled error in another with identical permissions.
What changes about a Google Cloud integration at scale?
Quotas are per project and per API, so a multi-project sweep has independent budgets that can each throttle. Handle throttling per project rather than globally.
How does authentication work for Google Cloud?
Service account with Workload Identity Federation where possible, avoiding downloadable keys entirely. A service account key file is a long-lived credential that grants everything the account has, and they leak through repositories more than any other credential type.
Does Google Cloud support webhooks, and can they be trusted?
Pub/Sub carries events with at-least-once delivery and no ordering unless explicitly enabled. Cloud Audit Logs record control-plane activity and can be routed to Pub/Sub, which is the supported path for reacting to changes.
What is the risk of writing to Google Cloud?
IAM writes change who can reach what, across projects if the binding is set high enough. An automation with IAM write permission can grant itself more, which is the definition of privilege escalation.
When is connecting Google Cloud the wrong call?
When key-based authentication would be required. If the integration cannot use federated identity, that is worth solving before granting long-lived keys.
What should a Google Cloud integration automate first?
Start with one bounded workflow that removes a measurable handoff, duplicate-entry step, reporting delay, or follow-up gap. Expand only after the first workflow is reliable.
Does UbiGrowth require Google Cloud to be replaced?
No. The operating model is designed around connecting to systems that should remain authoritative and building workflows around them rather than forcing a wholesale replacement.
Is connector availability identical for every workspace?
No. Availability can depend on provider configuration, authentication, scopes, workspace setup, and deployment state. Validate the required connection before treating it as an operational dependency.
Can the workflow act on Google Cloud, not just read it?
Action paths are possible but should be treated as a separate, bounded project with scoped credentials, explicit approval, and a record of what ran.
How are credentials handled?
Through workspace-approved, scoped grants. A shared secret pasted into a prompt or embedded in generated code is not an acceptable pattern.
What is a safe first integration?
A read-only workflow that produces something the team already wants from Google Cloud — delivery visibility or incident context — before any action path is considered.
How this access is governed
What ARIA is allowed to do in Google Cloud, and who decides.
Connecting Google Cloud is a permission decision, not just a setup step. These are the controls that decide what ARIA can reach, what it can change, what gets recorded, and how you take the access back.
Required permissions
ARIA works through the scopes the connection was granted, and no others. Authorization happens at the provider, so the permissions being requested are shown by the system itself before anything is connected.
What it can reach
Reachable systems are the intersection of what your organization approved in the connector registry and what the requesting identity is permitted to use. Identity resolves before execution, not after.
What it can do
Actions run through explicit execution paths with state, spend, and failure boundaries — a bounded worker path rather than an open-ended agent loop with a credential.
Credential handling
Credentials live in the governed connection layer and are resolved through canonical connection identity. They are not pasted into individual workflows, prompts, or generated artifacts.
Action logging
Execution carries state and traces: what triggered the work, which connection it used, and what came back — including an explicit failure when something did not run.
Approval and revocation
Consequential actions can be made to require a person to approve them. Access can be changed or revoked at the connection, and ARIA loses that reach without unpicking the work already completed.
Start with ARIA
Ask ARIA to run this integration.
Describe the outcome you need across this system. ARIA works out the scopes, data, and actions the job requires, and operates inside the access you grant — which you can change or revoke.
- ARIA acts only through the systems and permissions you connect.
- Connections use scoped credentials you can change or revoke.
- Actions are recorded, and consequential ones can require approval.
Start here
Turn the integration into a working business outcome.
Start with ARIA to describe the outcome, then continue into the product path that fits the workflow. Connector availability and required scopes should be validated for the specific workspace before production use.