Is this possible? I accidentally built 2 blocks in the wrong workflow, and I'm having to re-build them manually.
3 Likes
Hi @henrymeiklejohn, this is not possible. But if they are Resource queries, you could save them on the Query Library and import them from any Workflow. This is useful when the same query is needed in multiple Workflows. 
I didn't see the option to save a query to the library from a workflow though. Is that possible? I know how to do that from an app.
I didn't have the foresight to create the queries outside of my workflow, but if saving them from a workflow is possible that would have solved the issue I had.
Currently, there is not a way to save a query to the QL from a Workflow or App but sounds like a great FR. I went ahead and created it internally. We'll notify you with any updates on this feature. Until then, we do have to recreate them.
Awesome thank you. You can definitely "Extract to Query Library" to save from an app though. Just not from a workflow.
Thank you, I updated the FR!
Want to reference this post on this as well.
Being able to modularize base components of workflows would be a useful step in creating more maintainable workflow code.
As mentioned in the referenced post, I too like to take reusable bits of workflow (ex. a few step process to put meta data about a file into a DB, upload the file to storage, return the URL for that document and update the DB) and then incorporate that base function into other specific contexts as needed.
For example, I might want to process a stored file, which happens to be a spreadsheet of site traffic, into a dashboard for site admins or I might want to process a stored file, which happens to be a picture of a cat, into a collage of random cat images for kicks. Either way, my workflow would basically start the same (upload the file) and then branch from there.
1 Like
I've plus 1'd this topic as I also have the same need, many workflows that use the same blocks, but wouldn't be appropriate to try use the query library for these, and often I want to copy non-resources such as branches, returns and loops.
In case it springs any ideas for the FR, something I'm quite used to in homeassistant is toggling to yaml mode, which makes copying and pasting blocks as yaml text between automations, or from forums etc, trivial:
That demo if anyone's not familiar: Home Assistant Demo
I know retool can do full exports, but I couldn't make much sense of the export data for quick copying/pasting for myself.
Thank you for your feedback! I've added this and your +1 to the internal feature request.
1 Like
Hi, I just wanted to follow up on this.
Zapier has a feature that allows you to copy block(s) and paste them on other workflows, Retool has a 'duplicate' block feature but you can't move them across workflows.
For example, every workflow I have to manually create the same global error handlers.... is there an update on this FR?
Hi @Matthew_Carter,
Thank you for letting us know and checking in on this.
It is on our roadmap but looks like it isn't high on the priorities, I can add another +1 to the ticket for you.
A work around could be that you ca duplicate a workflow, then make changes as needed and call this as a sub-flow of the parent workflow where you would want the blocks to be used.
For example, if you have blocks 1, 2, and 3 but you want to move blocks 2 and 3 into another workflow.
Once you duplicate, you can remove block 1, then in the parent workflow you can call this modified workflow to execute blocks 2 and 3. I know this is a bit more time intensive but it offers a very high degree of flexibility and control!
1 Like
a ctrl-c to ctrl-v option would be amazing between Workflows and multi-step functions 
*Rectangle select and copy multiple even better!
1 Like
Great feedback! Will add that to the ticket for the engineer team.