Skip to main content
OpenOps integrates with CloudZero to automate the exchange of cost data and insights between CloudZero and your workflows.

​
Actions

OpenOps provides one action for interacting with CloudZero: The CloudZero action is based on the CloudZero API and requires configuring a CloudZero connection with an API key. API keys are created in CloudZero under Settings > API Keys, and each key is only displayed once after creation. The following section describes the action available in the CloudZero block.

​
Custom API Call

Allows making arbitrary calls to any CloudZero API endpoint:
  • URL: Dynamic endpoint selection
  • Method: GET, POST, PATCH, PUT, DELETE, or HEAD
  • Headers: Optional (authorization auto-injected)
  • Query Parameters: Optional
  • Body: Optional JSON payload

​
Designing a workflow

A typical CloudZero workflow detects an optimization opportunity using OpenOps actions for the cloud platforms OpenOps supports, and then records the finding in CloudZero so that it appears alongside the rest of your cost data. For example, a scheduled workflow can read the list of development accounts from an OpenOps table, look for resources that match a rule specific to your organization, call the Create Insight endpoint through Custom API Call for each finding, and notify the relevant team in Slack with a link to the new insight. Because the block exposes the API through Custom API Call, any endpoint in the CloudZero API reference can be used in the same way, including reading cost data to decide which team to notify. For an example of driving a workflow from an OpenOps table, see Creating a workflow to fill the project-owner mapping table in the CloudHealth guide. For the patterns behind owner mapping and decision tracking, see Designing Workflows with FinOps Platforms.