My pleasure! And yep! That’s what I’m saying. I dug into this a little bit for anything to watch out for and here’s what I found:
The CLI won’t stop you from acting on the wrong folder/recipe so you can add a mandatory step and have the agent run wk folders list / wk recipes list / wk recipes get <id> first, print back the resolved folder or recipe name and wait for you to give it the go-ahead before it runs any move/update/delete/etc.
Also, copying a recipe into your personal folder won’t duplicate the connection, it’ll just keep pointing at the same connection ID. So, if the agent also calls “wk connections update/delete/disconnect” on that shared ID, that affects every recipe using it, not just your copy.
And then wk doesn’t have folder scoping of its own (Project Grants aren’t wired into the CLI) so in Workato, you might set up a separate API client/Client Role that only has access to your personal folder. That way even if the agent tries to write to the wrong folder it just gets a permissions error instead of actually mutating something.
Hope that helps!