Seqera Platform is an intuitive, centralized command post that enables data analysis at scale, allowing users to launch, manage, and monitor scalable Nextflow pipelines and compute environments on-premises or across cloud providers.
Seqera Platform is an intuitive, centralized command post that enables data analysis at scale, allowing users to launch, manage, and monitor scalable Nextflow pipelines and compute environments on-premises or across cloud providers. On Nagent, Seqera is exposed as a fully-configurable developer tools integration that any agent can call — 14 actions, and API key authentication. No code is required to wire Seqera into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Seqera to automate the kinds of tasks developer tools teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Seqera into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Seqera, with input parameters and output schema. Drop these into any step of an agent built in Helix.
SEQERA_CREATE_WAVE_CONTAINERTool to submit a request to Wave for accessing a private container registry or building a container image on-the-fly. Use when you need to provision containers via Wave with Dockerfile, Conda recipe, or package specifications. Returns the name of the container made available by Wave.
Input parameters
If true, pushes the container to user-defined repository with a permanent URL (prevents expiration)
Specification for Conda or CRAN packages.
Base64-encoded Conda environment YAML file for building a container
Enum for container name strategies.
Base64-encoded Dockerfile content for building a new container. Required if containerImage and packages are not provided.
Name of the container to be served (e.g., 'docker.io/library/ubuntu:latest'). Required if containerFile and packages are not provided.
Container repository where container builds should be pushed
Container repository used to cache build layers
Configuration for container customization.
Seqera Platform access token for authentication
Seqera Platform workspace ID for retrieving credentials
Enum for container platform architectures.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SEQERA_GET_ORGANIZATION_DETAILSTool to retrieve detailed information about a specific organization.
Input parameters
The unique identifier of the organization (numeric ID)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SEQERA_GET_SERVICE_INFOTool to retrieve information about the Seqera API service. Use when you need to check the service version and commit ID for troubleshooting.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SEQERA_GET_USER_INFOTool to retrieve information about the authenticated user. Use when you need to fetch details of the current user after authentication.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SEQERA_GET_WAVE_BUILD_LOGSTool to get logs for a container build by build ID. Use when you need to troubleshoot or inspect the build process of a Wave container.
Input parameters
Build identifier for the container build whose logs are to be retrieved
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SEQERA_GET_WAVE_BUILD_STATUSTool to retrieve the status of a Wave container build by build ID. Use when you need to check if a container build is completed and whether it succeeded.
Input parameters
Build identifier returned from Wave container build request
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SEQERA_INSPECT_WAVE_CONTAINERTool to inspect container image metadata via Wave. Use when you need registry, manifest, digest, configuration, and OCI compatibility information about a container image.
Input parameters
Seqera Platform endpoint URL (default: https://api.cloud.seqera.io)
Name of the container to inspect (e.g., docker.io/library/ubuntu:latest)
Seqera Platform access token for private registries
Seqera Platform workspace ID
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SEQERA_LIST_ACTION_EVENT_TYPESTool to list supported action event types. Use when you need to discover available triggers for pipelines, optionally filtered by workspace.
Input parameters
Optional workspace ID to filter action types by a specific workspace
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SEQERA_LIST_COMPUTE_ENVIRONMENTSTool to retrieve a list of compute environments. Use when you need to page, sort, or filter compute environments accessible to your account.
Input parameters
Filter by compute environment status (e.g., 'AVAILABLE', 'CREATING', 'INVALID').
Workspace identifier. If omitted, defaults to user context.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SEQERA_LIST_ORGANIZATIONSTool to list all organizations. Use after authentication to retrieve accessible Seqera organizations.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SEQERA_LIST_PIPELINESTool to list all pipelines accessible to the authenticated user. Use when you need to browse pipelines with optional pagination, sorting, or search filters.
Input parameters
Page number for pagination (must be ≥ 1)
Search term to filter pipelines by name or description
Field to sort by, e.g., 'createdAt' or 'name'
Number of items per page (1–100)
Sort direction: 'asc' or 'desc'
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SEQERA_LIST_WORKFLOWSTool to list workflows. Use when you need to retrieve workflows filtered by workspace and paginated.
Input parameters
Maximum number of workflows to return (pagination size)
Pagination token to retrieve the next set of results
ID of the workspace to filter workflows
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SEQERA_VALIDATE_ACTION_NAMETool to validate action name. Use when you need to confirm if an action name is valid and available before creating an action. Returns validation status with details.
Input parameters
Action name to validate. The API will check if this name is valid and available.
Workspace numeric identifier to validate the action name within a specific workspace context
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SEQERA_VALIDATE_PIPELINE_NAMETool to validate a pipeline name. Use when you need to check if a given pipeline name is valid and available before creating or updating one.
Input parameters
Pipeline name to validate. If omitted, validates without a specific name.
Organization numeric identifier. If provided, validates the name in an organization context.
Workspace numeric identifier. If provided, validates the name in a workspace context. If omitted, validates in the default user context.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 95 agents privately built on Nagent that already use Seqera.
Build on Nagent
Connect Seqera to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Seqera, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Seqera is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Seqera is connected, you configure its 14 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Seqera steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Seqera event fires, the agent kicks off automatically.
Every Seqera action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Seqera ships with 14 pre-built developer tools actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Seqera together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Seqera-based workflows tailored to your business.