Open Botstar chat from a Slack handoff reaction
Use a designated Slack reaction on a handoff message to open the Botstar live chat for the person taking over.
Connect Slack to Botstar
When something happens in Slack, Notis takes the next step in Botstar. 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
Generates a JavaScript callback snippet for when the live chat window closes.
Examples
Ways Notis can move work from Slack to Botstar
Close Botstar chat from a Slack resolution reaction
When a teammate marks a Slack thread resolved with a chosen reaction, ask Botstar to close its live chat widget.
Update Botstar session details from a Slack handoff
When a channel handoff includes a useful customer update, ask Notis to update the active Botstar live chat profile.
Use a Slack DM to refresh Botstar live chat details
When a direct message contains a clear correction or update, ask Notis to apply it to the active Botstar live chat profile.
Update Botstar details when Slack confirms a customer correction
Use a designated reaction to confirm a customer detail in Slack, then request a Botstar live chat profile update.
Fetch Botstar app details when a support channel is created
When a new Slack support channel is created, ask Notis to retrieve the Botstar app ID needed for a widget setup task.
Retrieve Botstar app ID from a widget setup request
When a Slack channel message requests widget setup, retrieve the Botstar app ID so the setup owner has the required identifier.
Retrieve Botstar app ID from a direct setup request
A direct Slack setup request can cue Notis to retrieve the Botstar app ID for a teammate preparing a widget.
Use a Slack reaction to request Botstar app details
Mark a widget setup message with a chosen reaction and retrieve the Botstar application ID for the next setup step.
Supported Triggers and Actions
Notis builds workflows that link Slack to Botstar. A trigger fires from one place; an action lands in another.
Slack triggers
Botstar actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
TriggerScheduled
BotStar LiveChat onClose Callback
Generates a JavaScript callback snippet for when the live chat window closes.
ActionInstant
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
TriggerInstant
Create Bot
Creates a new bot.
ActionInstant
New Channel Created Trigger
Triggers when a new channel is created.
TriggerInstant
Get BotStar Application IDs
Retrieves the application IDs used by the live chat widget.
ActionInstant
Channel Message Received
Triggers when a message is posted in a channel, excluding direct messages.
TriggerInstant
Create Bot Attribute
Creates a bot attribute for shared, multilingual values.
ActionInstant
Direct Message Received
Triggers when a new direct message, including a thread reply, is sent to a user.
TriggerInstant
Livechat boot
Generates code to reinitialize the live chat widget after it loads.
ActionInstant
Message Reaction Added
Triggers when a reaction is added to a message.
TriggerInstant
Create CMS Entity
Creates a content entity with optional custom fields.
ActionInstant
Message Reaction Removed
Triggers when a reaction is removed from a message.
TriggerInstant
Close BotStar Livechat Widget
Generates a JavaScript snippet to hide the live chat window in livechat or popup mode.
ActionInstant
New Bot Message Received Trigger
Triggers when a bot posts a new message in a channel.
TriggerInstant
Create Entity Fields
Adds fields to an existing content entity.
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 Botstar
Connect any two apps with Notis in the middle.
Slack and Botstar, 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 Botstar.