Google Compute Engine

development

Compute Engine is where a lot of infrastructure actually lives, and this connection gives Neotask real control over it: creating, starting, stopping, resetting, and deleting virtual machine instances, plus inspecting disks, machine types, images, snapshots, and reservations. That covers both the everyday check — what's running right now — and the more consequential operations, like spinning up a new instance from a template or tearing one down.

• Create, start, stop, reset, or delete Compute Engine instances
• Inspect disks, machine types, images, snapshots, and reservations
• List running instances or check the details of a specific instance template

What you can automate

Google Compute Engine

Manage Google Compute Engine virtual machines, including creating, starting, stopping, resetting, and deleting instances, as well as inspecting disks, machine types, images, snapshots, and reservations.

Real workflows

Check and manage your running instances

Ask Neotask to list what's currently running on Compute Engine, or to spin up a new instance from a specific template, and it handles the request directly.

Frequently asked questions

Can this integration delete a live instance?

Yes, it has that capability — which makes it worth confirming exactly what you're asking for before requesting a delete or reset on a production instance.

Can it tell me what instance template or image was used?

Yes — you can ask it to check the details of a specific instance template, image, or snapshot.