ceven

Botstar

Syncs live chat sessions to your CRM, updates user profiles in real time based on chat inputs, and manages widget states across your website pages.

Try Botstar in Ceven

Ask Ceven anything
Standard

Why use Ceven?

  1. AI native Botstar integration

    • Describe the outcome and Ceven picks the right Botstar calls, fills the parameters, and checks the result.
    • Structured, agent friendly tool schemas so each call runs reliably instead of by guesswork.
    • Rich coverage for reading, writing, and querying your Botstar data, across all 31 of its actions.

  2. Managed auth

    • Built in OAuth with automatic token refresh and rotation.
    • One place to manage, scope, and revoke Botstar access.
    • Per user and per environment credentials instead of shared keys.

  3. Agent optimized design

    • Actions are tuned from real success and error rates so reliability climbs over time.
    • Full execution logs so you always know what ran in Botstar, when, and on whose behalf.
    • The agent pauses and asks when Botstar is unclear instead of plowing ahead.

  4. Enterprise grade security

    • Fine grained access so you control which agents and people can reach Botstar.
    • Least privilege by default, read scopes first and only the writes a workflow needs.
    • A full audit trail of every Botstar action to support review and sign off.

Supported tools

Every action Ceven's agents can run on Botstar, and when to use it.

Register close callback
Use this to trigger a specific action when the user closes the chat window, such as logging a session end event.
Get application IDs
Pull the Botstar appid needed to initialize or reinitialize the live chat widget on a page.
Boot live chat
Use this to reset or update the widget configuration after the initial page load with new session data.
Close chat widget
Hide the live chat window programmatically when the widget is in livechat or popup mode.
Register open callback
Set up a trigger that fires the moment a user opens the chat window to track engagement.
Open chat widget
Force the chat window to appear for the user after the widget has been bootstrapped.
Update user details
Modify user profile attributes and custom fields during an active live chat session.
Get webview parameter
Pull a specific value passed from the chatbot to the webview, typically used for custom modal inputs.
Send webview response
Push data from an open webview back into the Botstar chatbot flow to drive the next response.
Set widget mode
Switch the chat widget between popup and livechat modes based on user behavior.
Fetch session state
Read the current state of the active conversation to determine if a human agent is needed.
Clear user profile
Reset user attributes in the current session to start a fresh conversation flow.
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."
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.
Webview send response
Tool to send data from the webview back to the botstar chatbot. use when you need to transmit responses or custom outputs from an open webview.

21 actions · scroll to see them all

Frequently asked questions

Ceven interacts with Botstar webviews by utilizing the specific send response and get parameter tools. When a user interacts with a custom HTML page inside the bot, Ceven can extract the meta tags and input values, process them through a workflow, and then push the final result back into the bot conversation. This allows you to build complex calculators or booking forms that feel native to the chat experience while the actual logic and data storage happen in your own backend systems via Ceven. It effectively turns the Botstar webview into a two way data bridge.
Yes. You can use the livechat open action within a Ceven workflow. For example, if a user performs a specific action on your website that is tracked by a tool like Segment or Google Analytics, Ceven can receive that event and immediately call the Botstar boot and open functions. This ensures the chatbot appears exactly when the user is most likely to need help, rather than just sitting as a static icon in the corner of the screen throughout the entire visit.
Ceven handles multiple Botstar application IDs by storing them as separate environment variables within your workflow settings. When the agent needs to initialize a widget, it pulls the correct appid for the specific site or client context currently active. This means a single Ceven workflow can manage chat widgets across dozens of different domains, each linked to a different Botstar bot, provided the correct application ID is mapped to the corresponding domain in your configuration.
If a workflow attempts to open or update the widget before the bootstrap process is complete, the call will fail. To prevent this, Ceven workflows are designed to call the boot action first. The agent checks for the presence of the Botstar API on the page, executes the boot sequence with the necessary application ID, and then proceeds with the open or update command. This sequential execution ensures that the widget is fully loaded and ready to accept programmatic commands without causing console errors.
One specific quirk of the Botstar API is that user profile updates only persist if the session is correctly identified by a user ID or a persistent cookie. If a user is chatting anonymously and their session expires or they clear their cache, the attributes updated by Ceven may be lost. To avoid this, we recommend using the update user details action in conjunction with a known email address or internal customer ID. This ensures the data is tied to a permanent record in Botstar rather than a temporary session token.
Ceven uses the register close callback tool to achieve this. By setting up this handler during the initial widget boot, Ceven is notified the moment the user exits the chat. You can use this event to trigger a follow up email, mark a lead as inactive in your CRM, or start a timer for a re engagement prompt. It is a powerful way to ensure that the end of a conversation is treated as a data point for your sales and support teams.
Because Ceven interacts with Botstar via the client side API, there is negligible impact on the initial server response time. The Botstar widget loads asynchronously, and Ceven calls the API functions only after the necessary scripts are available in the browser. By using the boot action selectively, you can even delay the loading of the chat interface until a specific user action occurs, which can actually improve your initial page load performance and Core Web Vitals scores.
Ceven cannot rewrite the visual flow blocks inside the Botstar editor, but it can influence the path a user takes. By using the update user details action, Ceven can change a user attribute like status equals VIP. If your Botstar flow has a conditional block that checks for that specific attribute, the bot will automatically route the user down the VIP path. This allows you to change the user experience dynamically based on external data without ever touching the visual bot builder.

Alternatives to Botstar

Other tools that solve a similar problem. Ceven supports these too, so you can switch or run more than one at once.

Tidio logoTidioChatfuel logoChatfuelManyChat logoManyChat

Try Ceven on your stack

Plug Ceven on top of the tools you already run. Connect Botstar and the rest of your stack, describe the outcome, and its agents handle the work end to end, days of it in minutes.

Get started for free