Keep BotStar credential records aligned with Accredible
Have Notis check credential details on a schedule and update a selected BotStar CMS item when the returned information shows a correction is needed.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Update Entity Item
Updates an item’s name, status, or custom values.
Why this helps
A detail changed in the credential record can remain incorrect in BotStar until someone notices and edits it manually.
- Correct an existing BotStar CMS item using returned credential details.
- Reduce manual comparison between credential and support records.
- Keep record names, statuses, or supplied field values aligned where the data supports it.
Setup
Build it in a few focused steps.
- 1Connect Accredible certificates and Botstar once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it for credential record corrections.
- 3Tell Notis how to identify the existing BotStar CMS item and update it using the matching returned credential details.
- 4Pick a recurring schedule and choose where run reports should go.
- 5Test with one real credential and its existing BotStar CMS item.
Questions about this workflow
Can Notis identify the correct CMS item by itself?
The instruction needs to provide a reliable way to identify the existing item from returned data. If no shared identifier is available, that matching information must be supplied.
Will it create an item if none exists?
This workflow uses the update action, which updates an existing item. It does not create missing items.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Accredible certificates to Botstar. A trigger fires from one place; an action lands in another.
Accredible certificates 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.
Accredible certificates 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.