Spot missing BotStar fields before verified data arrives
A scheduled review can surface whether your bot's existing attribute definitions include the contact fields your process expects.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
List Bot Attributes
Lists attributes configured for a bot.
Why this helps
Bot schemas can drift, leaving teams unsure whether verified contact information has a consistent place to go.
- Get a recurring view of the bot attributes already defined.
- Notice missing expected fields before they disrupt a workflow.
- Keep schema review out of ad hoc memory and manual checks.
Setup
Build it in a few focused steps.
- 1Connect Addressfinder and BotStar once in the Notis portal.
- 2Create an automation in the portal or tell Notis from any channel.
- 3In one instruction, ask Notis to retrieve the BotStar bot attributes and summarize whether the contact fields you specify are present.
- 4Pick the recurring schedule and choose where run reports should go.
- 5Run once with a real bot and review the report against your expected fields.
Questions about this workflow
Does this automation create or change attributes?
No. It retrieves and reviews existing bot attributes.
Can it know which fields we require?
Only if you specify the expected field names in the instruction. Notis cannot infer your requirements from Addressfinder.
Does the schedule call Addressfinder?
This workflow uses the scheduled trigger to retrieve BotStar attributes. It does not claim to query Addressfinder, which has no listed trigger or action event here.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Addressfinder to Botstar. A trigger fires from one place; an action lands in another.
Addressfinder 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.
Addressfinder 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.