AppVeyor is a hosted continuous integration service for building and deploying applications.
AppVeyor is a hosted continuous integration service for building and deploying applications. On Nagent, Appveyor 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 Appveyor into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Appveyor 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 Appveyor 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 Appveyor, with input parameters and output schema. Drop these into any step of an agent built in Helix.
APPVEYOR_DELETE_BUILDTool to delete a build by ID. Use when you need to remove a build from AppVeyor. The API returns 204 No Content on successful deletion.
Input parameters
The ID of the build 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
APPVEYOR_DOWNLOAD_BUILD_LOGTool to download the build log for a specific job. Use when you need to retrieve the log output from a completed or running build job.
Input parameters
Build job ID (`jobId` property of `BuildJob`)
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
APPVEYOR_GET_BUILD_ARTIFACTSTool to get the list of artifacts for a specific build job. Use when you need to retrieve artifacts after a job completes.
Input parameters
The ID of the build job to retrieve artifacts from.
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
APPVEYOR_GET_BUILD_BY_VERSIONTool to get a specific project build by version number. Use when you need to retrieve detailed information about a build using its version identifier.
Input parameters
AppVeyor account name on which to operate. Accounts for which a user has access are listed on the Security page of the user profile (when logged in). The user account is also the accountName property of UserAccount.
Project slug (URL-friendly identifier for the project).
Build version (version property of Build, e.g., '1.0.233').
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
APPVEYOR_GET_ENVIRONMENTSTool to get a list of all deployment environments. Use when you need to enumerate available environments before creating deployments.
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
APPVEYOR_GET_PROJECT_BRANCH_STATUS_BADGETool to get a project branch status badge image. Returns a PNG or SVG badge image showing the build status for a specific project branch.
Input parameters
Return an SVG image instead of PNG? Exclusive with retina.
Return a larger image suitable for retina displays? Exclusive with svg.
Build branch name (e.g., 'master', 'develop').
Text to show in badge when build is failing.
Text to show in badge when build is passing.
Text to show in badge when build is pending.
ID of the status badge (statusBadgeId from ProjectWithConfiguration).
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
APPVEYOR_GET_PROJECTSTool to get a list of all projects for the authenticated account. Use after authentication to enumerate available projects.
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
APPVEYOR_GET_PROJECT_STATUS_BADGETool to get project status badge image. Use when you need to retrieve the status badge for displaying project build status.
Input parameters
Return an SVG image instead of PNG? Exclusive with retina.
Return a larger image suitable for retina displays? Exclusive with svg.
Text to show in badge when build is failing.
Text to show in badge when build is passing.
Text to show in badge when build is pending.
ID of the status badge (statusBadgeId from ProjectWithConfiguration).
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
APPVEYOR_GET_PUBLIC_PROJECT_STATUS_BADGETool to get status badge image for a project with a public repository. Use when you need to retrieve a build status badge for display or documentation purposes.
Input parameters
Return an SVG image instead of PNG? Exclusive with 'retina'
Repository branch to get badge for
Return a larger image suitable for retina displays? Exclusive with 'svg'
Slug (URL component) of repository
Text to show in badge when build is failing
Text to show in badge when build is passing
Text to show in badge when build is pending
Account name with repository provider
Repository provider supported for badges
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
APPVEYOR_GET_ROLETool to retrieve details of a specific role. Use when you need to inspect permissions and metadata of a role by ID.
Input parameters
Unique identifier of the role to retrieve.
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
APPVEYOR_GET_ROLESTool to retrieve all roles in the account. Use when you need to enumerate available roles before assigning permissions.
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
APPVEYOR_GET_USER_INVITATIONSTool to retrieve all pending user invitations in the account. Use when you need to list all outstanding invitations sent to potential team members.
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
APPVEYOR_GET_USERSTool to retrieve all users in the account. Use when you need to list all team users in your AppVeyor 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
APPVEYOR_LIST_COLLABORATORSTool to retrieve all collaborators in the account. Use when you need to list all team collaborators in your AppVeyor 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
No publicly available marketplace agent is found using this tool yet. There are 96 agents privately built on Nagent that already use Appveyor.
Build on Nagent
Connect Appveyor 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 Appveyor, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Appveyor is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Appveyor 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 Appveyor 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 Appveyor event fires, the agent kicks off automatically.
Every Appveyor 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 Appveyor 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 Appveyor together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Appveyor-based workflows tailored to your business.