Connect Aeroleads to Botpress
When something happens in Aeroleads, Notis takes the next step in Botpress. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from Aeroleads to Botpress
Start a Botpress conversation for a new lead
Turn an Aeroleads lead sent to a Notis webhook into a Botpress conversation, with the lead context ready for follow-up.
Open Botpress conversations for enriched prospects
Start Botpress conversations only when an Aeroleads webhook includes the enriched contact context your team wants to use.
Create Botpress conversations from verified email leads
Pass Aeroleads contact records containing business email details into Botpress conversations through a Notis webhook.
Start Botpress threads for outreach replies
When Aeroleads outreach response data arrives at a Notis webhook, create a Botpress conversation for the reply context.
Create Botpress threads for a chosen prospect segment
Use segment information included in an Aeroleads webhook request to start Botpress conversations for the prospects you specify.
Start Botpress threads with company research
Use company details supplied by Aeroleads to create Botpress conversations with a useful starting context.
Avoid duplicate Botpress threads for repeated lead requests
Check Botpress conversation history before creating a thread for a repeated Aeroleads lead request.
Review Botpress threads related to an incoming lead
When a lead reaches a Notis webhook, look up Botpress conversations to help decide whether follow-up already has a thread.
Find Botpress context before handling an outreach reply
Use an Aeroleads reply request to review existing Botpress conversations and avoid losing the thread's context.
Supported Triggers and Actions
Notis builds workflows that link Aeroleads to Botpress. A trigger fires from one place; an action lands in another.
Aeroleads triggers
Botpress actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete File
Permanently deletes a file from a bot’s storage; this cannot be undone.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Break Down Workspace Usage By Bot
Breaks down workspace usage by bot, including invocations, storage, and AI spending.
Get Account
Retrieves details of the authenticated account.
BOTPRESS_CHARGE_WORKSPACE_UNPAID_INVOICES
Charges unpaid invoices for a workspace and returns which payments succeeded or failed.
LIST_BOT_ISSUES
Lists issues associated with a bot.
Check Handle Availability
Checks whether a workspace handle is available and suggests alternatives if it is taken.
LIST_CONVERSATIONS
Lists conversations so you can retrieve chat threads.
BOTPRESS_CREATE_ADMIN_INTEGRATION
Creates an integration in a workspace.
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.
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.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
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.
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.
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:
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.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
More ways to connect Aeroleads and Botpress
Connect any two apps with Notis in the middle.
Aeroleads and Botpress, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Botpress.