# Triggering nextflow pipeline using API call
**URL:** https://community.seqera.io/t/triggering-nextflow-pipeline-using-api-call/2107
**Category:** Ask for help
**Tags:** nextflow, aws, tower
**Created:** [May 5, 2025, 4:28am UTC](https://community.seqera.io/t/triggering-nextflow-pipeline-using-api-call/2107 "2025-05-05T04:28:29Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@Fury\_Gaming](https://community.seqera.io/u/Fury_Gaming)
#### Post date: [May 5, 2025, 4:28am UTC](https://community.seqera.io/t/triggering-nextflow-pipeline-using-api-call/2107/1 "2025-05-05T04:28:29Z")
Hi all, I’m new to Nextflow. I’d like to explore how to host a Nextflow pipeline, trigger it using API calls, retrieve the results, and display them on a frontend.
---
### Author:  [@ewels](https://community.seqera.io/u/ewels)
#### Post date: [May 5, 2025, 5:30am UTC](https://community.seqera.io/t/triggering-nextflow-pipeline-using-api-call/2107/2 "2025-05-05T05:30:49Z")
Hi @Fury_Gaming,
There are many ways to do this, but the obvious one is to use Seqera Platform. The entire platform can be used via its API, which in turn can control and report on your Nextflow runs:
> **[Automation | Seqera Docs](https://docs.seqera.io/platform-cloud/getting-started/quickstart-demo/automation)**
>
> An introduction to automation with APIs and CLI tools in Seqera Platform
If you have any more specifics about your setup or how you’d like it to work, I’d be happy to offer some suggestions.
Phil
---
### Author:  [@Fury\_Gaming](https://community.seqera.io/u/Fury_Gaming)
#### Post date: [May 5, 2025, 6:13am UTC](https://community.seqera.io/t/triggering-nextflow-pipeline-using-api-call/2107/3 "2025-05-05T06:13:06Z")
I’m concerned that sharing a Git link to my pipeline could expose my code and potentially lead to security risks. I’d like to understand the implications of this and how to safeguard my pipeline appropriately.
---
### Author:  [@Adam\_Talbot](https://community.seqera.io/u/Adam_Talbot)
#### Post date: [May 12, 2025, 8:55am UTC](https://community.seqera.io/t/triggering-nextflow-pipeline-using-api-call/2107/4 "2025-05-12T08:55:08Z")
> I’m concerned that sharing a Git link to my pipeline could expose my code and potentially lead to security risks. I’d like to understand the implications of this and how to safeguard my pipeline appropriately.
If your code is stored in a private Git repository and access is granted only to the necessary services or collaborators, it should be as secure as possible. It is important **not to include sensitive information** , such as passwords or patient data, in your codebase. This ensures such data is never committed to the repository and significantly reduces the risk of exposure. Private repositories are free on GitHub, and if your organization uses a paid Git hosting service or hosts its own, those platforms also support secure code management.
While tools like Git can seem intimidating at first, they are widely used across the software industry to manage even the most secure codebases. I assure you it is safe when used properly and is a highly valuable skill to develop.
Regarding the Seqera Platform mentioned by @ewels, it pulls specific metadata from your Git repository, but the actual reading and execution of your full codebase happens only on your own computing infrastructure. This makes it more secure by design.