Skip to main content
OpenOps integrates with Finout to automate cost allocation with virtual tags and the retrieval of cost data and CostGuard recommendations.

​
Actions

OpenOps provides five actions for interacting with Finout: All Finout actions are based on the Finout API and require configuring a Finout connection with your Finout client ID and secret key. See Generate an API token in the Finout documentation for how to obtain them. The following sections describe the five actions available in the Finout block.

​
Get View Data

Retrieves the cost data of a saved Finout view:
  • View: Dynamic dropdown of the views available in your Finout account
Below is an example of the output returned by this step for a view grouped by a single dimension, based on the example response in the Finout API reference. The step returns the view ID and one entry per group, without the Total entry:

​
Get Virtual Tag Values

Retrieves virtual tags together with their possible values:
  • Virtual Tags: Dynamic multi-select of virtual tags to retrieve. Leave empty to retrieve all virtual tags

​
Add Value to Virtual Tag Filter

Adds a value to the filter of an existing virtual tag rule, for example to map a cloud account to a team:
  • Virtual Tag: Dynamic dropdown of the virtual tags in your Finout account
  • Tag Filter: Dynamic dropdown of the values defined for the selected virtual tag
  • Value to Add: The value to add to the selected filter

​
Get CostGuard Recommendations

Retrieves the recommendations produced by a CostGuard scan:
  • Scan: Dynamic dropdown of the CostGuard scans configured in your Finout account

​
Custom API Call

Allows making arbitrary calls to any Finout 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 Finout workflow focuses on cost allocation. Create a view in Finout that lists the accounts or resources without a team tag, retrieve it on a schedule with Get View Data, and retrieve the current virtual tags with Get Virtual Tag Values so that the list of teams stays in sync with Finout. For each untagged item, ask the FinOps owner in Slack which team it belongs to, with one button per team in Request Action or a Block Kit select element for a long list of teams. Once a team is chosen, Add Value to Virtual Tag Filter maps the item to that team, so that it is no longer returned as untagged on the next run, provided the view filters on that virtual tag. Recommendations retrieved with Get CostGuard Recommendations can be routed to resource owners and remediated in the same way as recommendations from other platforms. For the patterns behind approval requests and decision tracking, see Designing Workflows with FinOps Platforms.