$ loading▍
$ loading▍
| Field | Type | Notes |
|---|---|---|
| name | string | Required. Must be unique within the project. |
| triggerType | "manual" | "push" | "schedule" | Defaults to "manual". See Manual, Push, Cron. |
| triggerBranch | string | Only meaningful when triggerType is "push". Blank matches any branch. |
| triggerCron | string | Only meaningful when triggerType is "schedule". A raw cron expression. |
| server | reference | null | The server this workflow deploys to. Empty means it runs on this computer — see Run on this computer. |
| steps | array of { name, command } | Ordered list, run in sequence. command can span several lines. See Steps. |
| enabled | boolean | Defaults to true. Disabled workflows are skipped by both the cron scheduler and the push poller. |
| status | "idle" | "queued" | "running" | "success" | "failed" | The workflow's own last-known status, updated after each run. |
| lastRun | reference | The most recent run of this workflow. |
| lastRunAt | date | When that run started. |
Some settings are local paths or depend on what's installed, so CID keeps them on the computer where you set them instead of in your account:
| Setting | Notes |
|---|---|
| Shell | Command Prompt, PowerShell or Git Bash, for workflows that run on this computer. |
| Step working folders | One optional folder per step, in step order. |
| Artifacts | Paths to keep after a successful run. See Artifacts. |
There are no per-step environment overrides, matrix builds, or conditional steps.