Connect Slackbot to Chatfai

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

View example

Look up a Chatfai character from a Slack channel request

When a Slack channel message includes a Chatfai character ID, retrieve the public character details and summarize the context for the team.

View example

Send a Chatfai character brief for a Slack DM

When a teammate DMs a character ID, retrieve the public character and prepare a focused brief for the requester.

View example

Start character research after a Slack reaction

Use a reaction on a Slack message as a signal to retrieve the Chatfai character ID mentioned there and report the public profile.

View example

Review a Chatfai character when a Slack reaction is removed

When a reaction is removed from a Slack message, retrieve the referenced public character and summarize what should be reconsidered.

View example

Create a Chatfai character starter brief for a new Slack channel

When a Slack channel is created, retrieve a supplied Chatfai character and prepare a starter brief for the channel topic or project.

View example

Prepare Chatfai context for a Slack team FAQ

When a channel message asks about a Chatfai character, retrieve the public profile and draft a factual FAQ answer.

View example

Run a Chatfai character context check from a Slack DM

When a teammate sends a character ID for review, retrieve the public profile and highlight stated boundaries, themes, and missing context.

View example

Compare a reacted Chatfai character with the team request

When a Slack message receives a reaction, retrieve its public Chatfai character and compare the profile with the stated team need.

View example

Generate a Chatfai profile brief from a webhook

Send a character ID to a Notis webhook, retrieve the public Chatfai character, and produce a concise brief for downstream work.

Supported Triggers and Actions

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

Slackbot triggers

Chatfai actions

Recurring trigger

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

TriggerScheduled

Get Public Character By ID

Tool to retrieve a public character by its id. use when you need to fetch details of a single public character by providing its unique id.

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.