Connect Agenty to Botpress
When something happens in Agenty, 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 Agenty to Botpress
Turn Agenty site changes into Botpress issue checks
When Agenty detects a website change, check the Botpress bot for related issues and send a concise report to your chosen channel.
Review Botpress usage after Agenty monitoring runs
On a schedule, use Agenty monitoring context to prompt Notis to retrieve Botpress usage history and summarize trends for your report channel.
Find Botpress conversations related to Agenty signals
Send an Agenty signal to a Notis webhook, then prompt Notis to find and summarize relevant Botpress conversations for follow-up.
Break down Botpress usage by bot for monitoring reviews
Schedule a Botpress workspace usage breakdown by bot and have Notis report the metrics relevant to your Agenty monitoring routine.
Check customer conversations after an Agenty browser run
Have an Agenty browser workflow call a Notis webhook, then review Botpress conversations for threads that match the run's context.
Keep a scheduled inventory of Botpress workspaces
Schedule a Botpress workspace list for your Agenty monitoring operations and receive a report that helps keep workspace context close at hand.
Normalize Agenty extraction data with Botpress VRL
Send structured data from Agenty to a Notis webhook and use Botpress VRL to transform, validate, or normalize it for downstream review.
Watch Botpress workspace quota completion
On a recurring schedule, check Botpress workspace quota completion rates and report the highest usage levels relevant to your Agenty monitoring setup.
Send a Botpress conversation notice from an Agenty alert
When an Agenty alert arrives through a Notis webhook, prompt Notis to send a message to an existing Botpress conversation with the relevant notice.
Supported Triggers and Actions
Notis builds workflows that link Agenty to Botpress. A trigger fires from one place; an action lands in another.
Agenty 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 Agenty and Botpress
Connect any two apps with Notis in the middle.
Agenty 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.