CID

Export & import

Move workflows and variables between projects as JSON files.

Workflows and variables can be saved to a JSON file and imported into any project — to keep a backup, to copy a setup from one project to another, or to hand it to someone who isn't on the project.

Workflows

  • Export one: open the ⋯ menu on a workflow and choose Export as JSON.
  • Export all: on a project's Workflows tab, click Export all.
  • Import: on the Workflows tab, click Import and choose a file. CID says how many workflows it found before it adds anything.

A file has each workflow's name, trigger, server, steps and whether it's enabled, plus the settings saved on this computer: the shell, each step's working folder and the artifact paths. Run history isn't included.

storefront-workflows.json
{  "cid": "workflows",  "version": 1,  "exportedAt": "2026-11-19T10:00:00.000Z",  "project": "Storefront",  "workflows": [    {      "name": "Deploy to production",      "triggerType": "push",      "triggerBranch": "main",      "triggerCron": "",      "server": "Production",      "enabled": true,      "shell": null,      "steps": [        { "name": "Install", "command": "npm ci", "cwd": "" },        { "name": "Build", "command": "npm run build", "cwd": "web" }      ],      "artifacts": ["web/dist/*.zip"]    }  ]}

What happens on import

  • Names: if a workflow with the same name is already in the project, the imported one gets a number, like Deploy (2). Nothing is overwritten.
  • Servers are matched by name. A workflow whose server isn't in the project is skipped, so it never runs on your computer by mistake — add the server on the Connections tab, then import again.
  • Triggers are kept. Imported push and cron workflows start running on their own straight away; CID warns you about them before importing.
  • Shell: kept if this computer has it, otherwise the workflow uses this computer's default.

The fields are the same as in the Workflow format, with server as the server's name. A file with a single workflow object, or a plain list of them, imports too.

Variables

On a project's Environment tab, the Variables section has Export and Import. Importing adds the new names and overwrites the values of names that already exist; CID lists the ones it will overwrite before it changes anything.

storefront-variables.json
{  "cid": "variables",  "version": 1,  "exportedAt": "2026-11-19T10:00:00.000Z",  "project": "Storefront",  "variables": {    "API_URL": "https://api.example.com",    "NODE_ENV": "production"  }}

A plain object of names and values, like { "API_URL": "https://api.example.com" }, imports as well. Names follow the usual rules: letters, numbers and _, not starting with a number.

Secrets are never exported: CID can't read their values back. Add them again by hand in the project you import into.

On a shared project, anyone who can see workflows or variables can export them, and only owners and admins can import.

Something missing or wrong here? Let us know