Wire up BotStar's open callback after a release
Use a release signal to prompt the client setup for a BotStar open listener, so the expected callback is registered after initialization.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Livechat on open
Tool to register a callback when the chat window is opened. use after widget initialization.
Why this helps
Callback setup can be overlooked when release work spans frontend and deployment tasks.
- Prompts callback registration at release setup time
- Makes the expected open behavior explicit
- Reduces forgotten client initialization steps
Setup
Build it in a few focused steps.
- 1Connect Railway and BotStar to Notis once through the portal.
- 2Create an automation that asks for the BotStar open callback to be registered after widget initialization following a release signal.
- 3Select an incoming webhook trigger and connect it to the appropriate Railway release step.
- 4Choose a channel for run reports, then test with one real release signal.
Questions about this workflow
When should this callback be registered?
After the BotStar widget is initialized, as required by the action.
Does the webhook itself register browser code in Railway?
No. It starts the Notis automation; use it in the client setup flow that has access to 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.