Connect Addressfinder to Appveyor

When something happens in Addressfinder, Notis takes the next step in Appveyor. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Do this · Action

Build an automation Browse examples

Examples

Ways Notis can move work from Addressfinder to Appveyor

View example

Verify a release build by version

When a release system sends a version to Notis, retrieve its AppVeyor build details and summarize whether the release is ready for review.

View example

Get a scheduled AppVeyor project inventory

On a schedule, retrieve the projects in the authenticated AppVeyor account and turn the results into a tidy inventory report.

View example

Review an AppVeyor build log on request

Send a build job identifier to a Notis webhook to retrieve its AppVeyor log and get a readable summary of the output.

View example

Get a scheduled deployment environment overview

On a recurring schedule, list AppVeyor deployment environments and receive a compact overview for planning and review.

View example

Collect artifacts after a build completes

When an external system reports a completed build and provides its job identifier, retrieve the AppVeyor artifacts and summarize what is available.

View example

Review AppVeyor roles on a schedule

Periodically retrieve the roles in an AppVeyor account and summarize the returned role list for an access review.

View example

Prepare an AppVeyor user list for review

Use a webhook to request the AppVeyor account's user list and receive a concise summary for a team access review.

View example

Review pending AppVeyor invitations

On a schedule, retrieve pending AppVeyor user invitations and summarize the outstanding invites so they are easier to follow up.

View example

Request an AppVeyor collaborator review

Start from an HTTP request to retrieve the AppVeyor collaborator list and prepare a concise summary for review.

Supported Triggers and Actions

Notis builds workflows that link Addressfinder to Appveyor. A trigger fires from one place; an action lands in another.

Addressfinder triggers

Appveyor actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Get Build Artifacts

Lists the artifacts produced by a build job.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Delete Build

Delete a build by its ID.

ActionInstant

Get Environments

Lists available deployment environments.

ActionInstant

Download Build Log

Download the log for a specific build job, whether running or complete.

ActionInstant

Get Projects

Lists projects in your account.

ActionInstant

Get Role

Retrieves details about a specific role.

ActionInstant

Get Build By Version

Retrieve a project build by its version number.

ActionInstant

Get Roles

Lists all roles in your account.

ActionInstant

Trigger Types

Four ways to start an automation.

A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.

New Notion pageStripe chargeCalendar event

Webhook triggers

A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.

Any HTTP POSTCustom backendIoT event

Works with

ZapierPipedream

Most used

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

Database triggers

Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.

Row insertedValue > limitQuery match

Why AI automation

Classic automation breaks. AI adapts.

Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.

Classic automationAI automation

Cost

$ · pay per run

$$ · AI models per run

Reliability

Breaks on schema change

Adapts to format changes

Setup

Click 8 dropdowns

Describe it in English

Handles fuzzy

Hard-coded fields only

Reads intent, summarises

Human in loop

Bolted on

Built in · approval inbox

Maintenance

You own every break

Self-heals · we own it

Ease of use

Describe it. Notis builds it.

Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.

You · in the Notis Builder

NEW

“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”

Notis built this automation:

TriggerRow added to "Q4 OKRs"

Condition✦Status = "Blocked"

AI step✦Summarise the blocker in plain English

ActionDM the row owner with summary

Timeout✦No reply in 24h → ping you

Observability

Watch every run.

Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.