Create a chatflow for each new Slack channel
When a Slack channel is created, have Flowise create a dedicated chatflow so the channel's purpose can get a useful AI workflow from day one.
When something happens in Slack, Notis takes the next step in Flowiseai. 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
Clones a chatflow; if capacity is full, it may delete another chatflow to retry.
When a Slack channel is created, have Flowise create a dedicated chatflow so the channel's purpose can get a useful AI workflow from day one.
Use a clearly marked Slack channel message as a cue for Notis to retrieve the current list of Flowise chatflows, making a quick inventory easier to request.
When a teammate asks for a known Flowise chatflow's details in Slack, have Notis retrieve the single chatflow so its configuration can be reviewed without a separate search.
When a team member raises a chatflow conversation concern in Slack, have Notis retrieve that chatflow's messages for review, subject to the context in your instruction.
Turn a clear Slack export request into a Flowise chatflow export so teammates can prepare a backup or review copy without a separate manual lookup.
When you DM Notis a clear request to clone an existing Flowise chatflow, have it duplicate the flow for an experiment or new use case.
Before changing a Flowise workflow, DM Notis the chatflow reference and have it retrieve the current details for a quick pre-change review.
DM Notis when you want a Flowise chatflow export for safekeeping or a review, and have it retrieve the export for the specified flow.
Use a chosen Slack reaction on a channel message to request the current Flowise chatflow list, giving a lightweight signal for an inventory lookup.
Notis builds workflows that link Slack to Flowiseai. A trigger fires from one place; an action lands in another.
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Clones a chatflow; if capacity is full, it may delete another chatflow to retry.
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create a new chatflow.
Triggers when a new channel is created.
Delete a chatflow.
Triggers when a message is posted in a channel, excluding direct messages.
Create a document store for managing embeddings and vector data.
Triggers when a new direct message, including a thread reply, is sent to a user.
Delete messages from a chatflow.
Triggers when a reaction is added to a message.
Create a chatflow lead for follow-up or CRM use.
Triggers when a reaction is removed from a message.
Permanently delete a tool; this action cannot be undone.
Triggers when a bot posts a new message in a channel.
Create a custom tool.
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.
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,700+ apps can start a workflow.
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
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.
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.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
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:
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.
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 monthWhatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
Every step can include an LLM call: summarise, classify, extract, rewrite.
Every run, every step, every input, all replay-able from Mission Control.
Pause for approval. Notis pings you in chat with one-tap approve.
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
Slack and Flowiseai, or any other combination from 1,700+ integrations.
When this happens · Trigger
Do this · Action
7-day trial of any paid plan, with $20 of usage included.
No card. Works with personal or business Flowiseai.