All features

SDKs and CLI

Manage workflows, runs, and environments from typed SDKs and a command-line tool built for pipelines.

Everything is available in code

The SDKs and CLI expose every platform feature to developers. Typed SDKs for the languages your team already uses wrap the API, so triggering a run, reading a trace, or updating a schedule is a function call in your own application.

The CLI is designed for terminals and pipelines. A developer can scaffold a workflow, run it against recorded events, deploy it to an environment, and tail its logs without opening a browser.

Typical developer workflow

  • Scaffold a workflow with the CLI and commit it to the repository.
  • Run it locally against sample events and read the trace in the terminal.
  • Open a pull request, let the pipeline deploy to staging, and promote after review.
  • Use the SDK from application code to start runs and read results.

Built for automation

Every CLI command returns structured output and meaningful exit codes, which makes it easy to use in a pipeline. API tokens can be scoped to a single environment or action, so a deployment job can deploy without being able to read production data.

The SDKs and CLI are released together and versioned openly, so a team can pin a version and upgrade when it chooses.

Release notes for each SDK and CLI version appear on the changelog page, with the breaking changes called out at the top of the entry.

Back to all features