Skip to main content
client.automations is the public entry point for both workflows and agents. Start runs with root client.run().

List

folder_id="null" lists unfiled YAML workflows at the tenant root. Combining folder_id with type="agent" is rejected. Agent automations always return folderId / folderPath as null.

Get

Use typed ids or aliases (workflows.<slug> / agents.<slug>) when a slug could exist in both systems.

Move

Move YAML workflows between organizing folders. folder_path creates missing workflow folders; empty or / (and folder_id=None) files the workflow at root. Agent automations have no database folder model and are rejected.

Delete

Delete uses the same cleanup as the dashboard. Workflows archive the automations registry parent and keep execution history. Agents delete the agent implementation and history, archive the registry parent, and best-effort-delete leftover agent storage. There is no uniform purge of every related artifact.

Folders

client.folders manages workflow and template trees. Deleting a folder cascade-deletes child folders and unfiles contained workflows or templates; it does not delete those resources. Nested agent directories in Git are source organization only and are not folders.

Versions

Triggers

Trigger mutation and source management are intentionally not part of the public SDK surface.

Start A Run

Pin a version or agent source ref by suffixing the target:

File Inputs

See File inputs. Pass a Path, file handle, or {"content": bytes, "filename": str, "mime_type": str} and the SDK uploads via multipart/form-data automatically.