Get a scheduled review of device status entries
Replace a manual scan of logged device data with a short review delivered on a schedule you choose.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
List Entity Items
Lists items in a content entity, with optional pagination and filters.
Why this helps
When nobody owns a regular review, patterns in logged device readings can sit unnoticed among other work.
- Review BotStar CMS device entries on a consistent schedule.
- Surface notable readings from the entries returned by BotStar.
- Receive the run report where your team already works.
Setup
Build it in a few focused steps.
- 1Connect Adafruit IO and BotStar once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it.
- 3Ask Notis to retrieve the device log items from BotStar CMS and summarize notable entries returned.
- 4Choose a recurring schedule and select where run reports should go.
- 5Test with one real example and confirm the summary reflects the returned entries.
Questions about this workflow
Does this schedule read directly from Adafruit IO?
The listed action retrieves BotStar CMS items. Adafruit IO readings need to have been placed in that entity already, for example by a separate webhook workflow.
Can Notis detect trends across all historical readings?
Notis can analyze the items returned by BotStar. If you need a particular historical range or baseline that is not available in those items, include that data or requirement in your instructions.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Adafruit IO to Botstar. A trigger fires from one place; an action lands in another.
Adafruit IO 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.
Adafruit IO 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.