Skip to content
Notis

Keep chat-close behavior in view each week

Give close handling a regular place in your routine so it is less likely to disappear between releases.

Trigger

Recurring schedule

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

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 behavior can be forgotten when a release checklist focuses mainly on infrastructure.

  • Surfaces close behavior in a recurring review
  • Makes the client setup more consistent
  • Reduces memory load across release cycles

Setup

Build it in a few focused steps.

  • 1Connect Railway and BotStar to Notis once through the portal.
  • 2Create a new automation asking Notis to register the close callback after the widget is initialized during the weekly client review.
  • 3Select a weekly schedule as the trigger.
  • 4Choose a channel for reports and confirm the first run against the client setup.

Questions about this workflow

Will the schedule close the widget?

No. It registers the callback that runs when the chat window is closed.

Can the action run before initialization?

No. Register the callback after the widget is initialized.

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.

TriggerScheduled

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."

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Get BotStar Application IDs

Tool to retrieve the botstar application id (`appid`). use when initializing or reinitializing the live chat widget.

ActionInstant

Livechat boot

Tool to reinitialize the live chat widget with provided data. use after initial load to reset or update widget configuration.

ActionInstant

Close BotStar Livechat Widget

Tool to hide the live chat window. use when the chat widget is configured in livechat or popup mode.

ActionInstant

Livechat on open

Tool to register a callback when the chat window is opened. use after widget initialization.

ActionInstant

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').

ActionInstant

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.

ActionInstant

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.

ActionInstant

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.