Keep BotStar campaign content in sync with creative updates
When a campaign creative changes, pass the latest details to Notis and update the corresponding BotStar CMS item.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Update Entity Item
Updates an item’s name, status, or custom values.
Why this helps
When creative changes after launch, outdated campaign details can linger in chatbot content and confuse customers.
- Reflect campaign revisions in the CMS item your bot uses.
- Avoid manually searching for and editing stale campaign content.
- Keep a clear webhook-driven path from creative update to bot content.
Setup
Build it in a few focused steps.
- 1Connect Abyssale and BotStar once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it for campaign updates.
- 3Tell Notis to find the intended BotStar CMS item using identifying information in the webhook request and update it with the latest campaign details.
- 4Choose the webhook trigger and select where run reports should go.
- 5Send one real update request and confirm the intended item changes.
Questions about this workflow
What information does the webhook need?
Include enough identifying information to find the existing CMS item, along with the updated campaign content. The matching fields depend on your BotStar entity.
Will this create a new item?
This workflow uses Update Entity Item, so it is intended for an existing item that Notis can identify.
Can this run from an Abyssale trigger event?
Abyssale trigger events are not listed. An external process must send the webhook request to Notis.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Abyssale to Botstar. A trigger fires from one place; an action lands in another.
Abyssale 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
Creates a new bot.
Get BotStar Application IDs
Retrieves the application IDs used by the live chat widget.
Create Bot Attribute
Creates a bot attribute for shared, multilingual values.
Livechat boot
Reinitializes the live chat widget with updated data.
Create CMS Entity
Creates a content entity with optional custom fields.
Close BotStar Livechat Widget
Hides the live chat window.
Create Entity Fields
Adds fields to an existing content entity.
Connect any two apps with Notis in the middle.
Abyssale 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.