Skip to content
Notis

Keep BotStar entity names aligned with Agility

Send a restructure request and have Notis update the BotStar entity name to match the revised content model.

Trigger

Webhook received

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

Action

Update CMS Entity

Updates an existing content entity’s name or configuration.

Why this helps

A renamed content model can leave confusing labels in the chatbot CMS and make later maintenance harder.

  • Keep entity labels consistent after content reorganizations.
  • Reduce manual cleanup across systems.
  • Use an explicit request to identify the entity and its new name.

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, explain how to identify the BotStar entity and provide its new name from the restructure request.
  • 4Choose the webhook trigger and have your content process send it when naming changes.
  • 5Choose a report channel, then test with one real restructure request.

Questions about this workflow

Can Notis rename the Agility model too?

This workflow updates the BotStar CMS entity. The Agility action side is limited to fetching and managing content as described in the app overview.

What if several entities have similar names?

Include a stable entity identifier in the request or define a precise matching rule in your instruction.

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.