Connect Slackbot to Aivoov

When something happens in Slackbot, Notis takes the next step in Aivoov. 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 Slackbot to Aivoov

View example

Answer channel voice language requests

When a Slack channel asks for a voice language, fetch matching Aivoov voices and summarize the best options for the team.

View example

Turn a Slack DM into a voice shortlist

When someone sends a direct message asking for casting help, retrieve Aivoov voices and return a focused shortlist with useful details.

View example

Use a reaction to request voice review

When a Slack message receives a chosen reaction, fetch Aivoov voices and prepare a review summary for the referenced voice need.

View example

Prepare voice options for a new project channel

When a Slack channel is created, retrieve Aivoov voices and post a starter guide tailored to the channel's stated purpose.

View example

Answer bot requests with a voice catalog

When a Slack bot posts a request, retrieve the Aivoov voice catalog and summarize the options for the human team.

View example

Reopen voice research when a reaction is removed

When a review reaction is removed, retrieve Aivoov voices again and prepare a fresh summary for reconsideration.

View example

Triage new Slack messages into voice briefs

When a new Slack message arrives, detect voice related requests and return an Aivoov shortlist only when the message contains a relevant brief.

View example

Run an on demand voice catalog check

Start a webhook workflow whenever another system needs the current Aivoov voice list and a human readable summary.

View example

Send a weekly voice availability brief

On a recurring schedule, retrieve Aivoov voices and prepare a concise weekly availability brief for the team.

Supported Triggers and Actions

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

Slackbot triggers

Aivoov actions

Recurring trigger

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

TriggerScheduled

List Voices

Tool to retrieve a list of available voices. use to filter voices by language after confirming api key is valid.

ActionInstant

Webhook trigger

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

TriggerInstant

New Channel Created Trigger

Triggered when a new channel is created in Slack.

TriggerInstant

Channel Message Received

Triggered when a message is posted in a Slack channel (public, private, or multi-party IM). Does NOT match direct messages.

TriggerInstant

Direct Message Received

Triggered when a new direct message (DM) is sent to a user in Slack. Catches all DMs across all DM channels.

TriggerInstant

Message Reaction Added

Triggered when a reaction is added to a message in Slack. Supports optional filtering by channel and emoji name.

TriggerInstant

Message Reaction Removed

Triggered when a reaction is removed from a message in Slack. Supports optional filtering by channel and emoji name.

TriggerInstant

Reaction Added Trigger

DEPRECATED: use `SLACK_MESSAGE_REACTION_ADDED` instead. Triggered when a reaction is added to a message in Slack.

TriggerInstant

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.