CloudFlow now speaks Oracle Cloud

automate your OCI FinOps practice with the same flows you already run on AWS, Google Cloud, and Azure.

Oracle Cloud "waste" is easy to accumulate and annoying to clean up. Unattached block volumes bill at full price whether anything reads from them or not. Reserved public IPs start billing the moment they sit unassigned. Most teams know this. Fewer teams have a repeatable way to act on it, because until now CloudFlow could automate AWS, Google Cloud, and Azure, and OCI was a manual job. That gap is closed. CloudFlow now has an Oracle Cloud node (available today in Early Access).

What you get

The Oracle Cloud node lets a flow call OCI services directly. We didn't hand-pick a dozen actions. The service and operation catalog is generated from the official OCI SDK, so structured control-plane operations are available across OCI services. You pick a compartment and a subscribed region, configure the operation's parameters, and pass the output to the next node. Pagination is handled for you via the opc-next-page header.

Setup is deliberately boring. If your OCI tenancy is already connected to Cloud Intelligence™ for cost and usage reporting, the node reuses that same OCI asset. You add one IAM policy for CloudFlow and you're ready. The OCI connection guide has the exact policy.

Guardrails, because deletes are deletes

Destructive operations like DeleteVolume and DeletePublicIp support approvals. Right before deletion, CloudFlow re-fetches the resource and sends a conditional request with its ETag. A block volume must be AVAILABLE with no active attachment in any accessible compartment in the region. A public IP must be AVAILABLE, RESERVED, and unassigned. This cuts down race conditions where a resource changed between listing and deleting.

Start with the templates

Two prebuilt templates cover the most common OCI waste, and each has a step-by-step tutorial:

• Delete unattached Oracle Cloud block volumes
• Delete unused Oracle Cloud reserved public IPs

Both follow the same shape: list candidates on a schedule, filter to the ones that are safe to remove, route to a human for approval, delete, notify. Once you've run one, you'll see how to adapt the pattern to whatever your OCI environment accumulates.

Get started

1. Connect your OCI account, if you haven't already.
2. Create an OCI connection and add the CloudFlow IAM policy.
3. Open Templates in CloudFlow and pick one of the Oracle Cloud templates, or read the Oracle Cloud node docs and build from scratch.

Oracle Cloud nodes are available to customers enrolled in Early Access. If you run OCI and want in, talk to your account manager. The best feedback we can get right now is from teams pointing this at real tenancies.