DashboardSign inStart your trial

AppveyorAppveyor
01Integration field card

Appveyor Integration & Workflow Automation

Run Appveyor on autopilot. Keep the veto.

14 actions

Your Appveyor builds trigger deployments that ship code you haven't laid eyes on. Rills proposes the action, you approve from your phone before anything goes out.

Try the approval demo

Interactive. No signup. 14 days free · approvals always free.

Powered by Composio
02. The trust layer

Most automation fires first, asks later. Rills shows you the change before it ships.

Every consequential project management action from Appveyor arrives on your phone first. Approve in seconds. Decline without explaining yourself. Workflows wait, paused at zero cost, until you decide.

Queue 3

APPVEYOR · BUILD LOG REVIEW
85

Download build log for failed build #4123 and notify the team?

Build #4123 failed at step 'Tests'

Last 5 builds all passed

Same error pattern as last week's incident

SWIPE → APPROVE
Illustrative. Your real proposals match your data and your approval history.
  1. Free to wait. Free to think.

    Approvals and logic don't cost a credit. Pause a workflow for three hours or three weeks. The price is the same: zero. You only pay when something real happens: an AI call, an outbound action.

  2. Approve from your phone in five seconds.

    Swipe right when you're sure. Decline when you're not. Between meetings, mid-coffee, on the train. No dashboard to babysit, no inbox triage, and no surprise send you find out about after it's already out the door.

  3. Routine cases graduate themselves.

    Every approval feeds a confidence score for that exact workflow shape. The obvious cases (the ones you've green-lit fifty times) start running on their own. The judgment calls still come to you.

03. Overview

About Appveyor automation

Build artifacts, branch status badges, collaborator invites and build logs pile up faster than you can review them. A failed deploy ships to production before you've seen the test result. The ones AI gets wrong are the ones that break your demo at 3pm.

When Appveyor runs unsupervised

When Appveyor runs without a human check, small config changes can cause big problems.

  • A delete-build operation removes the artifact that the client just approved.
  • A collaborator invitation is sent to the wrong email, granting access to someone outside the team.
  • The project status badge updates to 'failing' even though the failure was a flaky test, triggering panic in your support inbox.
  • A build-by-version retrieval uses the wrong version number, and the downstream deployment fires the wrong binary.

What Rills does inside Appveyor

Rills watches for changes you care about and surfaces proposals for the operations that matter: download build logs when a build finishes, fetch environment variables for a new branch, or manage user invitations based on a schedule. You review each proposal on your phone, then approve or dismiss.

The artifact only deploys after you tap 'approve' on your phone; the badge only updates when you say it's accurate.

Why Appveyor has no triggers and how Rills fills the gap

Appveyor's API is event-driven but does not push notifications. Rills polls on your schedule or runs on upstream triggers from other tools. This Appveyor automation pattern works with Rills' flexible scheduling.

  • Poll every 15 minutes for completed builds and propose downloading build logs when failures appear.
  • Run on a cron schedule to fetch project branch status badges and alert you before they go public.
  • Trigger by a GitHub push event to check environment availability and propose listing collaborators for a new branch. For project management teams, Appveyor automation becomes safer with a human in the loop.
04. Actions

What Rills can do in Appveyor

4 of 14 actions across reads, writes, and updates.

  1. 01

    Download Build Log

    Retrieves the detailed build log output from a specific job, allowing you to review build results, errors, and diagnostic information without accessing the AppVeyor dashboard directly.

  2. 02

    Get Build Artifacts

    Retrieves the list of files and artifacts generated by a completed build job, allowing you to access build outputs like compiled binaries, installers, or test reports.

  3. 03

    Get Build By Version

    Retrieve detailed information about a specific project build by its version number, allowing you to quickly access build status, logs, and artifacts for any release.

  4. 04

    Get Projects

    Retrieve all projects associated with your AppVeyor account to view your continuous integration and deployment pipelines in one place.

05. NEXT MOVE

Approve every Appveyor change before it ships.

14 days free. No credit card. About 90 seconds to your first proposal.