Appveyor integration

Quick start

Call Appveyor from your generated app's worker code via the OverSkill composio client. The toolkit slug below maps to Appveyor's public Composio identifier — your app references it by name and OverSkill handles the OAuth round-trip.

// In your generated app's worker handler:
const composio = composioClient(env);

const result = await composio.execute(
  "APPVEYOR_ACTION_NAME",
  { /* action parameters — see Actions section below */ }
);

return new Response(JSON.stringify(result), {
  headers: { "Content-Type": "application/json" }
});

Replace ACTION_NAME with one of the slugs listed in the Actions section below. The composio client handles auth + rate limits automatically — no API key is exposed to user code.

Setup

End-users supply their own Appveyor API key. OverSkill provides a pre-built connection form via the integration card — your app can call the composio client immediately once the user has connected.

Available actions

14 actions exposed via the Appveyor integration. Each maps to a callable slug — pass it to composio.execute(...) in your worker code.

• APPVEYOR_DELETE_BUILD
• APPVEYOR_DOWNLOAD_BUILD_LOG
• APPVEYOR_GET_BUILD_ARTIFACTS
• APPVEYOR_GET_BUILD_BY_VERSION
• APPVEYOR_GET_ENVIRONMENTS
• APPVEYOR_GET_PROJECT_BRANCH_STATUS_BADGE
• APPVEYOR_GET_PROJECTS
• APPVEYOR_GET_PROJECT_STATUS_BADGE
• APPVEYOR_GET_PUBLIC_PROJECT_STATUS_BADGE
• APPVEYOR_GET_ROLE
• APPVEYOR_GET_ROLES
• APPVEYOR_GET_USER_INVITATIONS