Give device alert follow-up a GitHub owner
When the alert already names an owner and issue, let Notis handle the handoff in GitHub.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Add assignees to an issue
Adds or removes assignees for a github issue; changes are silently ignored if the authenticated user lacks push access to the repository.
Why this helps
A sensor alert may be acknowledged quickly but still lack a clear owner for the software follow-up.
- Put responsibility on the existing issue quickly.
- Use the assignee provided in the alert or automation instruction.
- Reduce the chance that device follow-up gets lost in chat.
Setup
Build it in a few focused steps.
- 1Connect Bolt IoT and GitHub once in Notis.
- 2Create an automation from any channel or in Automations, New Automation.
- 3Tell Notis to add the specified assignee to the existing GitHub issue referenced by a Bolt IoT alert.
- 4Choose the webhook trigger and where run reports should go.
- 5Test using a real alert with a valid repository, issue number, and assignee.
Questions about this workflow
Will this create an issue if the alert has no issue number?
No. The available action adds or removes assignees on an existing issue.
What if the user cannot assign issues in that repository?
GitHub may silently ignore the change if the authenticated user lacks push access.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bolt iot to GitHub. A trigger fires from one place; an action lands in another.
Bolt iot triggers
GitHub actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List repositories starred by the authenticated user
Deprecated: lists repositories starred by the authenticated user, including star creation timestamps; use 'list repositories starred by the authenticated user' instead.
List stargazers
Deprecated: lists users who have starred a repository; use `list stargazers` instead.
Star a repository for the authenticated user
Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.
Add email for auth user
Adds one or more email addresses (which will be initially unverified) to the authenticated user's github account; use this to associate new emails, noting an email verified for another account will error, while an existing email for the current user is accepted.
Add app access restrictions
Replaces github app access restrictions for an existing protected branch; requires a json array of app slugs in the request body, where apps must be installed and have 'contents' write permissions.
Add a repository collaborator
Adds a github user as a repository collaborator, or updates their permission if already a collaborator; `permission` applies to organization-owned repositories (personal ones default to 'push' and ignore this field), and an invitation may be created or permissions updated directly.
Add a repository to an app installation
Adds a repository to a github app installation, granting the app access; requires authenticated user to have admin rights for the repository and access to the installation.
Connect any two apps with Notis in the middle.
Bolt iot and GitHub, 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 GitHub.