Give each Adafruit IO device incident its own Discord thread
Keep troubleshooting focused by giving each reported device incident a dedicated place to discuss it.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Create new thread in channel
Creates a thread in a channel.
Why this helps
When device alerts land in a busy channel, questions and updates can get buried among unrelated messages.
- Separate incident discussion from the main channel conversation.
- Use the device or feed details in the thread name when supplied.
- Give teammates one place to add context and troubleshoot.
Setup
Build it in a few focused steps.
- 1Connect Adafruit IO and Discordbot once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis to create a Discord thread when an incoming Adafruit IO webhook reports an incident, using the supplied device or feed name in the thread title.
- 4Choose the webhook trigger and select where Notis should send run reports.
- 5Send one real incident example and confirm the thread appears in the intended channel.
Questions about this workflow
What counts as an incident?
Define the incident condition in your instruction or include an incident status in the webhook request. Adafruit IO does not provide a trigger event here.
Can the thread title include the device name?
Yes, when the webhook request includes a device or feed name. Otherwise Notis has no reliable name to use.
What Discord access is needed?
The connected Discordbot needs permission to create threads in the selected channel. Private-thread access requirements also depend on the channel setup.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Adafruit IO to Discordbot. A trigger fires from one place; an action lands in another.
Adafruit IO triggers
Discordbot actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add recipient to group channel
This action is deprecated and unsupported.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add guild member
Adds a user to a guild using an OAuth token with the guilds.join scope.
Assign role to guild member
Assigns a role to a member of a server.
Add reaction to message
Adds an emoji reaction from the bot to a message.
Add thread member
Adds a user to an unarchived thread if they can access its parent channel.
Ban user from guild
Permanently bans a user from a guild, optionally deleting their recent messages.
Bulk ban users from guild
Bans up to 200 guild users, optionally deleting their recent messages; BAN_MEMBERS is required.
Bulk Delete Messages
Deletes 2–100 messages under 14 days old from a channel; requires message-management permission.
Connect any two apps with Notis in the middle.
Adafruit IO and Discordbot, 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 Discordbot.