Keep BotStar CMS items current with verified form corrections
Carry a checked correction from an Algodocs form workflow into the BotStar record it belongs to.
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 corrected form value can reach the document workflow but never make it into the corresponding BotStar record.
- Update an existing BotStar CMS item when a verified correction arrives.
- Keep the stored record aligned with the corrected form information.
- Avoid re-entering corrections already checked in Algodocs.
Setup
Build it in a few focused steps.
- 1Connect Algodocs and BotStar once in the Notis portal.
- 2Create an automation in Automations, New Automation, and instruct Notis how to identify the BotStar CMS item and apply a verified Algodocs correction.
- 3Choose the Webhook trigger and send each verified correction from your Algodocs workflow.
- 4Choose where run reports should go, then test with one real correction and confirm the intended item was updated.
Questions about this workflow
Will the automation decide which correction is valid?
The workflow uses the verified correction your Algodocs process sends. Describe the conditions for applying it in your instruction.
What information is needed to update the right BotStar item?
Your request should include enough information to identify the existing item and the correction. If the incoming result does not identify the item, supply a lookup rule in your instruction.
When this happens · Trigger
Do this · Action
Updates an item’s name, status, or custom values.
Supported Triggers and Actions
Notis builds workflows that link Algodocs to Botstar. A trigger fires from one place; an action lands in another.
Algodocs triggers
Botstar actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
BotStar LiveChat onClose Callback
Generates a JavaScript callback snippet for when the live 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
Generates code to reinitialize the live chat widget after it loads.
Create CMS Entity
Creates a content entity with optional custom fields.
Close BotStar Livechat Widget
Generates a JavaScript snippet to hide the live chat window in livechat or popup mode.
Create Entity Fields
Adds fields to an existing content entity.
Connect any two apps with Notis in the middle.
Algodocs and Botstar, or any other combination from 1,600+ 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.