All integrationsCloud Computing

Google Compute Engine

Start, stop, create and delete Google Cloud virtual machines, change their size and labels, and take disk snapshots.

actions
19
triggers
4

Triggers

Start a workflow when something happens in Google Compute Engine.

  • Instance status changedRuns when an instance starts running, is stopped or is suspended, including a new instance once it is running. Instances as they are when the workflow is turned on don't start it.
  • New instanceRuns when an instance is created. Instances already there when the workflow is turned on don't start it.
  • Instance deletedRuns when an instance is deleted, with who deleted it.
  • New snapshotRuns when a disk snapshot is taken and ready to restore from. Snapshots already there when the workflow is turned on don't start it.

Actions

Steps a workflow can run in Google Compute Engine.

  • List instancesList your instances in every zone, or one, with their status, machine type, IP addresses and labels.
  • Get instanceGet one instance: its status, machine type, IP addresses, labels and when it last started and stopped.
  • Create instanceCreate a virtual machine and start it, from an operating system image, an instance template or a machine image.
  • Start instanceStart a stopped instance. Billing for its CPU and memory resumes.
  • Stop instanceShut down an instance. Its disks are kept and still billed; its CPU and memory aren't.
  • Reset instanceRestart an instance at once, like pressing a reset button. Anything not saved to disk is lost.
  • Suspend instancePause an instance, keeping what is in its memory, so it can carry on where it left off with 'Resume instance'.
  • Resume instanceCarry on a suspended instance from where it was paused.
  • Delete instanceDelete an instance for good, with the disks set to be deleted with it (usually its boot disk). Take a snapshot first to keep its data.
  • Set instance labelsAdd, change or remove an instance's labels. Labels it already has and you don't name are kept.
  • Change machine typeGive a stopped instance more or fewer CPUs and memory. Stop it first with 'Stop instance', and start it again afterwards.
  • Get serial console outputRead what an instance has written to its serial console, such as its boot messages, to see why it won't start.
  • List disksList your persistent disks in every zone, or one, with their size, type and the instances using them.
  • Create snapshotTake a snapshot of a disk, a backup it can be restored from later. The instance can keep running.
  • List snapshotsList your disk snapshots, newest first.
  • Delete snapshotDelete a snapshot for good.
  • List machine typesList the machine types a zone offers, with their CPUs and memory.
  • List operationsList the changes Compute Engine has made or is making in a zone, such as instances started, stopped or created, and who started each.
  • Get operationCheck on a change Compute Engine is making, such as one started with 'Wait until done' off, and optionally wait for it to finish.

Automate Google Compute Engine with Lodol.

Connect Google Compute Engine, then hand Lodol the job in Slack, Claude or ChatGPT.

We’re letting people in a few at a time.