Skip to content
Notis

Publish BotStar when its Agility content is ready

Describe the content conditions that signal launch readiness, and let Notis publish the bot when its scheduled check passes.

Trigger

Recurring schedule

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

Action

Publish Bot to Live

Publishes a bot to the live environment.

Why this helps

A bot launch can stall while someone repeatedly checks whether the supporting content is ready.

  • Reduce repeated manual readiness checks.
  • Make publishing contingent on conditions you define.
  • Keep the launch decision tied to current source content.

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, state the Agility content readiness conditions and tell Notis to publish the BotStar bot only when they are met.
  • 4Pick a recurring schedule as the trigger.
  • 5Choose a report channel, then test with one real readiness check before relying on publishing.

Questions about this workflow

What counts as ready?

You define the criteria in the instruction, such as required entries or statuses. The listed capabilities do not provide a standard readiness rule.

Will the workflow publish on every scheduled run?

Your instruction should require the readiness check to pass before publishing. Test that condition with a real example and review the run report.

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.

TriggerScheduled

BotStar LiveChat onClose Callback

Registers a callback that runs when the chat window closes.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Create Bot

Creates a new bot.

ActionInstant

Get BotStar Application IDs

Retrieves the application IDs used by the live chat widget.

ActionInstant

Create Bot Attribute

Creates a bot attribute for shared, multilingual values.

ActionInstant

Livechat boot

Reinitializes the live chat widget with updated data.

ActionInstant

Create CMS Entity

Creates a content entity with optional custom fields.

ActionInstant

Close BotStar Livechat Widget

Hides the live chat window.

ActionInstant

Create Entity Fields

Adds fields to an existing content entity.

ActionInstant

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.