Skip to main content
OpenOps integrates with Cloudability to automate the retrieval and management of cloud resource usage recommendations.

​
Actions

OpenOps provides four actions for interacting with Cloudability: All Cloudability actions are based on the Cloudability API and require configuring a Cloudability connection with your API key and API URL. The following sections describe the four actions available in the Cloudability block.

​
Get Recommendations

Retrieves cost optimization recommendations from Cloudability with extensive filtering options:
  • Vendor Type: AWS, Azure, GCP, or Containers
  • Recommendation Type: Dynamic dropdown based on the selected vendor
  • Look-Back Period: Last 10 or 30 days
  • Cost Basis: On-Demand or Effective pricing
  • Recommendations Status: Show only active, show all (including snoozed), or show only snoozed
  • Limit: Optional maximum number of recommendations to return
  • Additional Filters: Custom filters per Cloudability’s rightsizing API documentation
Below is a sample output returned by this step when it is configured to request active AWS EC2 recommendations with a 10-day look-back period:

​
Snooze Recommendations

Temporarily dismisses specific recommendations:
  • Vendor Type: AWS, Azure, GCP, or Containers
  • Recommendation Type: Dynamic dropdown based on the selected vendor
  • Account ID: The cloud account ID
  • Resource IDs: Array of resource IDs to snooze
  • Snooze Until: Date in yyyy-MM-dd format, or “never” for indefinite snoozing

​
Unsnooze Recommendations

Reactivates previously snoozed recommendations:
  • Vendor Type: AWS, Azure, GCP, or Containers
  • Recommendation Type: Dynamic dropdown based on the selected vendor
  • Account ID: The cloud account ID
  • Resource IDs: Array of resource IDs to unsnooze

​
Custom API Call

Allows making arbitrary calls to any Cloudability 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 Cloudability workflow starts by collecting active recommendations using the Get Recommendations action and iterating through them. For each recommendation, the workflow determines the owner of the affected resource from the tagMappings array returned with it, and asks the owner for a decision in Slack. If the owner approves, the workflow remediates the resource using the actions available for the cloud platforms OpenOps supports. If the owner snoozes it, the workflow delays the recommendation with Snooze Recommendations and can reactivate it later with Unsnooze Recommendations. For the patterns behind owner mapping, approval requests, and decision tracking, see Designing Workflows with FinOps Platforms.