client.automations is the public entry point for both workflows and agents. Start runs with root client.run().
List
folderId: 'null' lists unfiled YAML workflows at the tenant root. Combining folderId with type: 'agent' is rejected. Agent automations always return folderId / folderPath as null.
Get
workflows.<slug> / agents.<slug>) when a slug could exist in both systems.
Move
Move YAML workflows between organizing folders.folderPath creates missing workflow folders; empty or / (and folderId: null) 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
Start A Run
File Inputs
See File inputs. Pass aFile, Blob, or { content, filename, mimeType } and the SDK uploads via multipart/form-data automatically.