Check Botpress issues when an AnyDB process flags a concern
An HTTP request starts a Notis run. Notis uses the relevant AnyDB context to identify the bot, checks its Botpress issues, and reports findings for review.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
LIST_BOT_ISSUES
Lists issues associated with a bot.
Why this helps
When a database process flags a concern, checking the bot manually adds another interruption and can delay triage.
- Start an issue check when an AnyDB process requests it
- Bring database context into bot troubleshooting
- Receive a clear report of issues to investigate
Setup
Build it in a few focused steps.
- 1Connect AnyDB and Botpress once in the Notis portal.
- 2Create an automation in Automations, New Automation, or tell Notis what to do from any channel.
- 3In one instruction, ask Notis to use the incoming AnyDB context to identify the Botpress bot, list its issues, and report findings.
- 4Choose a webhook trigger and configure the AnyDB process to send an HTTP request to it.
- 5Choose where run reports should go, then test with one real example and verify the identified bot and findings.
Questions about this workflow
Does AnyDB start this workflow with a built-in event?
No AnyDB trigger events are listed here. The workflow starts with a Notis webhook when an HTTP request is sent.
What if the request does not identify a Botpress bot?
Include enough context in the request or instruction for Notis to identify the bot. If that information is missing, the workflow cannot reliably check the intended bot.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link AnyDB to Botpress. A trigger fires from one place; an action lands in another.
AnyDB 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.
Connect any two apps with Notis in the middle.
AnyDB 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.