# Connecting / Chaining existing Nextflow workflows in a meta workflow **URL:** \ **Category:** Tips & Tricks\ **Tags:** nextflow\ **Created:** [July 17, 2024, 8:08am UTC](https://community.seqera.io/t/connecting-chaining-existing-nextflow-workflows-in-a-meta-workflow/969 "2024-07-17T08:08:13Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![mahesh.binzerpanchal](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/mahesh.binzerpanchal/32/253_2.png) [@mahesh.binzerpanchal](https://community.seqera.io/u/mahesh.binzerpanchal)\ **Post date:** [July 17, 2024, 8:08am UTC](https://community.seqera.io/t/connecting-chaining-existing-nextflow-workflows-in-a-meta-workflow/969/1 "2024-07-17T08:08:13Z")
nf-core and the wider Nextflow community have written some amazing workflows. Occasionally, users ask if there’s a way to daisy-chain existing Nextflow workflows together in a single workflow. One way to go about it is to use a native process in Nextflow to run each workflow as it’s own process, using channels to connect the outputs and inputs of the workflows. [GitHub - mahesh-panchal/nf-cascade: A proof of concept daisy-chaining Nextflow workflows](https://github.com/mahesh-panchal/nf-cascade/) is one implementation of how to do so. This example chains together nf-core/fetchngs into both nf-core/taxprofiler and nf-core/mag, and then nf-core/mag into nf-core/funcscan. ---
**Author:** ![mbc](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/mbc/32/742_2.png) [@mbc](https://community.seqera.io/u/mbc)\ **Post date:** [July 25, 2024, 11:06am UTC](https://community.seqera.io/t/connecting-chaining-existing-nextflow-workflows-in-a-meta-workflow/969/2 "2024-07-25T11:06:14Z")
This looks very interesting, we have the same problem in our team. We are using prefect to orchestrate our workloads ( nextflow + other kind of jobs ). I will give this a try, thanks!