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

Actions

OpenOps provides three actions for interacting with Flexera One: All Flexera actions are based on the Flexera One API and require configuring a Flexera One connection, where you need to specify your app region, refresh token, organization ID, and project ID. The following sections describe the three actions available in the Flexera block.

Get Active Recommendations

Retrieves active cost optimization recommendations from Flexera:
  • Policy Set: Dynamic dropdown of available policy sets from your Flexera account
  • Filter by Provider: Optional filter by cloud provider (AWS, Azure, Google, or Alibaba)
Below is a sample output returned by this step when it is configured to request active Azure recommendations for the “Unused Volumes” policy set:

Get Incident

Retrieves details of a specific incident from Flexera:
  • Incident ID: The unique identifier of the incident to retrieve

Custom API Call

Allows making arbitrary calls to any Flexera One 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 Flexera workflow starts by collecting active recommendations using the Get Active Recommendations action and iterating through them. For each recommendation, the workflow determines the owner of the affected resource from the tags array returned with it, and asks the owner for a decision in Slack or Microsoft Teams. If the owner approves, the workflow remediates the resource using the actions available for the cloud platforms OpenOps supports. Decisions can be written back to Flexera with the Custom API Call action. For the patterns behind owner mapping, approval requests, and decision tracking, see Designing Workflows with FinOps Platforms.