Find Botpress bot issues after an address validation failure
A failed address check can point to a chatbot configuration problem. Send an Addresszen webhook to Notis and have it check the relevant Botpress bot for reported issues.
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
Address checks and chatbot errors live in separate systems, making it easy to miss the connection while troubleshooting delivery details.
- Surface bot issues alongside an address validation failure
- Reduce context switching during delivery troubleshooting
- Get a concise summary of relevant Botpress issues
Setup
Build it in a few focused steps.
- 1Connect Addresszen and Botpress once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Describe that Notis should use the webhook payload to identify the relevant bot, list its issues, and summarize any that may relate to the address validation failure.
- 4Choose the webhook trigger and select where run reports should go.
- 5Send one real Addresszen failure webhook to test the workflow.
Questions about this workflow
Does Addresszen provide a native trigger for this workflow?
No. Start it with a Notis webhook, which Addresszen or your connected backend can call when it has an address validation result.
Can the workflow prove that a Botpress issue caused the failure?
No. It can summarize issues for the bot identified in the webhook. Any connection to the address failure is a possible lead, not proof.
What information should the webhook include?
Include enough context for Notis to identify the relevant Botpress bot, such as its bot ID, along with the address validation result.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Addresszen to Botpress. A trigger fires from one place; an action lands in another.
Addresszen 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.
Addresszen 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.