Appveyor
for LuumenAI
Read AppVeyor builds, logs, and artifacts, and delete a bad build on approval.
Connect AppVeyor and Luumen can see your projects, look up a build by version, pull the job log, and list the artifacts it produced — without you switching to the web UI. When a build needs to be removed, Luumen shows you which one and waits for your approval before deleting it. Access uses an API key.
The Appveyor toolbox
14 tools: 13 read, 1 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadDownload Build LogDownload the build log for a specific job.
- ReadGet Build ArtifactsGet the list of artifacts for a specific build job.
- ReadGet Build By VersionGet a specific project build by version number.
- ReadGet EnvironmentsGet a list of all deployment environments.
- ReadGet Project Branch Status BadgeGet a project branch status badge image.
- ReadGet ProjectsGet a list of all projects for the authenticated account.
- ReadGet Project Status BadgeGet project status badge image.
- ReadGet Public Project Status BadgeGet status badge image for a project with a public repository.
- ReadGet RoleRetrieve details of a specific role.
- ReadGet RolesRetrieve all roles in the account.
- ReadGet User InvitationsRetrieve all pending user invitations in the account.
- ReadGet UsersRetrieve all users in the account.
- ReadList CollaboratorsRetrieve all collaborators in the account.
- WriteDelete BuildDelete a build by ID. Approval by default
One prompt, start to finish
What a governed Appveyor run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — delete build — is shown as a plan and requires approval by default, including the 1 action classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Appveyor — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
GitHubRepos, actions, and runbook code as context and as actions.
GitLabMerge requests and pipelines proposed, triggered, and rolled back.
BitbucketRead commits, diffs, and branches in Bitbucket, then open the fix as a held write.
Azure DevOpsAzure DevOps repos and pipelines as context — and as approved actions.Put Appveyor to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.