Understanding and using Actions in OpenOps workflows
OpenOps provides 120+ actions: operations that you can add as steps to your workflows.When you select an action in the workflow editor, actions are presented as groups. By default, you see a list of all action groups:You can also filter them to show only core actions or actions related to various integrations, referred to as apps:Below is an overview of the action groups currently available in OpenOps. To help you navigate them more easily, they are categorized by intent in the following sections. Some action groups appear in multiple sections if they contain actions with different intents.
These actions help control the sequence of operations in your workflow and make decisions based on inputs:
Condition: split the workflow into exactly two branches based on a condition.
Split: split the workflow into multiple branches based on a condition.
Loop on Items: iterates sequentially over a list. Each iteration runs independently and may finish, fail, or pause, but the loop continues with the next item. After all iterations, the loop’s final state reflects the outcomes: if any iterations fail, the loop fails; if any pause, the loop pauses until they resume. Workflow-wide limits (timeouts or size limits) can also halt execution.
Delay: pause workflow execution for a specified time period or until a specific time.
Stop Execution: stops the execution of the current scope. When used inside a loop, this action skips to the next iteration; otherwise, it ends the entire workflow. This is useful in conditional branching when a branch represents a condition that ends the workflow early.
These actions help you retrieve data from cloud resources, third-party services, APIs, and other sources.
Cloud provider integrations:
AWS: includes multiple actions related to AWS resources such as EC2, EBS, and RDS, as well as a CLI action to execute commands that are not available as dedicated actions.
Azure: execute Azure CLI commands.
Google Cloud: execute Google Cloud CLI commands, run SQL queries on BigQuery.
Recommendation and analytics service integrations:
Archera: retrieve available and recommended commitment plans for cloud providers.
AWS Compute Optimizer: retrieve a summary of recommendations, as well as EBS- or EC2-specific recommendations.
Azure: get Azure Advisor cost recommendations.
CloudFix: get recommendations and reports, or create change requests.
CloudHealth: get recommendations, search assets and retrieve asset perspectives, or manage asset tags.
CloudZero: make API calls to fetch telemetry, billing data, budgets, insights, and more.
Cloudability: retrieve, snooze and unsnooze recommendations.
Finout: get view data and recommendations, manage virtual tags.
Flexera: retrieve active recommendations and incidents.
Flexera Spot: fetch clusters and make custom API calls.
Google Cloud: get recommendations from selected Google Cloud recommenders.
Kion: perform API calls to manage billing sources and cloud rules, get reports, and more.
Pelanor: perform API calls to fetch reports, apply dimensions, monitor anomalies, and more.
Ternary: fetch usage recommendations, retrieve budgets and anomalies, get and create cases and users.
Umbrella (formerly Anodot): get recommendations, manage comments, get user accounts, update user status.
Vega Cloud: get anomalies, perform API calls to fetch recommendations or forecasts.
AWS Athena: run Athena queries.
Snowflake: run individual or batch Snowflake queries.
Databricks: run SQL queries in Databricks workspaces and trigger existing jobs.
File operations: create or read files in OpenOps storage.
HTTP: send HTTP requests to any API or respond to HTTP requests.
Many actions in this group involve writing CLI commands (AWS CLI, Azure CLI, Google Cloud CLI) or SQL queries (AWS Athena, Snowflake, Databricks, BigQuery). The OpenOps workflow editor provides AI assistance to generate such commands and queries, making it less overwhelming for occasional and less technical users. AI assistance works using your own API keys with an LLM provider of your choice. OpenAI, Anthropic, Perplexity, and a dozen other LLM providers are supported.
These are integration actions that provide various ways to make and request changes to your cloud resources via cloud provider APIs, infrastructure-as-code (IaC) tools, or pull requests.
Cloud provider integrations:
AWS: multiple actions related to AWS resources such as EC2, EBS, and RDS, as well as an AWS CLI action to execute any command.
Azure: execute Azure CLI commands.
Google Cloud: execute Google Cloud CLI commands.
IaC integrations:
AWS CloudFormation: update or delete resources in a CloudFormation template.
Terraform: update or delete resources in a Terraform template, modify Terraform variables files.