Connect Slackbot to Appveyor
When something happens in Slackbot, 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
Ways Notis can move work from Slackbot to Appveyor
List Appveyor projects when a Slack channel is created
When a new Slack channel appears, fetch the current Appveyor project list so the team can choose the right CI/CD workspace without leaving Slack.
Retrieve Appveyor build artifacts from a Slack channel request
When a team posts a channel message asking for build outputs, retrieve artifacts from the relevant Appveyor job and summarize what is available.
List Appveyor projects from a Slack direct message
When a founder asks in a Slack DM, return the current Appveyor project list for quick planning, triage, or handoff.
Retrieve release artifacts when a Slack message is marked ready
When someone adds a reaction to a release message, retrieve the relevant Appveyor build artifacts and share a concise handoff summary.
Audit artifact handoff when a Slack reaction is removed
When a reaction is removed from a release message, retrieve the related Appveyor artifacts so the team can reassess the handoff state.
List Appveyor environments for a Slack deployment question
When a deployment question appears in a Slack channel, fetch Appveyor environments and summarize the available targets.
Check Appveyor deployment targets from a Slack DM
When a founder asks privately about deployment targets, return the current Appveyor environment list with a focused summary.
Prepare Appveyor environment context for a new Slack channel
When a new project channel is created, retrieve Appveyor environments so the team starts with shared deployment context.
List Appveyor projects when a Slack kickoff message is starred
When a kickoff message receives a reaction, retrieve Appveyor projects and provide a concise project index for the team.
Supported Triggers and Actions
Notis builds workflows that link Slackbot to Appveyor. A trigger fires from one place; an action lands in another.
Slackbot triggers
Appveyor actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Build Artifacts
Tool to get the list of artifacts for a specific build job. use when you need to retrieve artifacts after a job completes.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Environments
Tool to get a list of all deployment environments. use when you need to enumerate available environments before creating deployments.
New Channel Created Trigger
Triggered when a new channel is created in Slack.
Get Projects
Tool to get a list of all projects for the authenticated account. use after authentication to enumerate available projects.
Channel Message Received
Triggered when a message is posted in a Slack channel (public, private, or multi-party IM). Does NOT match direct messages.
Get Role
Tool to retrieve details of a specific role. use when you need to inspect permissions and metadata of a role by id.
Direct Message Received
Triggered when a new direct message (DM) is sent to a user in Slack. Catches all DMs across all DM channels.
Get Roles
Tool to retrieve all roles in the account. use when you need to enumerate available roles before assigning permissions.
Message Reaction Added
Triggered when a reaction is added to a message in Slack. Supports optional filtering by channel and emoji name.
Get Users
Tool to retrieve all users in the account. use when you need to list all team users in your appveyor account.
Message Reaction Removed
Triggered when a reaction is removed from a message in Slack. Supports optional filtering by channel and emoji name.
Reaction Added Trigger
DEPRECATED: use `SLACK_MESSAGE_REACTION_ADDED` instead. Triggered when a reaction is added to a message in Slack.
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.
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.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
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.
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.
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:
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.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
More ways to connect Slackbot and Appveyor
Connect any two apps with Notis in the middle.
Slackbot and Appveyor, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Appveyor.