Skip to main content
OpenOps integrates with Archera to automate the review and purchase of cloud commitment plans and the tracking of existing commitments.

​
Actions

OpenOps provides seven actions for interacting with Archera: All Archera actions are based on the Archera API and require configuring an Archera connection with your API token and organization ID. Both are available in the API section of your Archera user settings. The following sections describe the seven actions available in the Archera block. Retrieves the commitment plan that Archera currently recommends for a cloud provider:
  • Provider: AWS or Azure

​
Get Default Commitment Plans

Retrieves the default commitment plans that Archera generates for a cloud provider:
  • Provider: AWS or Azure

​
Get Commitment Plan

Retrieves a specific commitment plan:
  • Plan ID: The UUID of the commitment plan to retrieve

​
Apply Commitment Plan

Applies a commitment plan in Archera:
  • Plan ID: The UUID of the commitment plan to apply

​
Get Commitments Inventory

Retrieves the inventory of existing commitments for a cloud provider within a date range:
  • Provider: AWS, Azure, GCP, Kubernetes, or Unknown
  • Start Date: Start of the date range in yyyy-MM-dd format
  • End Date: End of the date range in yyyy-MM-dd format
  • Search: Optional search term to filter commitments
  • Order By: Optional field to order results by: End Date, Duration (seconds), Start Date, Upfront Cost, Amortized Cost, Recurring Cost, Created At, Updated At, Is Leased, Account ID, Type, Status, Scope, Reservation End, Utilization, or Monthly Savings
  • Descending Order: Sort in descending order (enabled by default)
  • Page: Page number for pagination (defaults to 1)
  • Page Size: Number of items per page, from 1 to 10000 (defaults to 10)

​
Get Metrics

Retrieves savings and utilization metrics for a cloud provider:
  • Provider: AWS or Azure

​
Custom API Call

Allows making arbitrary calls to any Archera 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 Archera workflow runs on a schedule, retrieves the commitment plans that Archera proposes using the Get Default Commitment Plans or Get Recommended Plan action, and asks a person in Slack or Microsoft Teams which plan to purchase before applying it with the Apply Commitment Plan action. The message can include savings figures from the plans themselves or from the Get Metrics action, along with a link back to Archera. If nobody responds before the request times out, the workflow can apply the recommended plan automatically. A second common workflow retrieves existing commitments with the Get Commitments Inventory action and notifies owners about commitments that are about to expire, with a link to renew them in Archera. For the patterns behind approval requests and decision tracking, see Designing Workflows with FinOps Platforms.