Warp icon indicating copy to clipboard operation
Warp copied to clipboard

Import / Export Workflows and Notebooks via CLI

Open asteingass opened this issue 1 year ago • 2 comments

Discord username (optional)

elmo91

Describe the solution you'd like?

It would be great to have a way to import and export workflows and notebooks via CLI. That would open some possibilities to sync files with Obsidian for example. This would greately improve my workflows.

Is your feature request related to a problem? Please describe.

No response

Additional context

No response

How important is this feature to you?

3

Warp Internal (ignore) - linear-label:39cc6478-1249-4ee7-950b-c428edfeecd1

None

asteingass avatar Apr 17 '24 16:04 asteingass

Thanks for this feature request!

To anyone else interested in this feature, please add a 👍 to the original post at the top to signal that you want this feature, and subscribe if you'd like to be notified.

dannyneira avatar Apr 17 '24 22:04 dannyneira

Hi @asteingass We've recently added a "Export all Warp Drive Objects" option to the to the Command Palette (CMD-P on Mac, CTRL-SHIFT-P on Linux). I know it's not a CLI based way to export, but may help in the mean time for backing up your Workflows/Notebooks. See our docs for more.

dannyneira avatar Oct 09 '24 14:10 dannyneira

Any updates on this? The current import/export is really disappointing... might honestly be what turns me off of warp. I definitely cannot in good faith recommend adoption to my team with import/export in its sorry current state.

The fact that export flattens the folder structure is quite frustrating, and the fact that import duplicates shared enums is annoying, but at least with a CLI we could create our own workarounds while we wait for development progress.

stodoran avatar Dec 19 '24 00:12 stodoran

Any updates on this ?

ElTacitos avatar Mar 11 '25 16:03 ElTacitos

Quick up on this, it would be an absolute game changer 😄

ElTacitos avatar Apr 08 '25 15:04 ElTacitos

I cannot for the life of me figure out how to properly import a standardized workflow yaml. The import tool expect a folder selection target despite the button to select the files clearly stating md, yaml, yml files are supportted.

I should not need to put the single yaml I want to import into an empty folder and import that folder. Which partially works as in it imports the file but also the folder structure and doesn't properly sort it into the standard location for workflows within a project/system.

What is really pissing me off is that I have a properly formatted workflow I got from exporting from another project, but the autofill feature in the add workflow editor requires credits to perform the import despite all it having to do is read the yaml structure that I pasted into the empty workflow dialog. Very disappointing.

jpotter23 avatar Dec 18 '25 20:12 jpotter23