Connect AimTell to Botstar

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

View example

Turn AimTell subscriber interest into BotStar content

Send an AimTell subscriber or campaign webhook to Notis and create a BotStar CMS item with the provided interest details for your chatbot to use.

View example

Update BotStar content with AimTell campaign feedback

Use an AimTell webhook carrying updated campaign feedback to revise the matching BotStar CMS item, keeping chatbot content current.

View example

Add an AimTell interest segment to BotStar

When an AimTell webhook reports a new interest segment, create a BotStar bot attribute to make that concept available in the bot configuration.

View example

Refresh a BotStar attribute with AimTell campaign context

Use an AimTell webhook to update a selected BotStar bot attribute with new campaign context, keeping the bot's shared reference value current.

View example

Define BotStar user attributes for AimTell subscriber context

When AimTell sends a new subscriber context type, create a BotStar user attribute so bot builders can represent that data in the user profile.

View example

Create a BotStar content structure for an AimTell campaign theme

When a new campaign theme arrives through an AimTell webhook, create a BotStar CMS entity to organize related chatbot content.

View example

Get a scheduled BotStar bot inventory

On a schedule, retrieve your BotStar bots so Notis can summarize the current inventory in a run report and reduce the need to check manually.

View example

Review BotStar CMS structures on a schedule

Retrieve BotStar CMS entities on a recurring schedule and have Notis summarize the available structures and configured fields in a run report.

View example

Keep a scheduled BotStar attribute catalog

Retrieve BotStar bot attributes on a recurring schedule and receive a concise catalog of names, descriptions, values, and data types.

Supported Triggers and Actions

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

AimTell 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.