Make BotStar's close callback part of release setup
Keep chat-close behavior on the release checklist without relying on memory. Send a release signal to Notis when the initialized widget is ready.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
BotStar LiveChat onClose Callback
Tool to register a callback when the chat window is closed. use after the widget is initialized. example prompt: "register an onclose handler that logs 'goodbye!' to the console."
Why this helps
Close handling is easy to forget when deployment work shifts attention to infrastructure and launch checks.
- Calls attention to close handling after initialization
- Makes release steps more repeatable
- Reduces manual checklist recall
Setup
Build it in a few focused steps.
- 1Connect Railway and BotStar to Notis once through the portal.
- 2Create an automation with one plain-language instruction to register the BotStar close callback after initialization.
- 3Select an incoming webhook trigger tied to the release setup process.
- 4Choose a run-report channel and test with one real signal when the widget is initialized.
Questions about this workflow
What does the callback action register?
It registers a callback for when the chat window closes; use it after the widget is initialized.
Can a Railway deploy call the action directly?
The Railway process sends a request to Notis. The callback registration belongs in the client flow that has the initialized widget.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Railway to Botstar. A trigger fires from one place; an action lands in another.
Railway triggers
Botstar actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
BotStar LiveChat onClose Callback
Tool to register a callback when the chat window is closed. use after the widget is initialized. example prompt: "register an onclose handler that logs 'goodbye!' to the console."
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get BotStar Application IDs
Tool to retrieve the botstar application id (`appid`). use when initializing or reinitializing the live chat widget.
Livechat boot
Tool to reinitialize the live chat widget with provided data. use after initial load to reset or update widget configuration.
Close BotStar Livechat Widget
Tool to hide the live chat window. use when the chat widget is configured in livechat or popup mode.
Livechat on open
Tool to register a callback when the chat window is opened. use after widget initialization.
Livechat open
Tool to show the live chat window. use after the widget has been bootstrapped with botstarapi('boot') to programmatically open the chat window (mode must be 'livechat' or 'popup').
Livechat update
Tool to update user details on the current live chat session. use when you need to modify user profile attributes during an active conversation.
Get BotStar Webview Parameter
Tool to retrieve a parameter value passed from the botstar chatbot to the webview. use inside onchatbotready after your page loads in modal mode with bs:input meta tags.
Connect any two apps with Notis in the middle.
Railway and Botstar, or any other combination from 1,000+ 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.