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, then iterating through them, determining the owner of the affected resource, and deciding whether to request an action from the owner. If the owner approves the action, the workflow can remediate the resource using the actions available for the cloud platforms OpenOps supports. Below is a description of common patterns that can be implemented in your Cloudability workflows.

​
Owner mapping

Cloudability recommendations often need to be routed to the appropriate resource owners for review and action. OpenOps workflows can help you map cloud resources to their owners using tag values in the tagMappings array returned by the Get Recommendations action. Subsequent workflow steps may add owners or departments to the preconfigured Tag-owner mapping table. If your Cloudability instance returns specific owners, your workflow can add their contact details to the Tag-owner mapping table automatically. If it does not, you can populate the table manually once for each business unit to ensure that subsequent workflow runs know which team member should receive notifications or approval requests. For an example of implementing owner mapping as a separate workflow, see Creating a workflow to fill the project-owner mapping table in the CloudHealth integration guide. While the guide covers a different FinOps product, the principles of owner mapping apply to Cloudability workflows as well.

​
Recommendation tracking using OpenOps tables and states

Rather than acting on each recommendation once and then losing track of its status, your OpenOps workflow can log Cloudability recommendations to the preconfigured Opportunities table for centralized tracking and status management. Workflows using the Get Recommendations action can create or update table records with details such as estimated savings, resource IDs, recommendation types, and current status (Created, Under Review, Dismissed, Snoozed). This approach prevents duplicate notifications, provides audit trails, and enables reporting on realized vs. unrealized savings across your organization. Learn how to implement opportunity tracking by following the CloudHealth recommendation logging workflow.

​
Handling recommendations via Slack

For recommendations that require human judgment, OpenOps can send interactive Slack messages that allow resource owners to approve, dismiss, or snooze optimization opportunities directly from Slack. After retrieving recommendations with Get Recommendations, workflows can use owner mapping to identify the appropriate Slack user, then send a Slack message with buttons for different responses using Request Action in the Slack action block. Based on the user’s selection, the workflow can call Snooze Recommendations to temporarily dismiss false positives or proceed with automated remediation actions. Decisions are tracked in the Opportunities table. See Send a Slack notification with action buttons in the CloudHealth guide for implementation details.