Find and use Actions

Actions are the reusable operations a workflow composes. An engineer can automate with existing Actions without maintaining their implementation. The Environment's registry mapping determines which images a Definition can use.

Availability today

These docs do not yet list a released official integration catalog. The repository includes an echo development Action and the authoring guide creates a hello-world example. Neither implies that cloud, Kubernetes, or service-remediation integrations are already published or supported.

Ask your platform team for its approved Action inventory, versions, contracts, and support owners. The current operator CLI has no catalog search command. Your registry and Action documentation are the discovery sources.

The consumer quickstart uses an already installed Pypline first, with an optional echo example once an administrator has supplied its image. The service-health Definition elsewhere in these docs is explicitly illustrative.

Select an Action

Before adding an Action to a workflow, establish:

• Purpose and effects: what it reads or changes, and how it reports success.
• Contract: required inputs, defaults, output fields, and sensitive values.
• Permissions: external credentials, required scopes, and network access.
• Execution behavior: timeouts, partial failure, and whether retrying is safe.
• Compatibility: supported image platforms, Action version, and SDK/runtime requirements.
• Ownership: who publishes it, maintains it, and handles support.

Official, community, and internal Actions should have their provenance and support status stated explicitly. Treat an unknown publisher as an adoption decision, not as equivalent to an approved integration.

Reference a version

A Definition uses name@version, for example echo@2026.10.3. The Environment supplies the registry host and optional repository prefix. Do not put a full registry URL in uses.

Deployment resolves the image, inspects its typed contract, and pins the digest. Check the deployed revision when verifying what will run. Updating a tag does not update existing revisions; adopt a new version through a reviewed Definition and deployment.

Add a missing capability

First check whether your team already maintains a suitable Action. If it does not, an integration owner can use Action development to implement and publish one. Workflow consumers can then reuse it through their Environment's registry.

For a local evaluation, maintainers can use the repository's local appliance and echo setup. Follow publishing when distributing an Action to a shared registry.