Skip to content
Notis

Give device maintenance work a Slack home

When a scheduled maintenance review identifies an issue that needs coordination, create a Slack channel for the work to happen in one place.

Trigger

Recurring schedule

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

Action

Create channel

Initiates a public or private channel-based conversation

Why this helps

Maintenance issues can turn into scattered conversations when there is no shared place to coordinate the people and next steps.

  • Creates a dedicated place to coordinate a maintenance issue
  • Helps keep device follow-up together
  • Uses a recurring schedule for planned maintenance reviews

Setup

Build it in a few focused steps.

  • 1Connect Adafruit IO and Slack once in the Notis portal.
  • 2Create an automation in Notis by naming it and describing when a maintenance issue warrants a channel.
  • 3Tell Notis to create a Slack channel when the scheduled review identifies a device issue that needs coordinated work.
  • 4Choose a recurring Notis schedule as the trigger and select where run reports should go.
  • 5Run one real or representative maintenance review and confirm the channel decision and name are appropriate.

Questions about this workflow

Does Adafruit IO provide the scheduled trigger?

No. This workflow uses a Notis schedule because no Adafruit IO trigger events are listed.

What information does Notis need to review?

The automation needs access to the relevant maintenance context in its prompt or run input. The listed event data does not specify an Adafruit IO history retrieval action, so provide any readings or maintenance notes the review should use.

Will a channel be created for every scheduled run?

The prompt should instruct Notis to create one only when the review identifies an issue that needs coordinated work. The schedule itself does not supply a maintenance baseline.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Adafruit IO to Slack. A trigger fires from one place; an action lands in another.

Adafruit IO triggers

Slack actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Set snooze duration

Deprecated: turns on do not disturb mode for the current user, or changes its duration. use `set dnd duration` instead.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Add a custom emoji to a Slack team

Deprecated: adds a custom emoji to a slack workspace given a unique name and an image url. use `add emoji` instead.

ActionInstant

Add an emoji alias

Adds an alias for an existing custom emoji in a slack enterprise grid organization.

ActionInstant

Add a remote file

Adds a reference to an external file (e.g., google drive, dropbox) to slack for discovery and sharing, requiring a unique `external id` and an `external url` accessible by slack.

ActionInstant

Add a star to an item

Stars a channel, file, file comment, or a specific message in slack.

ActionInstant

Add call participants

Registers new participants added to a slack call.

ActionInstant

Add emoji

Adds a custom emoji to a slack workspace given a unique name and an image url; subject to workspace emoji limits.

ActionInstant

Add reaction to message

Adds a specified emoji reaction to an existing message in a slack channel, identified by its timestamp; does not remove or retrieve reactions.

ActionInstant

Connect any two apps with Notis in the middle.

Adafruit IO and Slack, 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 Slack.