Turn Slack channel questions into chatbot guidance
Send a question raised in a Slack channel to the relevant Chatbotkit conversation and use the bot's reply to give the team a useful first answer.
Connect Slack to Chatbotkit
When something happens in Slack, Notis takes the next step in Chatbotkit. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Triggers when a new channel is created.
Do this · Action
Sends text to an existing ChatBotKit conversation and generates a reply.
Examples
Ways Notis can move work from Slack to Chatbotkit
Get Chatbotkit help for Slack DM requests
Use a direct message asking for help as a cue for Notis to consult Chatbotkit and return a useful reply in the conversation.
Use a reaction to request a Chatbotkit follow-up
Treat a chosen Slack reaction on a message as a signal to ask Chatbotkit for a next-step response in the relevant conversation.
Check Chatbotkit bot readiness for new Slack channels
When a Slack channel is created, have Notis consult the available Chatbotkit bots so the team can identify the right assistant for the new space.
Find Chatbotkit knowledge sources for channel questions
When a Slack channel question points to missing reference material, have Notis list available Chatbotkit datasets to help identify a knowledge source.
Review Chatbotkit conversations after Slack feedback
When someone posts actionable feedback in Slack, have Notis retrieve Chatbotkit conversations for review so bot-related issues have a trail to investigate.
Review a Chatbotkit conversation when Slack flags a reply
Use an agreed reaction on a Slack message as a cue to retrieve messages from the related Chatbotkit conversation for closer review.
Find reusable Chatbotkit skillsets from DM requests
When a Slack DM requests a capability, have Notis list Chatbotkit skillsets to help identify an existing reusable bundle.
Check Chatbotkit integrations during Slack setup discussions
When a Slack channel discusses connecting a support channel, have Notis list configured Chatbotkit integrations to support an informed setup conversation.
Supported Triggers and Actions
Notis builds workflows that link Slack to Chatbotkit. A trigger fires from one place; an action lands in another.
Slack triggers
Chatbotkit actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
TriggerScheduled
Complete Conversation
Sends text to an existing ChatBotKit conversation and generates a reply.
ActionInstant
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
TriggerInstant
Attach Dataset File
Attaches a file to a dataset as a source of knowledge content.
ActionInstant
New Channel Created Trigger
Triggers when a new channel is created.
TriggerInstant
Create Integration
Creates a support integration for a chatbot to handle customer inquiries.
ActionInstant
Channel Message Received
Triggers when a message is posted in a channel, excluding direct messages.
TriggerInstant
Authenticate Secret
Generates an authentication URL for a secret.
ActionInstant
Direct Message Received
Triggers when a new direct message, including a thread reply, is sent to a user.
TriggerInstant
Create Skillset
Creates a reusable skillset that groups multiple skills.
ActionInstant
Message Reaction Added
Triggers when a reaction is added to a message.
TriggerInstant
Clone Blueprint
Clones a blueprint and its associated resources.
ActionInstant
Message Reaction Removed
Triggers when a reaction is removed from a message.
TriggerInstant
List Bots
Retrieves a paginated list of bots.
ActionInstant
New Bot Message Received Trigger
Triggers when a bot posts a new message in a channel.
TriggerInstant
Clone Bot
Clones a bot with its settings and configuration.
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 schedule (recurring or one-time), and a change in one of your Notis databases.
Integration triggers
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,500+ 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
Scheduled triggers
Run a workflow on the clock, on a recurring schedule or once at a set date and time. Daily standups, hourly syncs, a one-off launch reminder: the workhorse of Notis.
Daily · 8:00Weekdays onlyOnce · Dec 13
Beta
Database triggers
Fire when a row in one of your Notis databases is added or edited, with optional filters on its properties. New lead added, status changed, value crosses a limit.
Row addedProperty editedValue > limit
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.
- 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
All12Manager5Telegram1Messages0WhatsApp2Email4Slack8
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.
Related pairs
More ways to connect Slack and Chatbotkit
Connect any two apps with Notis in the middle.
Slack and Chatbotkit, or any other combination from 1,500+ 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 Chatbotkit.