/appveyor

name: appveyor
description: |
  AppVeyor integration. Manage Projects, Accounts, Users. Use when the user wants to interact with AppVeyor data.
compatibility: Requires network access and a valid Membrane account (Free tier supported).
license: MIT
homepage: https://getmembrane.com
repository: https://github.com/membranedev/application-skills
metadata:
  author: membrane
  version: "1.0"
  categories: ""

AppVeyor

AppVeyor is a continuous integration and continuous delivery (CI/CD) service for Windows and .NET projects. It automates building, testing, and deploying applications. Windows developers and teams use it to streamline their software development lifecycle.

Official docs: https://www.appveyor.com/docs/

AppVeyor Overview

• **Project**
• **Build**
• **Environment Variable**
• **Account**
• **Project**

Use action names and parameters as needed.

Working with AppVeyor

This skill uses the Membrane CLI to interact with AppVeyor. Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic rather than auth plumbing.

Install the CLI

Install the Membrane CLI so you can run `membrane` from the terminal:

npm install -g @membranehq/cli@latest

Authentication

membrane login --tenant --clientName=<agentType>

This will either open a browser for authentication or print an authorization URL to the console, depending on whether interactive mode is available.

**Headless environments:** The command will print an authorization URL. Ask the user to open it in a browser. When they see a code after completing login, finish with:

membrane login complete <code>

Add `--json` to any command for machine-readable JSON output.

**Agent Types** : claude, openclaw, codex, warp, windsurf, etc. Those will be used to adjust tooling to be used best with your harness

Connecting to AppVeyor

Use `membrane connection ensure` to find or create a connection by app URL or domain:

membrane connection ensure "https://www.appveyor.com/" --json

The user completes authentication in the browser. The output contains the new connection id.

This is the fastest way to get a connection. The URL is normalized to a domain and matched against known apps. If no app is found, one is created and a connector is built automatically.

If the returned connection has `state: "READY"`, skip to **Step 2**.

1b. Wait for the connection to be ready

If the connection is in `BUILDING` state, poll until it's ready:

npx @membranehq/cli connection get <id> --wait --json

The `--wait` flag long-polls (up to `--timeout` seconds, default 30) until the state changes. Keep polling until `state` is no longer `BUILDING`.

The resulting state tells you what to do next:

• **`READY`** — connection is fully set up. Skip to **Step 2**.
• **`CLIENT_ACTION_REQUIRED`** — the user or agent needs to do something. The `clientAction` object describes the required action:
• `clientAction.type` — the kind of action needed:
• `"connect"` — user needs to authenticate (OAuth, API key, etc.). This covers initial authentication and re-authentication for disconnected connections.
• `"provide-input"` — more information is needed (e.g. which app to connect to).
• `clientAction.description` — human-readable explanation of what's needed.
• `clientAction.uiUrl` (optional) — URL to a pre-built UI where the user can complete the action. Show this to the user when present.
• `clientAction.agentInstructions` (optional) — instructions for the AI agent on how to proceed programmatically.

After the user completes the action (e.g. authenticates in the browser), poll again with `membrane connection get <id> --json` to check if the state moved to `READY`.

• **`CONFIGURATION_ERROR`** or **`SETUP_FAILED`** — something went wrong. Check the `error` field for details.

Searching for actions

Search using a natural language description of what you want to do:

membrane action list --connectionId=CONNECTION_ID --intent "QUERY" --limit 10 --json

You should always search for actions in the context of a specific connection.

Each result includes `id`, `name`, `description`, `inputSchema` (what parameters the action accepts), and `outputSchema` (what it returns).

Popular actions

| Name | Key | Description | |---|---|---| | List Projects | list-projects | Get all projects in the AppVeyor account | | List Users | list-users | Get all users in the account | | List Environments | list-environments | Get all deployment environments | | List Collaborators | list-collaborators | Get all collaborators in the account | | List Roles | list-roles | Get all roles in the account | | Get Project | get-project | Get a project with its last build information | | Get User | get-user | Get user details by ID | | Get Role | get-role | Get role details by ID | | Get Deployment | get-deployment | Get deployment details by ID | | Get Collaborator | get-collaborator | Get collaborator details by user ID | | Get Project Settings | get-project-settings | Get detailed project settings and configuration | | Get Project History | get-project-history | Get build history for a project | | Start Build | start-build | Start a new build for a project | | Start Deployment | start-deployment | Start a deployment to an environment | | Add Project | add-project | Add a new project from a repository | | Add Collaborator | add-collaborator | Add a collaborator to the account | | Update Project | get-project-settings | Get detailed project settings and configuration | | Delete Project | delete-project | Delete a project | | Delete Build | delete-build | Delete a build by ID | | Delete User | delete-user | Delete a user from the account |

Running actions

membrane action run <actionId> --connectionId=CONNECTION_ID --json

To pass JSON parameters:

membrane action run <actionId> --connectionId=CONNECTION_ID --i