Keep matching BotStar items in sync with Agility
When an Agility change matters to your bot, have Notis find the corresponding item and refresh it in BotStar CMS.
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
A changed source page can leave an older version in your chatbot's content collection.
- Reduce outdated chatbot content after a source change.
- Update an existing item instead of creating another copy.
- Describe your matching rule in plain language.
Setup
Build it in a few focused steps.
- 1Connect Agility CMS and BotStar once in the Notis portal.
- 2Create an automation by telling Notis the outcome you want, or use Automations, New Automation in the portal.
- 3In one instruction, explain how to identify the matching BotStar item and update it from the webhook's Agility entry.
- 4Choose the webhook trigger and have Agility CMS send it for relevant content changes.
- 5Choose a report channel, then test with one real changed entry and its existing BotStar item.
Questions about this workflow
Will Notis know which BotStar item matches the Agility entry?
Only if your instruction and available entry data provide a reliable matching key. The listed capabilities do not promise automatic cross-app matching.
Can the workflow create an item if no match exists?
You can describe a fallback in the instruction, but this workflow's action is to update an item. Confirm your intended behavior with a real example during setup.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Agility cms to Botstar. A trigger fires from one place; an action lands in another.
Agility cms 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.
Agility cms 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.