Keep BotStar chat context current with scheduled IP enrichment
Refresh visitor context on a schedule by enriching supplied IP data through Abstract and reinitializing the BotStar widget with the updated information.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Livechat boot
Reinitializes the live chat widget with updated data.
Why this helps
Visitor context can become stale between sessions, leaving the next conversation to start with details that need to be checked again.
- Refresh widget configuration with updated context.
- Reduce repeat lookups when a visitor returns.
- Keep scheduled context maintenance out of the team's working memory.
Setup
Build it in a few focused steps.
- 1Connect Abstract and BotStar once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name the context refresh.
- 3Tell Notis to enrich the supplied visitor IP data with Abstract and reinitialize the BotStar widget using the updated context.
- 4Choose the Notis cron trigger, set the recurring schedule, and select where run reports should go.
- 5Test with one real visitor context example and check the reinitialized widget.
Questions about this workflow
What does the livechat boot action do?
It reinitializes the live chat widget with provided data, after the widget has already loaded.
Does Abstract supply visitor IP data?
Abstract enriches IP data, but the IP itself must be supplied to the automation.
Can this run without a BotStar widget already loaded?
The documented action reinitializes the widget after initial load, so the workflow should be used where that widget is available.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Abstract to Botstar. A trigger fires from one place; an action lands in another.
Abstract triggers
Botstar actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
BotStar LiveChat onClose Callback
Registers a callback that runs when the chat window closes.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Bot
Get BotStar Application IDs
Retrieves the application IDs used by the live chat widget.
Create Bot Attribute
Livechat boot
Reinitializes the live chat widget with updated data.
Create CMS Entity
Close BotStar Livechat Widget
Hides the live chat window.
Create Entity Fields
Connect any two apps with Notis in the middle.
Abstract 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.