Connect Aeroleads to Chatbotkit

When something happens in Aeroleads, Notis takes the next step in Chatbotkit. 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 Aeroleads to Chatbotkit

View example

Add new AeroLeads prospects as ChatbotKit contacts

On a schedule, find newly discovered AeroLeads prospects and create ChatbotKit contacts with the available identifying details.

View example

Save AeroLeads prospect context as ChatbotKit memory

Find prospects on a schedule and save useful returned context as memories associated with ChatbotKit contacts.

View example

Add AeroLeads prospect research to a ChatbotKit dataset

Use a scheduled AeroLeads search to add selected returned research as records in an existing ChatbotKit dataset.

View example

Create a ChatbotKit contact from an AeroLeads webhook request

Start from an HTTP request, use its supplied prospect criteria with AeroLeads, and create a ChatbotKit contact from returned details.

View example

Save webhook-requested AeroLeads research to ChatbotKit memory

Use an HTTP request to start prospect research and store selected returned context as a ChatbotKit memory.

View example

Add AeroLeads research to a ChatbotKit conversation

On a schedule, find qualifying prospects and add a clearly labeled research message to the specified existing ChatbotKit conversation.

View example

Add requested AeroLeads findings to a ChatbotKit dataset

Start an AeroLeads lookup from an HTTP request and add selected returned findings to an existing ChatbotKit dataset.

View example

Start ChatbotKit conversations for selected AeroLeads prospects

Use a scheduled AeroLeads search to identify prospects and create ChatbotKit conversations for records with the required identifiers.

View example

Create a ChatbotKit conversation from a prospect request

Use an HTTP request and available AeroLeads results to create a ChatbotKit conversation for a selected prospect.

Supported Triggers and Actions

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

Aeroleads triggers

Chatbotkit actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Complete Conversation

Sends a message to a chatbot conversation and returns the bot's AI-generated reply.

ActionInstant

Webhook trigger

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

TriggerInstant

Attach Dataset File

Attaches a file to a dataset as a source of knowledge content.

ActionInstant

Create Integration

Creates a support integration for a chatbot to handle customer inquiries.

ActionInstant

Authenticate Secret

Generates an authentication URL for a secret.

ActionInstant

Create Skillset

Creates a reusable skillset that groups multiple skills.

ActionInstant

Clone Blueprint

Clones a blueprint and its associated resources.

ActionInstant

List Bots

Retrieves a paginated list of bots.

ActionInstant

Clone Bot

Clones a bot with its settings and configuration.

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.