Bring device alerts into the right Botpress conversation
When an Adafruit IO event reaches your Notis webhook, send its useful details to a Botpress conversation that you identify in the request.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
BOTPRESS_SEND_MESSAGE
Sends a message to a user in an existing conversation.
Why this helps
Important device alerts can get lost when you have to notice them in one system and manually update the relevant conversation in another.
- Put a device alert in an existing Botpress conversation
- Include the event details provided to the webhook
- Avoid switching tools to relay an alert manually
Setup
Build it in a few focused steps.
- 1Connect Adafruit IO and Botpress once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Describe in one instruction how to summarize the alert and send it to the existing conversation identified by the request.
- 4Choose a Notis webhook trigger and select where run reports should go.
- 5Test with one real alert and an existing Botpress conversation.
Questions about this workflow
Can the automation create the conversation if one does not exist?
This workflow uses the send-message action for an existing conversation. It does not create a conversation.
How does it know which conversation to update?
The webhook request must provide enough information to identify the existing Botpress conversation.
Will an Adafruit IO event start this automatically?
No Adafruit IO trigger events are available in this package. An HTTP request to the Notis webhook starts the workflow.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Adafruit IO to Botpress. A trigger fires from one place; an action lands in another.
Adafruit IO 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.
Adafruit IO 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.