Connect Ably to Botstar

When something happens in Ably, 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 Ably to Botstar

View example

Refresh BotStar LiveChat Profiles from Ably Presence

Use an Ably webhook signal to check channel presence and refresh the matching BotStar live chat profile with relevant user details.

View example

Open BotStar LiveChat When an Ably Event Arrives

Use an incoming Notis webhook to respond to an Ably event by opening the already bootstrapped BotStar live chat widget.

View example

Close BotStar LiveChat After an Ably Resolution Signal

When an Ably webhook signal indicates a conversation is resolved, hide the configured BotStar live chat window.

View example

Send Ably Context from a BotStar Webview to the Chatbot

Use an Ably event to provide relevant context to an open BotStar webview, then send the resulting response back to the chatbot.

Supported Triggers and Actions

Notis builds workflows that link Ably to Botstar. A trigger fires from one place; an action lands in another.

Ably 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

Tool to register a callback when the chat window is closed. use after the widget is initialized. example prompt: "register an onclose handler that logs 'goodbye!' to the console."

ActionInstant

Webhook trigger

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

TriggerInstant

Get BotStar Application IDs

Tool to retrieve the botstar application id (`appid`). use when initializing or reinitializing the live chat widget.

ActionInstant

Livechat boot

Tool to reinitialize the live chat widget with provided data. use after initial load to reset or update widget configuration.

ActionInstant

Close BotStar Livechat Widget

Tool to hide the live chat window. use when the chat widget is configured in livechat or popup mode.

ActionInstant

Livechat on open

Tool to register a callback when the chat window is opened. use after widget initialization.

ActionInstant

Livechat open

Tool to show the live chat window. use after the widget has been bootstrapped with botstarapi('boot') to programmatically open the chat window (mode must be 'livechat' or 'popup').

ActionInstant

Livechat update

Tool to update user details on the current live chat session. use when you need to modify user profile attributes during an active conversation.

ActionInstant

Get BotStar Webview Parameter

Tool to retrieve a parameter value passed from the botstar chatbot to the webview. use inside onchatbotready after your page loads in modal mode with bs:input meta tags.

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.