Connect Agility cms to Botstar

When something happens in Agility cms, Notis takes the next step in Botstar. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Do this · Action

Build an automation Browse examples

Examples

Ways Notis can move work from Agility cms to Botstar

View example

Send published Agility content to BotStar

When an Agility CMS webhook signals a published entry, create a corresponding BotStar CMS item for your bot to use.

View example

Import Agility content into BotStar on a schedule

On a recurring schedule, find Agility CMS entries that meet your instruction and add them to a BotStar CMS entity.

View example

Refresh a BotStar item when Agility content changes

Use an Agility CMS webhook to prompt Notis to update the matching BotStar CMS item with the latest entry details.

View example

Review BotStar CMS items against Agility content

On a schedule, review BotStar CMS items alongside Agility content and report items that appear outdated or need attention.

View example

Create a BotStar content entity from an Agility model

When an Agility model or content type is ready, use a webhook to create a corresponding BotStar CMS entity.

View example

Publish BotStar after an Agility content readiness check

On a schedule, check Agility content for the readiness conditions you specify, then publish the BotStar bot when they are met.

View example

Create a BotStar bot for an Agility launch

When a launch request arrives by webhook, create a named BotStar bot using details supplied with the request.

View example

Refresh a BotStar status attribute from Agility

On a schedule, check Agility CMS content and update a BotStar attribute with the current status you specify.

View example

Mark retired Agility content inactive in BotStar

When a retirement request arrives, find the corresponding BotStar CMS item and update its status according to your instruction.

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

Trigger Types

Four ways to start an automation.

A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.

New Notion pageStripe chargeCalendar event

Webhook triggers

A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.

Any HTTP POSTCustom backendIoT event

Works with

ZapierPipedream

Most used

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

Database triggers

Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.

Row insertedValue > limitQuery match

Why AI automation

Classic automation breaks. AI adapts.

Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.

Classic automationAI automation

Cost

$ · pay per run

$$ · AI models per run

Reliability

Breaks on schema change

Adapts to format changes

Setup

Click 8 dropdowns

Describe it in English

Handles fuzzy

Hard-coded fields only

Reads intent, summarises

Human in loop

Bolted on

Built in · approval inbox

Maintenance

You own every break

Self-heals · we own it

Ease of use

Describe it. Notis builds it.

Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.

You · in the Notis Builder

NEW

“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”

Notis built this automation:

TriggerRow added to "Q4 OKRs"

Condition✦Status = "Blocked"

AI step✦Summarise the blocker in plain English

ActionDM the row owner with summary

Timeout✦No reply in 24h → ping you

Observability

Watch every run.

Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.