CircleCI is a continuous integration and delivery platform that automates build, test, and deployment pipelines for software development.
CircleCI is a continuous integration and delivery platform that automates build, test, and deployment pipelines for software development. On Nagent, CircleCI is exposed as a fully-configurable developer tools integration that any agent can call — 65 actions, and API key authentication. No code is required to wire CircleCI into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use CircleCI 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 CircleCI 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 CircleCI, with input parameters and output schema. Drop these into any step of an agent built in Helix.
CIRCLECI_CREATE_CONTEXTTool to create a new context in CircleCI. Contexts are used to secure and share environment variables across projects. Use this when you need to set up a new environment configuration for your CircleCI workflows.
Input parameters
The user-defined name of the context. This name must be unique within the owner scope.
Owner information specifying who owns this context (organization or account).
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
CIRCLECI_CREATE_CONTEXT_GRAPHQLTool to create a new CircleCI context using the GraphQL API. Use when you need to create a context for storing environment variables in CircleCI. The mutation returns error information if creation fails or payload data if successful.
Input parameters
The unique ID of the owner organization (UUID format).
The type of owner - must be ORGANIZATION.
The name of the context to create.
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
CIRCLECI_CREATE_CONTEXT_RESTRICTIONTool to create a context restriction in CircleCI. Use when you need to limit context access based on project, expression rules, or group membership.
Input parameters
An opaque identifier of a context.
Type of the restriction. Use 'project' to restrict by project UUID, 'expression' to restrict by expression rule (e.g., branch conditions), or 'group' to restrict by group.
Value used to evaluate the restriction. If the restriction_type is 'project', this will be the project UUID. If the restriction_type is 'expression', this will be the expression rule (e.g., 'pipeline.git.branch == "main"').
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
CIRCLECI_CREATE_ORGANIZATION_ORB_ALLOWLISTTool to create a new URL Orb allow-list entry for an organization. Use when you need to allow URL-based orb references from specific URL prefixes in CircleCI pipelines for an organization.
Input parameters
An authentication method to use for fetching URL orb references that match this allow-list entry's prefix.
Name of the URL orb allow-list entry.
URL prefix. URL orb references that start with this prefix will be allowed by this allow-list entry.
Org UUID or slug in the form `vcs-slug/org-name`. For projects that use GitLab or GitHub App, use `circleci` as the `vcs-slug` and replace the `org-name` with the organization ID (found in Organization Settings).
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
CIRCLECI_CREATE_ORGANIZATION_PROJECTTool to create a new project within a CircleCI organization. Use when you need to programmatically set up a new project for CI/CD automation.
Input parameters
The name of the project to create.
Org UUID or slug in the form `vcs-slug/org-name`. For projects that use GitLab or GitHub App, use `circleci` as the `vcs-slug` and replace the `org-name` with the organization ID (found in Organization Settings).
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
CIRCLECI_CREATE_ORG_GROUPTool to create a group in an organization. Use when you need to organize users within a CircleCI organization by creating logical groups.
Input parameters
Name of the group.
An opaque identifier of an organization.
Description to describe the group.
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
CIRCLECI_CREATE_PROJECT_ENV_VARTool to create a new environment variable for a CircleCI project. Use when you need to add a new environment variable that will be available in project builds.
Input parameters
The name of the environment variable to create.
The value of the environment variable.
Project slug in the form `vcs-slug/org-name/repo-name`. The `/` characters may be URL-escaped. For projects that use GitLab or GitHub App, use `circleci` as the `vcs-slug`, replace `org-name` with the organization ID (found in Organization Settings), and replace `repo-name` with the project ID (found in Project Settings).
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
CIRCLECI_CREATE_USAGE_EXPORT_JOBTool to create a usage export job for a CircleCI organization. Use when you need to export usage data for billing, analysis, or reporting purposes. Rate limited to 10 queries per hour. Maximum date window is 32 days, with up to 13 months of historical data available.
Input parameters
End date for the usage export in ISO 8601 format (e.g., '2026-02-07T23:59:59Z'). Maximum date window is 32 days between start and end.
Start date for the usage export in ISO 8601 format (e.g., '2026-02-01T00:00:00Z'). Maximum date window is 32 days between start and end.
Organization ID (UUID) to create the usage export for.
Array of organization IDs to include in shared context. Use this to include usage data from related 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
CIRCLECI_DELETE_CONTEXT_GRAPHQLTool to delete a CircleCI context by its UUID using GraphQL API. Use when you need to permanently remove a context from your CircleCI organization. This action is irreversible and will delete all environment variables associated with the context.
Input parameters
The UUID of the context to delete.
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
CIRCLECI_DELETE_CONTEXT_RESTRICTIONTool to delete a context restriction by its ID. Use when you need to remove a specific restriction from a CircleCI context.
Input parameters
An opaque identifier of a context.
An opaque identifier of a context restriction.
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
CIRCLECI_DELETE_NAMESPACETool to delete a CircleCI registry namespace and all its associated orbs. Use when you need to permanently remove a namespace from the registry. This is a destructive operation that cannot be undone.
Input parameters
The UUID identifier of the namespace to delete. This will delete the namespace and all associated orbs.
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
CIRCLECI_DELETE_NAMESPACE_ALIASTool to remove a namespace alias by name in CircleCI. Use when you need to delete an existing namespace alias that is no longer needed. The mutation returns a boolean indicating success and any errors that occurred during deletion.
Input parameters
The name of the namespace alias to delete.
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
CIRCLECI_DELETE_ORGANIZATION_ORB_ALLOWLISTTool to remove an entry from the organization's URL orb allow-list. Use when you need to revoke access to a previously allowed orb URL.
Input parameters
Org UUID or slug in the form `vcs-slug/org-name`. For projects that use GitLab or GitHub App, use `circleci` as the `vcs-slug` and replace the `org-name` with the organization ID (found in Organization Settings).
URL orb allow-list entry UUID.
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
CIRCLECI_DELETE_ORG_GROUPTool to delete a group from a CircleCI organization. Use when you need to remove a group permanently from the organization.
Input parameters
An opaque identifier of an organization.
An opaque identifier of a group.
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
CIRCLECI_DELETE_PROJECTTool to delete a CircleCI project and its settings. Use when you need to permanently remove a project from CircleCI. This action cannot be undone.
Input parameters
Project slug in the form 'vcs-slug/org-name/repo-name'. The '/' characters may be URL-escaped. For projects that use GitLab or GitHub App, use 'circleci' as the 'vcs-slug', replace 'org-name' with the organization ID (found in Organization Settings), and replace 'repo-name' with the project ID (found in Project Settings).
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
CIRCLECI_DELETE_PROJECT_ENV_VARTool to delete an environment variable from a CircleCI project. Use when you need to remove an existing environment variable by name.
Input parameters
The name of the environment variable to delete.
Project slug in the form `vcs-slug/org-name/repo-name`. The `/` characters may be URL-escaped. For projects that use GitLab or GitHub App, use `circleci` as the `vcs-slug`, replace `org-name` with the organization ID (found in Organization Settings), and replace `repo-name` with the project ID (found in Project Settings).
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
CIRCLECI_GET_CONTEXTTool to retrieve a context by its unique ID. Use when you need details about a specific CircleCI context.
Input parameters
An opaque identifier of a 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
CIRCLECI_GET_CURRENT_USERTool to retrieve information about the currently authenticated user. Use when you need details about the signed-in user's profile, permissions, and account settings.
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
CIRCLECI_GET_FLAKY_TESTSTool to get flaky tests for a project. Use when you need to identify tests that passed and failed in the same commit. Branch-agnostic insights help improve test reliability.
Input parameters
The project slug in the form 'vcs-slug/org-name/repo-name' (e.g., 'gh/CircleCI-Public/circleci-cli').
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
CIRCLECI_GET_JOB_ARTIFACTSRetrieves artifacts (output files like test results, logs, build binaries, reports) produced by a CircleCI job. Use this when you need to access files generated during a job's execution, such as test reports, coverage data, compiled binaries, or deployment artifacts. Returns download URLs for each artifact. Note: Jobs may produce zero artifacts if none were explicitly stored using 'store_artifacts' in the config.
Input parameters
The number of the job to list artifacts for.
Token to retrieve the next page of results. Obtain this from the 'next_page_token' field in a previous response.
The project slug in the form of 'vcs-slug/org-name/repo-name', e.g., 'gh/CircleCI-Public/api-preview-docs'.
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
CIRCLECI_GET_JOB_DETAILSTool to fetch details of a specific job within a project. Use when you need status, timing, and executor information for a CircleCI job by its number.
Input parameters
The number of the job to fetch details for.
The project slug in the form 'vcs-slug/org-name/repo-name', e.g., 'gh/CircleCI-Public/api-preview-docs'.
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
CIRCLECI_GET_ORB_DETAILSTool to query detailed information about a CircleCI orb using the GraphQL API. Use when you need to retrieve orb metadata, versions, usage statistics, or namespace details.
Input parameters
The orb reference in format 'namespace/orbname'. Use this to query public orbs like 'circleci/node' or 'circleci/python'.
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
CIRCLECI_GET_ORB_VERSIONTool to retrieve detailed information about a specific CircleCI orb version via GraphQL. Use when you need orb source code, version history, usage statistics, or metadata for a specific orb version.
Input parameters
The orb reference including version information. Format: 'namespace/orb-name@version' (e.g., 'circleci/node@5.0.0'). The namespace identifies the orb publisher, orb-name is the orb identifier, and version is the specific version to query.
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
CIRCLECI_GET_ORGANIZATIONTool to retrieve organization details from CircleCI using GraphQL query. Use when you need organization information by ID or by name and VCS type.
Input parameters
The unique UUID of the organization. Either org_id OR both org_name and vcs_type must be provided.
The name of the organization. Must be provided together with vcs_type if org_id is not provided.
The version control system type. Must be provided together with org_name if org_id is not provided. Common values: GITHUB, BITBUCKET.
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
CIRCLECI_GET_ORGANIZATION_GROUPTool to retrieve a group in an organization. Use when you need to get details about a specific group within a CircleCI organization.
Input parameters
An opaque identifier of an organization.
An opaque identifier of a group.
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
CIRCLECI_GET_PIPELINE_CONFIGTool to fetch pipeline configuration by ID. Use when you need the source or compiled YAML of a specific pipeline.
Input parameters
The unique ID of the pipeline to fetch configuration for.
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
CIRCLECI_GET_PIPELINE_DEFINITIONTool to retrieve a pipeline definition by project and definition ID. Use when you need details about a specific pipeline definition's configuration, sources, and metadata.
Input parameters
An opaque identifier of a project.
An opaque identifier of a pipeline definition.
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
CIRCLECI_GET_PROJECTTool to retrieve a CircleCI project by its slug. Use when you need project details such as organization info, project ID, or VCS configuration.
Input parameters
Project slug in the form `vcs-slug/org-name/repo-name` (e.g., `gh/CircleCI-Public/circleci-cli`). The `/` characters may be URL-escaped.
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
CIRCLECI_GET_PROJECT_WORKFLOWSTool to get summary metrics for all workflows of a project. Use when you need to analyze performance across all workflows, including success rates, duration metrics, throughput, and credits used.
Input parameters
The name of a vcs branch. If not passed we will scope the API call to the default branch.
Token to retrieve the next page of results (for pagination).
Whether to retrieve data for all branches combined. Use either this parameter OR the branch name parameter.
Project slug in the form `vcs-slug/org-name/repo-name`. The `/` characters may be URL-escaped. For projects that use GitLab or GitHub App, use `circleci` as the `vcs-slug`, replace `org-name` with the organization ID (found in Organization Settings), and replace `repo-name` with the project ID (found in Project Settings).
The time window for the report. Specifies the reporting window for data aggregation.
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
CIRCLECI_GET_TEST_METADATATool to fetch test metadata for a specific job. Use when you need detailed test results, run times, and failure messages after a job completes.
Input parameters
Maximum number of test results to return. Defaults to 30.
The number of the job to fetch test metadata for.
A token to retrieve the next page of results.
The project slug in the form 'vcs-slug/org-name/repo-name', e.g., 'gh/CircleCI-Public/circleci-cli'.
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
CIRCLECI_GET_USAGE_EXPORT_JOBTool to retrieve a usage export job by organization ID and job ID. Use when you need to check the status or download URLs of a usage export job.
Input parameters
An opaque identifier of an organization.
An opaque identifier of a usage export job.
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
CIRCLECI_GET_USER_INFORMATIONTool to retrieve information about a CircleCI user by their unique ID. Use when you need user profile details after obtaining the user ID.
Input parameters
The unique ID of the user.
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
CIRCLECI_GET_WORKFLOW_SUMMARYTool to get metrics and trends for a workflow. Use when you need workflow performance insights including success rates, duration metrics, and trends over time.
Input parameters
The name of a vcs branch. If not passed we will scope the API call to the default branch.
Whether to retrieve data for all branches combined. Use either this parameter OR the branch name parameter.
Project slug in the form `vcs-slug/org-name/repo-name`. The `/` characters may be URL-escaped. For projects that use GitLab or GitHub App, use `circleci` as the `vcs-slug`, replace `org-name` with the organization ID (found in Organization Settings), and replace `repo-name` with the project ID (found in Project Settings).
The name of the workflow.
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
CIRCLECI_LIST_CONTEXT_ENV_VARSTool to list all environment variables for a specific context. Use when you need to retrieve or paginate through environment variables stored in a CircleCI context.
Input parameters
An opaque identifier of a context.
A token to specify which page of results to fetch.
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
CIRCLECI_LIST_INSIGHTS_BRANCHESTool to get all branches for a project from CircleCI Insights. Use when you need to retrieve the list of branches that have workflow runs in the project.
Input parameters
Project slug in the form `vcs-slug/org-name/repo-name`. The `/` characters may be URL-escaped. For projects that use GitLab or GitHub App, use `circleci` as the `vcs-slug`, replace `org-name` with the organization ID (found in Organization Settings), and replace `repo-name` with the project ID (found in Project Settings).
The name of a workflow. If not passed we will scope the API call to the project.
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
CIRCLECI_LIST_INSIGHTS_SUMMARYTool to get summary metrics with trends for the entire organization and for each project. Use when you need organization-wide performance analytics across all projects.
Input parameters
Organization slug in the form `vcs-type/org-name`. Example: `gh/CircleCI-Public` or `bb/my-org`.
Filter by project names. Can be a single project name or multiple project names.
Reporting window for summary metrics.
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
CIRCLECI_LIST_NAMESPACE_ORBSTool to list orbs in a CircleCI registry namespace with pagination support. Use when you need to browse available orbs in a namespace, filter by visibility (public/private), or retrieve orb statistics. Returns up to 20 orbs per page with cursor-based pagination.
Input parameters
Enum for orb visibility filter types.
Pagination cursor for fetching subsequent pages. Use empty string for the first page, then use the cursor value from previous response's edges.
The registry namespace name to query (e.g., 'circleci', 'myorg'). If not provided, queries all accessible namespaces.
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
CIRCLECI_LIST_ORB_CATEGORIESTool to retrieve all CircleCI orb categories with pagination support. Use when you need to list available categories for orb classification. Returns up to 20 categories per page with cursor-based pagination.
Input parameters
Pagination cursor for fetching subsequent result pages. Use empty string for first page.
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
CIRCLECI_LIST_ORBSTool to list CircleCI orbs with pagination support via GraphQL API. Use when you need to browse available orbs, filter by certification status, or discover orbs with their usage statistics. Returns up to 20 orbs per page with cursor-based pagination.
Input parameters
Cursor for pagination. Use empty string for the first page, then use the cursor from the previous response to get the next page.
Filter for certified orbs only (true) or include all orbs (false). Certified orbs are officially verified by CircleCI.
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
CIRCLECI_LIST_ORGANIZATION_GROUPSTool to list all groups in a CircleCI organization. Use when you need to retrieve groups for an organization to manage permissions or view group memberships.
Input parameters
The number of results per page.
An opaque identifier of an organization.
A token to specify which page of results to fetch.
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
CIRCLECI_LIST_PAGES_SUMMARYTool to get summary metrics and trends for a project across its workflows and branches. Use when you need to analyze project performance, track success rates, throughput, credits usage, and duration trends.
Input parameters
The names of VCS branches to include in branch-level workflow metrics.
Project slug in the form `vcs-slug/org-name/repo-name`. The `/` characters may be URL-escaped. For projects that use GitLab or GitHub App, use `circleci` as the `vcs-slug`, replace `org-name` with the organization ID (found in Organization Settings), and replace `repo-name` with the project ID (found in Project Settings).
The names of workflows to include in workflow-level metrics.
Reporting window for summary metrics.
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
CIRCLECI_LIST_PIPELINE_DEFINITIONSTool to list all pipeline definitions for a specific project. Use when you need to retrieve available pipeline configurations for a project.
Input parameters
A token to retrieve the next page of results.
An opaque identifier of a project.
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
CIRCLECI_LIST_PIPELINESTool to get a list of pipelines for an organization. Use when you need to retrieve pipelines across multiple projects or for a specific organization.
Input parameters
Only include entries created by your user.
Org slug in the form `vcs-slug/org-name`. For projects that use GitLab or GitHub App, use `circleci` as the `vcs-slug` and replace the `org-name` with the organization ID (found in Organization Settings).
A token to retrieve the next page of results.
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
CIRCLECI_LIST_PIPELINES_FOR_PROJECTTool to list all pipelines for a specific project. Use when you need to retrieve the pipelines for a project (e.g., to display recent runs on a dashboard).
Input parameters
Only return pipelines triggered by the current user if true.
Only return pipelines on this branch.
A token to retrieve the next page of results.
The project slug in the form `vcs-slug/org-name/repo-name` (e.g., `github/CircleCI-Public/circleci-cli`).
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
CIRCLECI_LIST_PROJECT_ENV_VARSTool to list all environment variables for a CircleCI project. Use when you need to retrieve project-level environment variables. Note that values are masked for security.
Input parameters
Token to fetch the next page of results.
Project slug in the form 'vcs-slug/org-name/repo-name'. The vcs-slug should be 'gh' (GitHub) or 'bb' (Bitbucket). Example: 'gh/CircleCI-Public/api-preview-docs'.
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
CIRCLECI_LIST_PROJECT_SCHEDULESTool to list all schedules for a specific project. Use when you need to retrieve scheduled pipeline triggers for a project.
Input parameters
A token to retrieve the next page of results.
Project slug in the form `vcs-slug/org-name/repo-name`. The `/` characters may be URL-escaped. For projects that use GitLab or GitHub App, use `circleci` as the `vcs-slug`, replace `org-name` with the organization ID (found in Organization Settings), and replace `repo-name` with the project ID (found in Project Settings).
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
CIRCLECI_LIST_SELF_HOSTED_RUNNERSList self-hosted runners in CircleCI. Use this to retrieve information about your organization's self-hosted runners, optionally filtered by namespace or resource class. Useful for monitoring runner availability and status.
Input parameters
Filter runners by namespace (e.g., 'my-namespace'). Returns all runners in the specified namespace. Must provide either this or resource_class (but not both).
Filter runners by specific resource class (e.g., 'my-namespace/my-resource-class'). Returns only runners for this resource class. Must provide either this or namespace (but not both).
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
CIRCLECI_LIST_USER_COLLABORATIONSTool to retrieve organizations where the authenticated user has access. Use when you need to list all organizations a user can collaborate on.
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
CIRCLECI_LIST_WORKFLOWS_BY_PIPELINE_IDTool to list all workflows associated with a specific pipeline. Use when you need to fetch or paginate through workflows by pipeline ID.
Input parameters
Maximum number of workflows to return. Default is 20, maximum is 100.
Token to retrieve the next page of results (for pagination).
The unique identifier of the pipeline.
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
CIRCLECI_LIST_WORKFLOWS_JOBS_WORKFLOWSTool to get summary metrics for a project workflow's jobs. Use when you need performance analytics like success rates, duration statistics, and credit usage for jobs in a specific workflow.
Input parameters
The name of a vcs branch. If not passed we will scope the API call to the default branch.
The name of the jobs you would like to filter from your workflow. If not specified, all workflow jobs will be returned. The job name can either be the full job name or just a substring of the job name.
A token to retrieve the next page of results.
Whether to retrieve data for all branches combined. Use either this parameter OR the branch name parameter.
Project slug in the form `vcs-slug/org-name/repo-name`. The `/` characters may be URL-escaped. For projects that use GitLab or GitHub App, use `circleci` as the `vcs-slug`, replace `org-name` with the organization ID (found in Organization Settings), and replace `repo-name` with the project ID (found in Project Settings).
The name of the workflow.
Time window for calculating summary metrics.
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
CIRCLECI_LIST_WORKFLOWS_TEST_METRICSTool to get test metrics for a project's workflows. Use when you need to analyze test performance, identify flaky tests, or find the slowest tests in a workflow.
Input parameters
The name of a vcs branch. If not passed we will scope the API call to the default branch.
Whether to retrieve data for all branches combined. Use either this parameter OR the branch name parameter.
Project slug in the form `vcs-slug/org-name/repo-name`. The `/` characters may be URL-escaped. For projects that use GitLab or GitHub App, use `circleci` as the `vcs-slug`, replace `org-name` with the organization ID (found in Organization Settings), and replace `repo-name` with the project ID (found in Project Settings).
The name of the workflow.
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
CIRCLECI_QUERY_CONTEXTTool to retrieve a CircleCI context by its UUID using GraphQL API. Use when you need to fetch context details including ID, name, and creation time. Returns null in the data field if the context ID does not exist.
Input parameters
The UUID of the context to query.
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
CIRCLECI_QUERY_NAMESPACE_EXISTSTool to determine if a namespace exists in the CircleCI registry. Use when you need to verify namespace existence before performing operations. Returns a boolean indicating whether the namespace exists.
Input parameters
The namespace name to check existence for (e.g., 'circleci', 'myorg').
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
CIRCLECI_QUERY_ORB_CATEGORY_IDTool to fetch the unique category ID for a CircleCI orb category by its name. Use when you need to categorize orbs or query category-specific information. Returns null in the data field if the category name does not exist.
Input parameters
The name of the orb category to query (e.g., Deployment, Testing, Security, Notifications).
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
CIRCLECI_QUERY_ORB_EXISTSTool to check if an orb exists in CircleCI registry and retrieve its privacy status. Use when you need to verify orb existence or check if an orb is private/public. Returns null in the data.orb field if the orb does not exist.
Input parameters
Full orb name in format 'namespace/orb' (e.g., 'circleci/node').
Optional namespace name to verify its existence alongside the orb.
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
CIRCLECI_QUERY_ORB_IDTool to fetch an orb's ID and optionally its namespace ID by orb name. Use when you need to query orb identifiers for CircleCI orbs. The name parameter should be the full orb reference (namespace/orbname). Optionally provide the namespace parameter to also retrieve the namespace ID in the same call.
Input parameters
Full orb reference in format namespace/orbname (e.g., 'circleci/node', 'myorg/myorb').
Namespace name to query the namespace ID (e.g., 'circleci', 'myorg'). Optional but recommended to get both orb and namespace IDs in one call.
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
CIRCLECI_QUERY_ORB_LATEST_VERSIONTool to fetch the latest published version of a CircleCI orb. Use when you need to check the most recent version number of an orb for dependency management or updates. Returns null in the data field if the orb does not exist.
Input parameters
The orb reference in format 'namespace/orbname' (e.g., 'circleci/node', 'circleci/aws-cli').
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
CIRCLECI_QUERY_ORB_SOURCETool to retrieve source code of a specific CircleCI orb version via GraphQL. Use when you need to access the YAML configuration or inspect the implementation of an orb version. Returns null if the orb version reference does not exist.
Input parameters
The orb reference including version information. Format: 'namespace/orb-name@version' (e.g., 'circleci/node@5.0.0'). The namespace identifies the orb publisher, orb-name is the orb identifier, and version is the specific version to retrieve source for.
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
CIRCLECI_QUERY_PLAN_METRICSTool to query plan metrics including credit usage by project and organization for a date range. Use when you need to analyze credit consumption, compute time usage, or project-level metrics for an organization.
Input parameters
The unique UUID of the organization to query plan metrics for.
Date range to filter metrics. Specify start and end dates in ISO 8601 format (YYYY-MM-DD).
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
CIRCLECI_REMOVE_CONTEXT_ENV_VAR_GRAPHQLTool to remove an environment variable from a CircleCI context using GraphQL API. Use when you need to delete a context-level environment variable by its name.
Input parameters
The name of the environment variable to remove from the context.
The UUID of the context containing the environment variable to delete.
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
CIRCLECI_RENAME_NAMESPACETool to rename a CircleCI namespace by its UUID identifier. Use when you need to change the name of an existing namespace. Returns the renamed namespace ID on success, or errors if the operation fails.
Input parameters
The new name for the namespace.
The unique identifier (UUID) of the namespace to rename.
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
CIRCLECI_STORE_ENVIRONMENT_VARIABLETool to store an environment variable in a CircleCI context using GraphQL mutation. Use when you need to add or update an environment variable within a specific context.
Input parameters
The value of the environment variable to store.
The name of the environment variable to store.
The UUID of the context to store the environment variable in.
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
CIRCLECI_TRIGGER_PIPELINETriggers a new CI/CD pipeline run for a specified CircleCI project. Use this tool to programmatically start a build on a specific branch or tag, optionally passing custom pipeline parameters for conditional workflow execution. Requires write access to the project.
Input parameters
The git tag to trigger the pipeline on. Use this to trigger builds for tagged releases. Cannot be used together with 'branch'.
The branch name to trigger the pipeline on. If not specified, triggers on the project's default branch. Cannot be used together with 'tag'.
Pipeline parameters as key-value pairs to pass to the CircleCI config. These parameters must be declared in your .circleci/config.yml file. Useful for conditional workflow execution or dynamic configuration.
Project identifier in the format 'vcs-slug/org-name/repo-name'. The vcs-slug should be 'gh' (GitHub) or 'bb' (Bitbucket). Example: 'gh/my-org/my-repo' for a GitHub project.
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
CIRCLECI_UPSERT_CONTEXT_ENV_VARTool to add or update an environment variable in a CircleCI context. Use when you need to set or modify context-level environment variables for your CircleCI projects.
Input parameters
The value of the environment variable.
An opaque identifier of a context.
The name of the environment variable.
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
CIRCLECI_VALIDATE_ORB_CONFIGTool to validate CircleCI orb YAML configuration using the orbConfig GraphQL query. Use when you need to verify that an orb definition is syntactically correct before publishing or using it. Returns validation status, any errors found, and the processed YAML output.
Input parameters
The YAML configuration of the orb to validate. Must be a valid YAML string containing orb definition with version, description, commands, jobs, or executors.
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 52 agents privately built on Nagent that already use CircleCI.
Build on Nagent
Connect CircleCI 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 CircleCI, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, CircleCI is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once CircleCI is connected, you configure its 65 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop CircleCI 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 CircleCI event fires, the agent kicks off automatically.
Every CircleCI 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 CircleCI ships with 65 pre-built developer tools actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching CircleCI together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build CircleCI-based workflows tailored to your business.