Keep BotStar LiveChat Profiles in Step with Ably Presence
When an Ably event signals a presence change, let Notis check the channel and update the active BotStar conversation with the details you need.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
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.
Why this helps
Presence changes and customer context live in different places, making it easy to miss who is active before replying.
- Refresh active conversation details after an Ably presence signal.
- Reduce manual checks across chat tools.
- Use a webhook payload to identify the relevant channel or user.
Setup
Build it in a few focused steps.
- 1Connect Ably and BotStar once in the Notis portal.
- 2Create an automation named for the profile refresh.
- 3Tell Notis to use the incoming Ably signal to check the relevant channel presence and update the matching active BotStar live chat profile with the supplied details.
- 4Pick the Notis webhook trigger and provide its endpoint to the system sending the Ably signal.
- 5Choose a report channel, then test with one real presence change and confirm the matching live chat session is active.
Questions about this workflow
Does Ably provide a native Notis trigger for this workflow?
No. Start the automation with a Notis webhook request sent when your Ably event occurs.
Which profile details will be updated?
Specify the details in your instruction and ensure the webhook or Ably data provides them. Notis cannot infer missing profile values.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Ably to Botstar. A trigger fires from one place; an action lands in another.
Ably 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.
Ably 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.