Cloud / Infrastructure · 45 pre-built actions
Google Cloud Platform integration with Nexus
Run Google Cloud operations through governed workflows. GCS and Pub/Sub events start runs, and Compute, Cloud Storage and BigQuery actions carry out approved work.
Pre-built actions
What you can automate
45 pre-built Google Cloud Platform actions, grouped by what they work on.
45
PRE-BUILT ACTIONS
- 01Compute actions manage virtual machine operations.
- 02Cloud Storage actions work with buckets and objects.
- 03BigQuery actions run queries and work with datasets.
Workflow
How it fits into a Nexus workflow
GCS, GCP Pub/Sub are trigger sources in Nexus. An event can start a governed run directly, and Google Cloud Platform steps then run as pre-built actions in the same workflow.
A trigger source starts work. A connector action performs work. Both run inside the same governed execution.
Beyond pre-built actions
When the pre-built action is not enough
Move down one step: an API, protocol or database call, then custom logic in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript with any library. Every step uses the same secrets, approvals, history and audit.
01
Call the Google Cloud Platform API with the HTTP Request node, or use GraphQL, SOAP or a database node where the system exposes one.
02
Write custom integration logic in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript, with the libraries your team already uses.
03
Direct calls and code use the same vault-backed secrets, approvals, run history and audit as pre-built actions.
Examples
Workflow examples
File arrival to processing
A new object in Cloud Storage starts validation and loads results into BigQuery.
Approved compute changes
Compute changes run only after an operator approves.
Event to incident
A Pub/Sub message opens a ServiceNow incident with context.
Deployment, trust and audit
Governance, audit and deployment
Deployment
Nexus runs on-premises, in private or sovereign cloud, or air-gapped. The step needs network reach to the system it calls, and nothing else changes.
Secrets and identity
Credentials are referenced through vault-backed secret handling and role-based access, never embedded in workflow logic.
Audit
Inputs, outputs, approvals and outcomes are written to the execution history for every run.
FAQ
Google Cloud Platform connector questions
- Which Google Cloud Platform actions are pre-built?
- Nexus includes 45 pre-built Google Cloud Platform actions across Compute (15), Cloud Storage (15) and BigQuery (15).
- Can Google Cloud Platform start a workflow?
- Yes. GCS, GCP Pub/Sub are trigger sources, so an event can start a run directly.
- What if the operation I need is not pre-built?
- Use the Google Cloud Platform API through the HTTP Request node, or write the step in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript. It runs in the same workflow with the same approvals and audit.
Related reading
Continue from here
- AWS connector
EC2, S3, IAM and Lambda.
- ServiceNow connector
Incidents, changes and CMDB.
- Infrastructure orchestration
Operations runbooks with approval and evidence.
- Integration patterns
How systems work together in a complete process.
Integration review
Discuss how Google Cloud Platform fits your process.
Bring the operation you need. We will map it to a pre-built action, or to the API, protocol or code step that covers it.