$ loading▍
$ loading▍
Move workflows and variables between projects as JSON files.
this page on cid.pumpkins.devWorkflows 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.
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.
{
"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"]
}
]
}
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.
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.
{
"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.