Import

You already have workflows. Start with those.

dagweave reads the workflows you already run, from a repo or straight off a live cluster, and hands them back as standard Argo Workflows YAML, ready to edit on the canvas.

The problem

Your workflows are already running. Not all of them are in a repo.

The ones that only exist on the cluster are hardest to hand to anyone.

dagweave pulls those out through the connector and puts them in your repo.

Getting them in

Bring them in from wherever they are

Not every manifest lives in a repo.

where they come fromtext

git repo   ->  every manifest in the repo, in one pass
cluster    ->  what is actually running, through the connector
paste      ->  manifests, straight onto the canvas

What it can read

It opens manifests dagweave didn't write

Real manifests get written by people, over years. They use retry strategies, artifact repository references, pod spec patches, sidecars, a withParam loop three levels deep.

Your whole file opens, every template and every field.
The newest manifests open the same way, new fields and all, every one of them a control in the inspector.
The first publish rewrites the file: keys sort, indentation reflows, and steps dagweave models get a content-hashed template name. After that, changing one field diffs as one field.

fields from a real manifestyaml

retryStrategy:
  limit: "3"
  retryPolicy: OnTransientError
withParam: "{{steps.shards.outputs.result}}"
artifactRepositoryRef:
  configMap: artifact-repositories
  key: s3-prod

Afterwards

There is only one file, and it's yours

An imported workflow doesn't become a dagweave object with an export button bolted on. It stays a standard Argo Workflows manifest, in your repo, in the format the controller already reads.

You're not maintaining a canvas version and a real version that drift apart. There's one file.
It runs where it ran before: your cluster, your Argo Workflows install, unchanged by the trip through the canvas.
Publish it, and a step matching something already in your registry folds into that template instead of copying it.
Stop using dagweave and there is nothing to migrate back.

Bring the workflows you already run.

dagweave is in early access. Leave an email and we will bring you on as we open it up.