Connect Abstract to Botstar

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

View example

Refresh BotStar profiles with verified lead details

Use Abstract to verify a phone number or validate an email from an incoming lead, then update the active BotStar conversation with the confirmed details.

View example

Return verified contact details to a BotStar chatbot

Check contact details submitted in a BotStar webview with Abstract, then send the result back to the chatbot as a webview response.

View example

Close a BotStar chat after an IP risk check

When a webhook supplies an IP for review, use Abstract to enrich its data and close the BotStar live chat widget if the result meets your stated risk criteria.

View example

Open BotStar live chat for a scheduled outreach window

On a schedule, ask Notis to use Abstract to validate a supplied outreach contact, then open the BotStar live chat widget when the contact passes your stated check.

View example

Refresh BotStar live chat with current visitor context

On a recurring schedule, use Abstract to enrich supplied visitor IP data and reinitialize the BotStar widget with the updated context.

Supported Triggers and Actions

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

Abstract 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

ActionInstant

Get BotStar Application IDs

Retrieves the application IDs used by the live chat widget.

ActionInstant

Create Bot Attribute

ActionInstant

Livechat boot

Reinitializes the live chat widget with updated data.

ActionInstant

Create CMS Entity

ActionInstant

Close BotStar Livechat Widget

Hides the live chat window.

ActionInstant

Create Entity Fields

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.